another thing to try when you want to couple jboss and cocoon2 is to comment out all hsqldb references because i found that to be the last obstacle(after xerces/crimson and xfvb was sorted out) to get cocoon2rc1 to run on jboss.
of reasons that i haven't yet looked carefully at the hsqldb server wants an absolut path to a work directory it has access to, but jboss autodeploys all wars in a temp directory, and hsql cannot live under these conditions, so it has to be boostrapped with a working directory. i solved this by hunting down and commenting out all references to hsqldb as well, but that's because i don't use it. a last knirk with jboss+tomcat4 is that the tomcat-test.ear that is bundled in the dist doesn't work when you have bootstrapped jboss to run with xerces and xalan, so i removed this ear file from the deploy dir, restarted jboss and copied the cocoon.war file into it. it works very well, except that tomcat4 still has a troubles with removing stale work files, so sometimes i have to kill jboss/tomcat/work/* to allow changes to take place. mvh karl řie -----Original Message----- From: Parc Place [mailto:[EMAIL PROTECTED]] Sent: 11. november 2001 21:19 To: [EMAIL PROTECTED] Subject: Re: Deploying Cocoon2 in JBoss under Linux Hi, sorry about the delay, just catching up on my email this afternoon. I managed to get this somewhat functional a few weeks ago - as you mention, there are a number of exceptions during startup about the unsupported codepage - I agree that it's not a critical problem, and can confirm that it isn't preventing cocoon from running. >>I've read and followed all instructions when trying to deploy >>Cocoon-2.0rc1a into JBoss-2.4.3_Tomcat-3.2.3 (the bundled edition) under my >>Debian linux (sid). I've removed the JAXP and Crimson parsers, had put >>xerces instead of it, modified the run.sh script according to the guide, and >>even replaced jaxp/crimson with xerces+xalan in my ant installation. >> Ok, here is a difference in our setup - I used the version bundled with tomcat 4 One thing that I needed help with was getting JBoss to use Xerces - I read on this mailing list (a very informative email from karl řie, email title was "FAQ: cocoon2 parser errors +tomcat/jboss/whatever", you can try searching for it) that you have to tell it which SAX parser and DOM builder to use - my run.sh for jboss has been modified so that it contains this: ... JBOSS_CLASSPATH=$JBOSS_CLASSPATH:../lib/xerces_1_4_3.jar JAXP=-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.Docum entBuilderFactoryImpl JAXP="$JAXP -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactory Impl" ... Although it was a nice challange getting all this working together, I've decided to switch back to plain Tomcat for Cocoon, and experiment with EJB seperately. For now, at least. Good luck, Adam --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]> --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
