IN THE NEXT LINE, REPLACE THE "#" WITH "?" AND YOU WILL GET THE CORRECT FIRST LINE OF THE FILE (THIS WAS PUT IN TO PREVENT IE FROM BEING "INTELLIGENT" AND TRYING TO PROCESS THIS FILE)
<#xml version="1.0" encoding="UTF-8"#>
<map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0">
<!-- 
   This is the 'heart' of Cocoon. The sitemap maps URI space to 
   resources. It consists basicly of two parts: components and
   pipelines. Pipelines are made out of components.
-->



<!-- =========================== Components ================================ -->

 <map:components>

<!--
  All pipelines consist at least of two components: a generator, that
  produces the content and a serialiser, that delivers the content to
  the client.

  More precisely: a generator generates SAX events and a serializer
  consumes these events and produces a character stream.

  Some things to note here: each generator has a unique name, this
  name is mapped to a java class, one name is declared as default
  generator. In addition each generator may have additional
  configurations as child elements.

  Additional attributes are targeted at the component manager. The optional
  "label" attribute is relevant for the view concept below. The optional
  "logger" attribute defines the logging category where messages produced
  by a component should go. If there's no "logger" attribute, the category
  used is the one defined for the "sitemap" component in cocoon.xconf.

  We have chosen in this example sitemap to use a different logging category
  for each component, which allows fine-grained classification of log
  messages. But you are free to use any category you want.

  It is possible to have the same java class declared as different
  generators by using different names. No configuration options are
  shared between these instances, however.

  All components follow this schema.

-->
  <map:generators default="file">
    <map:generator label="content,data" logger="sitemap.generator.file" 
		name="file" 
		pool-grow="4" pool-max="32" pool-min="8" src="org.apache.cocoon.generation.FileGenerator"/>

    <map:generator label="content,data" logger="sitemap.generator.serverpages" 
		name="serverpages" 
		pool-grow="2" pool-max="32" pool-min="4" 
		src="org.apache.cocoon.generation.ServerPagesGenerator"/>
    
    <map:generator label="content,data" logger="sitemap.generator.directory" 
		name="directory" 
		pool-grow="2" pool-max="16" pool-min="2" 
		src="org.apache.cocoon.generation.DirectoryGenerator"/>

    <map:generator label="data" logger="sitemap.generator.request" 
		name="request" 
		pool-grow="2" pool-max="16" pool-min="2" 
		src="org.apache.cocoon.generation.RequestGenerator"/>

    <map:generator label="data" logger="sitemap.generator.status" 
		name="status" 
		pool-grow="2" pool-max="16" pool-min="2" src="org.apache.cocoon.generation.StatusGenerator"/>

   <map:generator label="content,data" logger="sitemap.generator.imagedirectory" 
		name="imagedirectory" 
		src="org.apache.cocoon.generation.ImageDirectoryGenerator"/>

   <map:generator label="data" logger="sitemap.generator.extractor" 
		name="extractor" 
		src="org.apache.cocoon.generation.FragmentExtractorGenerator"/>
  
    <map:generator label="content,data" 
		name="jsp" 
		src="org.apache.cocoon.generation.JspGenerator"/>

    <map:generator label="content,data" 
		name="stream" 
		src="org.apache.cocoon.generation.StreamGenerator"/>

    <map:generator label="content,data" 
		name="script" 
		src="org.apache.cocoon.generation.ScriptGenerator"/>

    <map:generator label="content,data" 
		name="html" 
		src="org.apache.cocoon.generation.HTMLGenerator"/>

    <map:generator label="content,data" 
		name="velocity" 
		src="org.apache.cocoon.generation.VelocityGenerator"/>


    <!-- ======================= SunShine =========================== -->
    <map:generator label="content,data" name="sunSpot" src="org.apache.cocoon.sunshine.sunspot.generation.PortalGenerator"/>
    <map:generator label="content,data" name="sunSpot-conf" src="org.apache.cocoon.sunshine.sunspot.generation.ConfigurationGenerator"/>
    <map:generator label="content,data" name="sunRise-conf" src="org.apache.cocoon.sunshine.sunrise.generation.ConfigurationGenerator"/>
