Cocoon & DataBase
Origonal Link: http://localhost:8080/cocoon/documents/developing/datasources.html


Memory Refresh:
Heard of cocoon: 

	Three files:
		$CATALINA_HOME/webapps/cocoon/sitemap.xmap	
		$CATALINA_HOME/webapps/cocoon/WEB-INF/cocoon.xconf
		$CATALINA_HOME/webapps/cocoon/WEB-INF/web.xml
	
	
	All of these objects from generator to serializer, but also viewer, ressource, etc.. will be describing by one name and one java class:
	in fact this is a mapping between a functionnality and his code execution. Exemple:
	<map:generator label="content,data" name="html" src="org.apache.cocoon.generation.HTMLGenerator"/>
	
	
$CATALINA_HOME/webapps/cocoon/sitemap.xmap				
	The sitemap maps URI space to resources. It consists of two parts: components & pipelines.
	Pipeline made out of components. There exists lot of variety of components.
	One Pipeline is describing by an input (a generator) and one output (one serializer). 
	Between these two objects we can found other objectss as :
		transformer
			transform an xml input to xml output, ie consume SAX event and produce SAX event. Example, translation multi-language, ie I18n:
			<map:transformer logger="sitemap.transformer.i18n" name="i18n" src="org.apache.cocoon.transformation.I18nTransformer"/>
		matchers		
		selectors 		(enable switch, if then else operation)
		action
	
	Generator read a specific input and give an xml output. Here we have defining the mapping between html input and the job to process an xml output.
	Transformer take a xml input and give an xml output.
	Serializer read an xml input and give pdf, svg, html, etc. ouput format.
	
	* Readers
		is an exception. A reader is in the same time, an generator, serializer. They are useful for delivering binary content like ipages or jsp.
		<map:reader name="jsp" src="org.apache.cocoon.reading.JSPReader"/>
		
		<map:match pattern="news/**.jpg">
			<map:read mime-type="image/jpg" src="http://images.slashdot.org/topics/{1}.jpg"/>
		</map:match>
	* Viewers
		<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>		
	* Ressources
		are pipelines fragments, or exactly like pipelines.
	* Pipelines
		<map:pipelines>
		
			<map:pipeline>
				<map:match pattern="sub/**">
					<map:mount check-reload="yes" src="sub/sitemap.xmap" uri-prefix="sub"/>
				</map:match>
				<map:handle-errors>
					<map:transform src="stylesheets/system/error2html.xsl"/>
					<map:serialize status-code="500"/>
				</map:handle-error>
			</map:pipeline>
			
			<-- 
				The previous pipeline must be seen like a sub-sitemap mounted like the Unix command mount, 
				it's recommanded by the author. Author have recommended to place sitemap.xmap file in each
				sub-sitemap 
			-->
			
			<map:pipeline>
				<map:match pattern="documents/index">
					<map:redirect-to uri="index.html"/>
				</map:match>
				<map:match pattern="documents/**">
					<map:mount check-reload="yes" src="documentation/" uri-prefix="documents"/>
				</map:match>
				<map:match pattern="tutorial/**">
					<map:mount check-reload="yes" src="tutorial/" uri-prefix="tutorial"/>
				</map:match>
			</map:pipeline>	
				
			<-- ====================
				Main sample pipeline
				==================== -->
				
			<map:pipeline>
				<map:match pattern="">
					<map:generate src="welcome/welcome.xhtml"/>
					<map:serialize/>
				</map:match>
				
				<map:match pattern="cocoon.gif">
					<map:read mime-type="image/gif" src="welcome/cocoon.gif"/>
				</map:match>
				
				<map:match pattern="news/**.jpg">
					<map:read mime-type="image/jpg" src="http://images.slashdot.org/topics/{1}.jpg"/>
				</map:match>
				
				<map:match pattern="welcome">
					<map:generate src="docs/samples/samples.xml" />
				</map:match>
			
				<map:match pattern="news/slashdot.xml">
					<map:generate src="http://slashdot.org/slashdot.xml"/>
					<map:transform src="stylesheets/news/slashdot.xsl"/>
					<map:serialize/>
				</map:match>				
			
				<--- This main pipeline is not a simple pipeline is an "oléoduc" ...... -->
			</map:pipeline>	
						
		</map:pipelines>	
			
	
$CATALINA_HOME/webapps/cocoon/WEB-INF/cocoon.xconf
$CATALINA_HOME/webapps/cocoon/WEB-INF/web.xml


Install really simple.
In order to install Oracle driver.
Please go to $CATALINA_HOME/webapps/cocoon/WEB-INF/web.xml

<init-param> 
<param-name>load-class</param-name> 
<param-value>
<!-- For PostgeSQL Database: --> postgresql.Driver

<!-- For Oracle Database: --> oracle.jdbc.driver.OracleDriver
</param-value> 
</init-param>

You can download your JDBC Oracle Driver on 
http://technet.oracle.com/software/content.html
or
http://technet.oracle.com/
or
http://dbdependency.sourceforge.net/download.html



Notes:
======
1. If you have Oracle JDeveloper 3.0, it already has the Oracle 8
and 8i JDBC drivers.

2. If you have Oracle JDeveloper 2.0, note that the JDBC driver
will not work against an Oracle8i Linux database, due to a bug
with the drivers shipped with JDeveloper 2.0.

3. If you have Oracle8i, use the JDBC drivers shipped with the
Oracle8i database. You need to install this component using the
Oracle Universal Installer. 




My first xml page converted in html by cocoon:
==============================================
Plateform: 
	Debian 2.4.18-686 (uname -r), TC4.1.12, cocoon-2.0.3, j2sdk1.3.1, jikes-1.17, ant 1.5.1
Installation
	TC: By using binary package
	Ant idem

Before, read your mapped URI in your $CATALINA_HOME/webapps/cocoon/sitemap.xmap
For example as seen before, we have m