Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   5388 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

Apache::AxKit::Plugin:UsergContributed Perl Apache::AxKit::Plugin::Fragment(3)

NAME
       Apache::AxKit::Plugin::Fragment - Fragment plugin

SYNOPSIS
	 AxAddPlugin Apache::AxKit::Plugin::Fragment

DESCRIPTION
       This module provides direct web access to XML fragments, using an XPath
       syntax. By simply providing a querystring containing an XPath query,
       this module will set the XML to be parsed to be the XML nodes returned
       by the query. The nodes will be wrapped in either <result-
       set>...</resultset> or you can specify the outer tag using:

	       PerlSetVar XPathFragmentElement foo

       to wrap it in <foo>...</foo>.

USAGE
       Simply add this module to the plugin list before StyleFinder:

	       PerlHandler Apache::AxKit::Plugins::Fragment \
			       AxKit

       Then request a URL as follows:

	       http://server/myfile.xml?/some/xpath/query

       Queries that match the regular expression: ^\w+= are ignored, as are
       any invalid XPath queries.

       Note that it's important to write your stylesheet to make use of this
       capability! If you intend to use this Fragment plugin, you can't assume
       that your stylesheet will just magically work. It will have to not make
       assumptions about the XML being passed into it. The apply_templates()
       method of XPathScript is extremely useful here, as is the xpath query
       'name(/child::node())' which identifies the top level element's name.
       Here's how I got around this with my first experiments with this:

	       <!-- Main document body -->
	       <% if (findvalue('name(/child::node())') eq 'page') { %>
		       <%= apply_templates('/page/body/section') %>
	       <% } else { %>
		       <%= apply_templates('/') %>
	       <% } %>

       Which checks that the top level element is called 'page', otherwise it
       simply does apply_templates() on all the nodes.

perl v5.8.8			  2005-07-14Apache::AxKit::Plugin::Fragment(3)

                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 

Vote for polarhome