</map:generators>

<!--
  Transformers can be placed inside the pipeline between the generator
  and the serializer. You may have as many transformers as you
  like. Transformers consume SAX events and emmit SAX events.

  The "xslt" transformer is an example of a component with additional
  configuration.
-->
  <map:transformers default="xslt">

    <map:transformer logger="sitemap.transformer.xslt" 
		name="xslt" 
		pool-grow="2" pool-max="32" pool-min="8"
		src="org.apache.cocoon.transformation.TraxTransformer">
      <use-request-parameters>false</use-request-parameters>
      <use-browser-capabilities-db>false</use-browser-capabilities-db>
      <use-deli>false</use-deli>
    </map:transformer>

    <map:transformer logger="sitemap.transformer.log" 
		name="log" 
		pool-grow="2" pool-max="16" pool-min="2" 
		src="org.apache.cocoon.transformation.LogTransformer"/>

    <map:transformer logger="sitemap.transformer.xinclude" 
		name="xinclude" 
		pool-grow="2" pool-max="16" pool-min="2" 
		src="org.apache.cocoon.transformation.XIncludeTransformer"/>

    <map:transformer logger="sitemap.transformer.cinclude" 
		name="cinclude" 
		pool-grow="2" pool-max="16" pool-min="2" 
		src="org.apache.cocoon.transformation.CIncludeTransformer"/>

   <map:transformer logger="sitemap.transformer.sql" 
		name="sql" 
		src="org.apache.cocoon.transformation.SQLTransformer"/>

   <map:transformer logger="sitemap.transformer.extractor" 
		name="extractor" 
		src="org.apache.cocoon.transformation.FragmentExtractorTransformer"/>

   <map:transformer logger="sitemap.transformer.i18n" 
		name="i18n" 
		src="org.apache.cocoon.transformation.I18nTransformer">
    <catalogue-name>messages</catalogue-name>
    <catalogue-location>translations</catalogue-location>
    <cache-at-startup>true</cache-at-startup>
   </map:transformer>

   <map:transformer logger="sitemap.transformer.filter" 
		name="filter" 
		src="org.apache.cocoon.transformation.FilterTransformer"/>

   <map:transformer logger="sitemap.transformer.writeDOMsession" 
		name="writeDOMsession" 
		src="org.apache.cocoon.transformation.WriteDOMSessionTransformer"/>

   <map:transformer logger="sitemap.transformer.readDOMsession" 
		name="readDOMsession" 
		src="org.apache.cocoon.transformation.ReadDOMSessionTransformer"/>

   <map:transformer logger="sitemap.transformer.encodeURL" 
		name="encodeURL" 
		src="org.apache.cocoon.transformation.EncodeURLTransformer"/>

  
   <map:transformer 
		name="xt" 
		src="org.apache.cocoon.transformation.XTTransformer"/>


    <!-- ======================= SunShine =========================== -->
    <map:transformer name="sunShine" src="org.apache.cocoon.sunshine.transformation.SunShineTransformer"/>
    <map:transformer name="sunShinePre" src="org.apache.cocoon.sunshine.transformation.SunShinePreTransformer"/>
    <map:transformer name="sunShinePost" src="org.apache.cocoon.sunshine.transformation.SunShinePostTransformer"/>
    <map:transformer name="sunShineInsert" src="org.apache.cocoon.sunshine.transformation.InsertTransformer"/>
</map:transformers>

<!--
  Readers are an exception to the above rule that a pipline need to
  have exactly one generator and exactly one serializer. Readers
  circumvent the XML oriented SAX pipeline model, think of a reader
  being a generator and a serializer at once thus a pipeline may not
  contain any generator, transformer or serializer in addition to a
  reader. They are useful for delivering binary content like images.
