Just thought I'd let you know that yesterday I managed to get most of our application 
running with Jetty 5 alpha 3 and JBoss 3.2.2.

It also appears that I've got the JMX console working.

Here's what I did (assuming the use of the default server config):

* Removed $JBOSS_HOME/server/default/deploy/jbossweb-jetty.sar, and replaced with the sar 
from the Jetty 5 distribution.

* Replaced $JBOSS_HOME/lib/xercesImpl.jar with newer version (used the one bundled with 
Jetty) - thanks Greg.

* Replaced $JBOSS_HOME/server/default/lib/javax.servlet.jar with the jar from the Jetty 
sar (I was getting errors because my JSPs couldn't find 
javax.servlet.jsp.el.VariableResolver or something in that package)

* Added commons-el.jar to jbossweb-jetty.sar (probably would work in default/lib instead) 
taken from the ext directory of the Jetty distribution. I think I was getting class not 
found for something in org.apache.commons.el.

* Changed jmx-console.war/WEB-INF/web.xml and my webapps to use Servlet 2.4 schema. I was 
getting errors about the description elements in the jmx-console's descriptor, so I 
removed them and then it deployed. Had to fix some things in my webapps, and it tooks me a 
long time to realise that <taglib> now goes inside <jsp-config>. I found that trying to 
read the schema itself is really difficult, but there's a nice diagram of the descriptor 
in the spec.

* Upgraded JSTL from 1.0 to a nightly build of the apache JSTL 1.1 implementation:
http://jakarta.apache.org/taglibs/doc/standard-doc/intro.html (information)
http://cvs.apache.org/builds/jakarta-taglibs/nightly/projects/standard/ (nightly builds)
- I couldn't find the Beta 1 build that they mention on the information page. So that 
meant upgrading standard.jar in the Webapps lib directory and upgrading jstl.jar in 
$JBOSS_HOME/server/default/lib.

* Fixed the taglib declaration in my JSPs for the core JSTL library because it's been 
changed from http://java.sun.com/jstl/core to http://java.sun.com/jsp/jstl/core (annoying).

[As an aside, I don't know why JSTL 1.0 wouldn't work with JSP 2.0 - perhaps it's because 
the EL stuff has been moved out of JSTL, but the error I was getting was a TLD type error]

* Swore a lot :)

And now it seems to work (at least the parts where I've changed the JSTL declaration), and 
I've been able to view the jmx-console, update an attribute and invoke a method. I've not 
tried the web-console because so far I've not worked out what's so useful about it so I 
don't deploy it. As for the new features I've not done much more that try a simple bit of 
EL in a JSP, but that worked OK.

Interestingly my JBoss server seemed to start about 30 seconds quicker (1:30 instead of 
2:00) with the upgraded Jetty, but that could mean I've forgotten to deploy something!

Hope that's a useful guide to what's necessary. Please let me know if I'm putting any of 
the jars in the wrong place or doing anything that doesn't make sense.

-Andrew

Eric Jain wrote:

>>Jetty-5 in CVS now builds a jboss-jetty.sar.
> 
> Great!
> 
>>  1) You need to update the xerces used by JBoss to something
>>     that handles schemas well.
> 
> No problem.
> 
>>  2) You either need to non use the jmx-console or to replace
>>     the jasper jars (in the jboss-jetty.sar) with the JSP1.2
>>     jasper - as the jmx-console does not appear to work with
>>     JSP2.0???
> 
> That's a bit of a problem as my main interest in Jetty-5 is JSP2.0, and
> I do use the jmx-console a lot. Guess I'll need to wait until they fix
> that... In any case, thanks!
> 
> --
> Eric Jain
> 

-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
jetty-discuss mailing list
jetty-discuss <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jetty-discuss