portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18415] - Jetspeed can't be deployed and used with JBoss
Date Tue, 01 Apr 2003 16:19:29 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18415>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18415

Jetspeed can't be deployed and used with JBoss





------- Additional Comments From roshan741@hotmail.com  2003-04-01 16:19 -------
Hello,

I have got Jetspeed working on Jboss 3.0.6.  I have outlined the steps I took below.

The issues that you get are really Jboss issues. If you try running Jetspeed in
standalone Tomcat or Jetty Servlet engines it works fine out of the box. 

By default, Jboss doesn't use the Classloading rules outlined in the Servlet
specification. Instead it uses the standard Java2 classes loading rules. This
means it might not be using the JAR files packaged with Jetspeed but instead use
the ones packaged with Jboss. 

You can resolve this by making sure the JAR files used are the ones needed by
Jetspeed. So delete/replace wrong JAR file versions. A better solution is
probably enabling Servlet spec's classloading rules in Jboss. I am not sure how :-(

For Jboss 3.0.6 with Jetty

[1] Remove  $JBOSS_HOME/server/default/lib/caster.jar
[2] Replace  $JBOSS_HOME/server/default/lib/hsqldb.jar with the one included in
Jetspeed. Without this I got an error saying the HSQL database version is wrong.
So you only need this step if you use HSQL as your database in Jetspeed.

For Jboss 3.0.6 with Tomcat

[1] Do the same steps as above to resolve JAR file issues.
[2] Then expand the jetspeed.war file in to a directectory in the  deployment
folder.  I created a directory called
$JBOSS_HOME/server/default/deploy/jetspeed.war (note this is a directory not a
file).  Jetty expands the WAR file. But the Tomcat version doesn't. I think
without expanded WAR it can't load the property files. 

Some of this issues are already documented in 
http://www.shiftat.com/blog/page/werner/20021027

Hope this helps.

Regards,
Roshan

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org


Mime
View raw message