-->
  <map:readers default="resource">

    <map:reader logger="sitemap.reader.resource" 
		name="resource" 
		pool-max="32" src="org.apache.cocoon.reading.ResourceReader"/>
  
    <map:reader 
		name="jsp" 
		src="org.apache.cocoon.reading.JSPReader"/>

  </map:readers>

<!--
  Serializers consume SAX events and produce a character stream. Every
  pipeline needs to be terminated by a serializer.
-->
  <map:serializers default="html">

    <map:serializer logger="sitemap.serializer.html" mime-type="text/html" 
		name="html" 
		pool-grow="4" pool-max="32" pool-min="4" 
		src="org.apache.cocoon.serialization.HTMLSerializer">
      <buffer-size>1024</buffer-size>
    </map:serializer>

    <map:serializer logger="sitemap.serializer.links" 
		name="links" 
		src="org.apache.cocoon.serialization.LinkSerializer"/>

    <map:serializer logger="sitemap.serializer.xml" mime-type="text/xml" 
		name="xml" 
		src="org.apache.cocoon.serialization.XMLSerializer"/>

    <map:serializer logger="sitemap.serializer.vrml" mime-type="model/vrml" 
		name="vrml" 
		src="org.apache.cocoon.serialization.TextSerializer"/>

    <map:serializer logger="sitemap.serializer.wml" mime-type="text/vnd.wap.wml" 
		name="wml" 
		src="org.apache.cocoon.serialization.XMLSerializer">
      <doctype-public>-//WAPFORUM//DTD WML 1.1//EN</doctype-public>
      <doctype-system>http://www.wapforum.org/DTD/wml_1.1.xml</doctype-system>
      <encoding>ASCII</encoding>
      <omit-xml-declaration>yes</omit-xml-declaration>
    </map:serializer>

    <map:serializer logger="sitemap.serializer.svgxml" mime-type="image/svg-xml" 
		name="svgxml" 
		src="org.apache.cocoon.serialization.XMLSerializer">
      <doctype-public>-//W3C//DTD SVG 20000303 Stylable//EN</doctype-public>
      <doctype-system>http://www.w3.org/TR/2000/03/WD-SVG-20000303/</doctype-system>
    </map:serializer>

    <map:serializer logger="sitemap.serializer.xhtml" mime-type="text/html" 
		name="xhtml" 
		pool-grow="2" pool-max="64" pool-min="2" src="org.apache.cocoon.serialization.XMLSerializer">
      <doctype-public>-//W3C//DTD XHTML 1.0 Strict//EN</doctype-public>
      <doctype-system>http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd</doctype-system>
      <encoding>UTF-8</encoding>
    </map:serializer>

    <map:serializer logger="sitemap.serializer.text" mime-type="text/text" 
		name="text" 
		src="org.apache.cocoon.serialization.TextSerializer"/>
  
    <map:serializer mime-type="image/jpeg" 
		name="svg2jpeg" 
		src="org.apache.cocoon.serialization.SVGSerializer">
      <parameter name="quality" type="float" value="0.9"/>
    </map:serializer>

    <map:serializer mime-type="image/png" 
		name="svg2png" 
		src="org.apache.cocoon.serialization.SVGSerializer"/>

    <map:serializer mime-type="application/pdf" 
		name="fo2pdf" 
		src="org.apache.cocoon.serialization.FOPSerializer"/>
		
    <map:serializer mime-type="application/postscript" 
		name="fo2ps" 
		src="org.apache.cocoon.serialization.FOPSerializer"/>

    <map:serializer mime-type="vnd.hp-PCL" 
		name="fo2pcl" 
		src="org.apache.cocoon.serialization.FOPSerializer"/>

  </map:serializers>

<!--
  Matchers are executed during pipeline setup. They decide if a
  pipeline fragment is used within a pipeline. Usually, the decision
  is based on a match on the requested URI but matchers exist, that
  match different things as well. Most often the fragment contained in
  a matcher has a generator as well as a serializer. This is not a
  necessity, matchers can be nested while chaining does not work.
  Related concepts are selectors and actions. 

  Since this is important, let me repeat it: Matchers are executed
  during pipeline setup.
