[jules]

provided that you do not stray outside the J2EE specs, your knowledge and app should run on any compliant implementation.

Advantages of Jetty are :

1). You will get much better support in these fora - since it is JBoss' chosen webcontainer and I am the integrator :-)

2). Jetty is frequently reported as being faster, more robust and having better throughput and scalability than TC.

3). Jetty's goals include being enterprise strength and providing the best possible webcontainer within JBoss - TC's primary goal is to be the reference implementation....


If you are interested in Jetty - check out jetty.mortbay.org. It should tell you everything that you need to know.

Sorry for the sales pitch - but every now and then I like to justify Jetty's existence within the JBoss project and you mentioned it first.



Jules

[fodder]

Call me old fashioned but I'd quite like it if JBoss came with a few examples. Doesn't have to be fantastic but something.

Anyone got a working petstore that they would like to write some simple notes for ?

[jules]

Guys,

Forgive me if you've already considered this, but 9 times out of 10 it turns out to be the answer to this type of problem.

Unix filing systems are case sensitive.

If you created your app, or modified it under windows, you must ensure that the case of the dir/file names is as intended and consistent....

Jules

[sosparma]

I've verified that all my files and dirs are in place and that they're keeping their original cases, but JBoss cannot seem to be able to find my "WEB-INF/web.xml".

If I deploy my WAR file into Tomcat(without JBoss), it runs beautifully.

Could it be a small glitch inside JBoss?

Any help will be appreciated it. Thanks.

[slawsonb]

Regarding the Jetty sales pitch...

Is there an Apache connector for Jetty? If not, then there is no way I can choose Jetty.

[ikant]

I've searched all the forums. This questions has been asked over and over and no answer has yet to be posted.

[jules]

YES,

but I don't know much about it I shall defer to Greg - Jetty's author and when he has answered put it in the Jetty/JBoss integration FAQ on:

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/contrib/jetty/FAQ?rev=HEAD&content-type=text/vnd.viewcvs-markup

Over to you, Greg.


Jules

[jules]

This should save Greg's breath...


http://jetty.mortbay.com/jetty/doc/JettyWithApache.html

Jetty 4.1 (if you want AJP13 support) is currently in JBoss cvs HEAD.

I will merge it into Branch_3_0 as soon as Greg declares it stable (probably a couple of weeks away).

Hope that helps,


Jules

[gregwilkins]

Actually that document was out of date. I have now just updated it - so if you looked, look again!

http://jetty.mortbay.com/jetty/doc/JettyWithApache.html

The short story is that you can use mod_proxy to forward
requests as HTTP/1.1. This is simple but does not use persistent connections.

You can also now use mod_jk and the AJP13 protocol to get the full apache load balancing act etc. The AJP13 support is part of Jetty 4.1 and is in JBoss CVS head. Once it has proved stable, it will be back ported to JBoss 3.0.x