Thanks to all !
Yesterday I found out the reason for my problem.
In my personal build script for jboss I did
an un-jar of jetty-plugin.sar,
replaced the conf/default by conf/ebm1 in jetty.xml for my personal
config dir
and packed this together and put it to $JBOSS_HOME/deploy/lib.
But not all
Using the current cvs-version of jboss, I get some new problems on
startup after doing an build all.
conf-file jboss-service.xml requests jbosspool.jar.
jbosspool.jar was build in jboss-all/pool/ouput/lib but not copied to
$JBOSS_HOME/lib/ext.
conf-file jboss-service.xml also requests
Frank,
I'm surprised at the Jetty error.
mortbay.jetty.jar should not be in lib/etc but jetty-plugin.sar, which contains it,
should.
can you confirm ?
when you say current - how current ?
are there any other errors, warnings associable with Jetty upon startup ?
what happens if you move the
Julian Gosnell schrieb:
Frank,
I'm surprised at the Jetty error.
mortbay.jetty.jar should not be in lib/etc but jetty-plugin.sar, which contains it,
should.
can you confirm ?
jetty-plugin.sar is in deploy/lib. It contains
org.jboss.jetty.JBossLogSink but not