-->
  <map:matchers default="wildcard">

    <map:matcher logger="sitemap.matcher.wildcard" 
		name="wildcard" 
		src="org.apache.cocoon.matching.WildcardURIMatcher"/>

    <map:matcher logger="sitemap.matcher.regexp" 
		name="regexp" 
		src="org.apache.cocoon.matching.RegexpURIMatcher"/>

    <map:matcher logger="sitemap.matcher.request-parameter" 
		name="request-parameter" 
		src="org.apache.cocoon.matching.RequestParameterMatcher"/>

    <map:matcher logger="sitemap.matcher.cookie" 
		name="cookie" 
		src="org.apache.cocoon.matching.CookieMatcher"/>

    <map:matcher logger="sitemap.matcher.header" 
		name="header" 
		src="org.apache.cocoon.matching.HeaderMatcher"/>

    <map:matcher logger="sitemap.matcher.parameter" 
		name="parameter" 
		src="org.apache.cocoon.matching.ParameterMatcher"/>

    <map:matcher logger="sitemap.matcher.sessionstate" 
		name="sessionstate" 
		src="org.apache.cocoon.matching.WildcardSessionAttributeMatcher">
      <attribute-name>org.apache.cocoon.SessionState</attribute-name>
    </map:matcher>

    <map:matcher logger="sitemap.matcher.next-page" 
		name="next-page" 
		src="org.apache.cocoon.matching.WildcardRequestParameterMatcher">
      <parameter-name>next-state</parameter-name>
    </map:matcher>

    <map:matcher logger="sitemap.matcher.referer-match" 
		name="referer-match" 
		src="org.apache.cocoon.matching.WildcardHeaderMatcher">
      <header-name>referer</header-name>
    </map:matcher>
 
 </map:matchers>

<!--
  Selectors are executed during pipeline setup. They can be used to
  determine which pipeline fragments should be combined. They are best
  compared with a switch statement in java. Matchers and actions are
  related concepts.

  Since this is important, let me repeat it: Selectors are executed
  during pipeline setup.
-->
  <map:selectors default="browser">

    <map:selector logger="sitemap.selector.browser" 
		name="browser" 
		src="org.apache.cocoon.selection.BrowserSelector">
    <!-- # NOTE: The appearance indicates the search order. This is very important since
         #       some words may be found in more than one browser description. (MSIE is
         #       presented as "Mozilla/4.0 (Compatible; MSIE 4.01; ...")
    -->
      <browser name="explorer" useragent="MSIE"/>
      <browser name="pocketexplorer" useragent="MSPIE"/>
      <browser name="handweb" useragent="HandHTTP"/>
      <browser name="avantgo" useragent="AvantGo"/>
      <browser name="imode" useragent="DoCoMo"/>
      <browser name="opera" useragent="Opera"/>
      <browser name="lynx" useragent="Lynx"/>
      <browser name="java" useragent="Java"/>
      <browser name="wap" useragent="Nokia"/>
      <browser name="wap" useragent="UP"/>
      <browser name="wap" useragent="Wapalizer"/>
      <browser name="mozilla5" useragent="Mozilla/5"/>
      <browser name="mozilla5" useragent="Netscape6/"/>
      <browser name="netscape" useragent="Mozilla"/>
    </map:selector>

    <map:selector logger="sitemap.selector.request-parameter" 
		name="request-parameter" 
		src="org.apache.cocoon.selection.RequestParameterSelector">
    <!-- Define now which request parameter to use; or do it later,
         when using this selector, via "parameter-name" parameter.
    <parameter-name>myparam</parameter-name> 
    -->
    </map:selector>

    <map:selector logger="sitemap.selector.request-attribute" 
		name="request-attribute" 
		src="org.apache.cocoon.selection.RequestAttributeSelector">
    <!-- <attribute-name>myparam</attribute-name> -->
    </map:selector>

    <map:selector logger="sitemap.selector.session-attribute" 
		name="session-attribute" 
		src="org.apache.cocoon.selection.SessionAttributeSelector">
    <!-- <attribute-name>myparam</attribute-name> -->
    </map:selector>

    <map:selector logger="sitemap.selector.parameter" 
		name="parameter" 
		src="org.apache.cocoon.selection.ParameterSelector"/>

    <map:selector logger="sitemap.selector.header" 
		name="header" 
		src="org.apache.cocoon.selection.HeaderSelector">
    <!-- <header-name>myparam</header-name> -->
    </map:selector>

    <map:selector logger="sitemap.selector.host" 
		name="host" 
		src="org.apache.cocoon.selection.HostSelector"/>

  </map:selectors>

