Stephen I think this is a great idea - and will hopefully help in getting some of us moved over from 2.1 to 2.2 without too much pain.
One question/suggestion - is it possible to outline in simple steps how you get to build this war file and, as you point out, what changes need to be made along the way in order to add in various blocks; for example, I would need FOP and also the FINS block. Maybe a page on the wiki with these details, plus those below, would be the best place for all of this? Thanks Derek >>> On 2008/07/30 at 08:04, in message <[EMAIL PROTECTED]>, "Stephen Rosman" >>> <[EMAIL PROTECTED]> wrote: I've created an example of a simple cocoon application so that if all you're interested in is building a sitemap then you don't have to go through maven. It only has the default cocoon blocks at the moment, but I'd imagine that if you released a version of the software like this you'd include the kitchen sink or at least FOP. I haven't tested it on any other setup but I'd like to know if anyone is interested in this approach - it certainly would have saved me a lot of trouble if it had been available - I wouldn't have had to learn anything about log4j, spring or maven. It only required a single class to copy the context parameters across to a properties object for cocoon to do the initalisation - it probably doesn't even need that but I couldn't figure that out (no one answered by call for help on the mailing list :-(). Should I post the project source to the dev list? Anyhow the .war file is at: http://www.filefactory.com/file/e7800a/n/cocoon-simple-webapp-1_0-SNAPSHOT_war Configuration: If you're using Tomcat, you just stick it on your server (in my case C:\apps\cocoon-simple\), add a context fragment file (in my case C:\apps\tomcat\conf\Catalina\localhost\cc.xml). -- <Context docBase="C:\apps\cocoon-simple\cocoon-simple-webapp-1.0-SNAPSHOT.war"> <Parameter name="cocoon.site" value="C:\apps\cocoon-simple\site"/> <Parameter name="cocoon.logconfig" value="file:///c|/apps/cocoon-simple/logs/log4j.xml"/> </Context> -- Add a log4j configuration file specified by $cocoon.logconfig (in my case C:\apps\cocoon-simple\logs) -- <?xml version="1.0" encoding="UTF-8" ?> <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd"> <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/";> <appender name="CORE" class="org.apache.log4j.FileAppender"> <param name="File" value="c:/apps/cocoon-simple/logs/log4j.log" /> <param name="Append" value="false" /> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value="%d %-5p %t %c - %m%n"/> </layout> </appender> <root> <priority value="info"/> <appender-ref ref="CORE"/> </root> </log4j:configuration> -- And build your cocoon application in the directory specified in the $cocoon.site context initialisation parameter. -- Stephen Rosman --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks Transtec Computers for their support. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
