In the patch queue, there is a Castortransformer: <Castortransformer> Marshals a object from the Session or the Sitemap into a series of SAX events. TheCastortransformer need to be configured with a default mapping. This mapping is used as long as no other mappings are specfied. </Castortransformer>
The castor jar (xml only version) is about 750kb big, and the license is BSD style (http://castor.exolab.org/license.html). Now, it's cool to have Cocoon use all these projects out of the box, but the distribution is getting bigger and bigger every day. There are three solutions that come to my mind now: 1. make a ./src/contrib section that is not compiled; it is checked for compilation only upon distribution. Classes that do not compile at that time are (after a reasonable notification) purged from CVS. No jars are supplied. 2. make two distributions: Cocoon proper and Cocoon extra. This goes in Cocoon extra along with the jar. 3. Projects that give extra value to Cocoon, but not officially supported, can be moved in a SourceForge project (like ant does). What do you think? -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