<!--
  Actions are executed during pipeline setup. Their purpose is to
  execute some arbitrary complex code. They are the work horses of
  pipelines. Use them to update databases, check external resources
  etc. The execution may fail or complete successfully. Only if the
  execution was successful, the pipeline fragment contained inside is
  used within the pipeline. Related concepts are matchers and
  selectors.

  Since this is important, let me repeat it: Actions are executed
  during pipeline setup.
-->
  <map:actions>

    <map:action logger="sitemap.action.add-employee" 
		name="add-employee" 
		src="org.apache.cocoon.acting.DatabaseAddAction"/>

    <map:action logger="sitemap.action.del-employee" 
		name="del-employee" 
		src="org.apache.cocoon.acting.DatabaseDeleteAction"/>

    <map:action logger="sitemap.action.upd-employee" 
		name="upd-employee" 
		src="org.apache.cocoon.acting.DatabaseUpdateAction"/>

<!-- deprecated, use locale in stead
    <map:action logger="sitemap.action.lang-select" 
		name="lang-select" 
		src="org.apache.cocoon.acting.LangSelect"/>
-->
    <map:action logger="sitemap.action.locale" 
		name="locale" 
		src="org.apache.cocoon.acting.LocaleAction"/>

    <map:action logger="sitemap.action.request" 
		name="request" 
		src="org.apache.cocoon.acting.RequestParamAction"/>

    <map:action logger="sitemap.action.form-validator" 
		name="form-validator" 
		src="org.apache.cocoon.acting.FormValidatorAction"/>

    <map:action logger="sitemap.action.session-state" 
		name="session-state" 
		src="org.apache.cocoon.acting.SessionStateAction"/>

    <map:action logger="sitemap.action.session-isvalid" 
		name="session-isvalid" 
		src="org.apache.cocoon.acting.SessionIsValidAction"/>

    <map:action logger="sitemap.action.resource-exists" 
		name="resource-exists" 
		src="org.apache.cocoon.acting.ResourceExistsAction"/>

    <map:action logger="sitemap.action.set-header" 
		name="set-header" 
		src="org.apache.cocoon.acting.HttpHeaderAction"/>

  

    <!-- ======================= SunShine =========================== -->
    <map:action name="sunShine-session" src="org.apache.cocoon.sunshine.acting.SessionAction"/>
    <map:action name="sunRise-auth" src="org.apache.cocoon.sunshine.sunrise.acting.AuthAction">
        <handlers>
          <handler name="sunspotdemohandler" xmlns:map="http://apache.org/cocoon/sitemap/1.0" xmlns:sunshine="http://sunshine.sundn.de/sunshine/1.0">
		<redirect-to uri="cocoon://sunspotdemoportal"/>
		<authentication uri="cocoon:raw://sunspotdemoresource-sunrise-authuser"/>
		<load-users uri="cocoon:raw://sunspotdemoresource-sunrise-loaduser"/>
		<load-roles uri="cocoon:raw://sunspotdemoresource-sunrise-roles"/>
		<new-user uri="cocoon:raw://sunspotdemoresource-sunrise-newuser"/>
		<new-role uri="cocoon:raw://sunspotdemoresource-sunrise-newrole"/>
		<change-user uri="cocoon:raw://sunspotdemoresource-sunrise-changeuser"/>
		<delete-role uri="cocoon:raw://sunspotdemoresource-sunrise-delrole"/>
		<delete-user uri="cocoon:raw://sunspotdemoresource-sunrise-deluser"/>
		<applications>
			<application loadondemand="true" name="sunspotdemo">
				<configuration name="sunSpot">
					<auth-redirect>sunspotdemo-portal</auth-redirect>
					<portal-uri>sunspotdemo-portal</portal-uri>
					<profile-cache>true</profile-cache>
					<process-sunlets-parallel>false</process-sunlets-parallel>
					<default-sunlet-timeout>10000</default-sunlet-timeout> <!-- milliseconds -->
					<profile>
						<layout-base uri="sunspotdemo/profiles/layoutprofile.xml"/>
						<sunlet-base uri="sunspotdemo/profiles/sunletprofile.xml"/>
						<sunlet-base-save uri="sunspotdemo/profiles/sunletprofile.xml"/>
						<type-base uri="sunspotdemo/profiles/types.xml"/>
						<admin-type-base uri="sunspotdemo/profiles/admintypes.xml"/>
						<global-delta-load uri="sunspotdemo/profiles/globalprofile.xml"/>
						<global-delta-save uri="cocoon:raw://sunspotdemoresource-saveglobalprofile"/>
						<role-delta-load uri="cocoon:raw://sunspotdemoresource-roleprofile"/>
						<role-delta-save uri="cocoon:raw://sunspotdemoresource-saveroleprofile"/>
						<user-delta-load uri="cocoon:raw://sunspotdemoresource-userprofile"/>
						<user-delta-save uri="cocoon:raw://sunspotdemoresource-saveuserprofile"/>
						<user-status-load uri="cocoon:raw://sunspotdemoresource-userstatus"/>
						<user-status-save uri="cocoon:raw://sunspotdemoresource-saveuserstatus"/>
					</profile>
				</configuration>
			</application>
		</applications>
	    </handler>
        </handlers>
    </map:action>

    <map:action name="sunRise-login" src="org.apache.cocoon.sunshine.sunrise.acting.LoginAction"/>
    <map:action name="sunRise-logout" src="org.apache.cocoon.sunshine.sunrise.acting.LogoutAction"/>
    <map:action name="sunRise-loggedIn" src="org.apache.cocoon.sunshine.sunrise.acting.LoggedInAction"/>
    <map:action name="sunSpot-auth" src="org.apache.cocoon.sunshine.sunspot.acting.AuthAction"/>
  </map:actions>
