If you rename the webapps directory in cocoons build directory to webapps.war (or anything else, als long as the ".war" is at the end) you can deploy Cocoon by moving/copying the entire directory to the jboss/server/default/deploy directory (Make sure JBoss is nor runing, as JBoss will emediately start deploying the webapp and if the OS is not finished with copying you will get tons of errors).
Afert starting JBoss you should be able to acess Cocoon at http://localhost:8080/{name of the directory without the ".war" at the end/
Hope this could help. Chris
beyaNet wrote:
Hi Chris,
I am in the process of moving from Tomcat to JBoss, but don't want to go through the hear ache of spending days trying to get everything to work. Could you possibly tell me all the stages involved in your jboss/cocoon setup process?
many thanks
Andrew On 18 Oct 2004, at 16:19, Christofer Dutz wrote:
Ok ... I am starting to feel a little silly now. I keep on searching the web before posting to this list. As soon as I do post something I find the solution ... I found some information at: http://www.orava.org/orava/weblog/category/web-systems/
The solution to the problems with Cocoon 2.1.5.1 not beeing able to run in Jboss 4.0 is a simple library-versioning problem and can be solved the folowing way: 1. You have to move the |logkit-1.2.2.jar file from |WEB-INF/lib to JBoss server/{theconfigyouwant}/lib 2. After this commons-logging-1.0.4.jar and log4j-1.2.8.jar have to be removed from Cocoons WEB-INF/lib directory These little changes made Cocoon work with JBoss 4.0 nicely.
Chris
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