</map:components>

<!-- =========================== Views =================================== -->

<!--
  Views provide diffent, well, views to resources. Views are
  orthogonal to pipelines. Please refer to the docs.
-->
 <map:views>
  <map:view from-label="content" name="content">
   <map:serialize type="xml"/>
  </map:view>

  <map:view from-label="data" name="pretty-content">
    <map:transform src="stylesheets/simple-xml2html.xsl"/>
    <map:serialize type="html"/>
  </map:view>
  
  <map:view from-position="last" name="links">
   <map:serialize type="links"/>
  </map:view>

 </map:views>

<!-- =========================== Resources ================================= -->

<!--
  Resources are pipeline fragments that may be used from different
  pipeline fragments. For our needs, they behave exactly like
  pipelines, only that they are not accessible from outside.
  Hence I will explain what's inside below for pipelines.
-->

 <map:resources>
  <map:resource name="slides">
   <map:generate src="docs/samples/slides/slides.xml"/>
   <map:transform src="stylesheets/slides/slides-navigation.xsl">
    <map:parameter name="use-request-parameters" value="true"/>
    <map:parameter name="use-browser-capabilities-db" value="true"/>
   </map:transform>
   <map:transform src="stylesheets/slides/slides-apachecon.xsl"/>
   <map:serialize/>
  </map:resource>

  <map:resource name="dynamic-page">
     <map:generate src="{target}.xsp" type="serverpages"/>
     <map:transform src="stylesheets/dynamic-page2html.xsl">
       <map:parameter name="view-source" value="{target}.xsp"/>
     </map:transform>
     <map:serialize/>
  </map:resource>

  <map:resource name="dynamic-page1">
     <!-- print all current sitemap parameters to log -->
     <map:act type="session-state">
        <map:parameter name="new-state" value="{../0}"/>
        <!-- 
           use the complete string that was matched as a parameter. Compare
           this with the target parameter below. There the third
           sitemap parameter refers to the very same string. Verfy this
           by looking at the log. This irritating effect stems from
           the fact, that the above map:parameter belongs conceptually
           still to the parent element while all other nested tags
           are, well, nested.
        -->
        <map:call resource="dynamic-page">
           <map:parameter name="target" value="{../target}/state{../../../0}{../../0}"/>
        </map:call>
     </map:act>
  </map:resource>

  <map:resource name="dynamic-page2">
     <map:act type="session-state">
        <map:parameter name="new-state" value="1"/>
        <map:call resource="dynamic-page">
           <map:parameter name="target" value="{../target}1"/>
        </map:call>
     </map:act>
  </map:resource>

  <map:resource name="simple-page">
     <map:generate src="{target}.xml" type="file"/>
     <map:transform src="stylesheets/page/simple-page2html.xsl">
        <map:parameter name="view-source" value="{target}.xml"/>
     </map:transform>
     <map:serialize/>
  </map:resource>
 </map:resources>

<!-- ========================== Action sets ================================ -->

<!--
  Action sets group actions together. If some actions are often used
  together in pipeline fragments, it's easier to group them and refer
  to the group. For more info, please see the docs.
-->

 <map:action-sets>
  <map:action-set name="employee">
   <map:act action="Add" type="add-employee"/>
   <map:act action="Delete" type="del-employee"/>
   <map:act action="Update" type="upd-employee"/>
  </map:action-set>
 </map:action-sets>

<!-- =========================== Pipelines ================================= -->

<!--
  Pipelines. The beef. Pipelines specify, how the processing of your
  content is done. Usually, a pipeline consists of several fragments
  that specify the generation, transformation, and serialization of
  SAX events.

  Processing is done in two steps:

  1) The top level elements are executed in order of appearance until
     one signals success. These top level elements are usually
     matchers. AFAIK other components are not supported for this.

     Other components are called depth-first to determine what
     fragments make up the processing pipeline. When a component
     fails, no nested components are called but the next component on
     the same level.

  2) Once it is determined which generator, which transformers and
     wich serializer is used, these components are executed. During
     this, the pipeline may not be changed.


  You may have as many pipelines in your sitemap as you like. However,
  it seems that the only purposes would be to specify different error
  handlers.
-->

 <map:pipelines>

	<!-- ***** NUN.ME.SHU pipelines ***** -->

	<!-- filter out featured sites, and use local sitemap for its xml files -->
	<map:pipeline>
		<map:match pattern="s/ldde/**.xml">
			<map:mount check-reload="yes" src="s/ldde/sitemap.xmap" uri-prefix="s/ldde"/>
		</map:match>
	</map:pipeline>

	<map:pipeline>
		<map:match pattern="s/framework/**.xml">
			<map:mount check-reload="yes" src="s/framework/sitemap.xmap" uri-prefix="s/framework"/>
		</map:match>
	</map:pipeline>

	
	<!-- process xml files -->
	<map:pipeline>
		
		<map:match pattern="**.xml">
			<map:generate src="{1}.xml"/>
			<map:transform src="xsl/main.xsl">
				<map:parameter  name="use-request-parameters" value="true"/>			
			</map:transform>
			<map:serialize/>
		</map:match>

		<!-- append "-source" to any xml file, and you will be able to view the xml source -->
		<map:match pattern="**.xml-source">
			<map:generate src="{1}.xml"/>
			<map:transform src="xsl/cp.xsl"/>
			<map:serialize type="xml"/>
		</map:match>
		
	</map:pipeline>

 </map:pipelines>

</map:sitemap><!-- end of file -->