RE: [JBoss-user] Jetty vs Tomcat
I am guessing you use Ant to build your project? If so, why not compile them as part of the build? I know Ant can do this in some manner. --- Rod Macpherson <[EMAIL PROTECTED]> wrote: > I agree this needs clarification and we do not have > any > container-specific features so it boils down to > which one JBoss > determines is the least problematic in general or > the most beneficial in > general. Speaking of web containers and features > that are remarkable in > their absense, when deploying large webapps it can > be a real burden not > being able to precompile all of the JSP pages. I > have brought this up > several times and bascially got a shoulder shrug. > The reason that > surprises me is that the time to compile each page > during a regression > test has a material impact on the build/test/deploy > cycle. This really > takes up a lot of valuable QA time because you have > to go through and > hit each page individually rather than having them > automatically > compiled as part of the build and deploy process. > Anybody else vote for > this? > > Rod > > -Original Message- > From: Joachim Van der Auwera > [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 06, 2003 7:23 AM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] Jetty vs Tomcat > > > Fair enough, but the question remains. > It used to be Tomcat, then changed to Jetty and now > changed to Tomcat > again. I can only assume this has something to do > with the feature set > and/or integration with JBoss. > > What are the differences between the two containers? > Just to make sure > that us users can make an informed choice between > the two. > > Thanks for the info, > Joachim > > - Original Message - > From: "Scott M Stark" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, August 06, 2003 2:48 PM > Subject: Re: [JBoss-user] July 2003 news > > > > As stated in previous msgs on the question of > Jetty, we will continue > > to maintain the embedded container service. > > > > -- > > > > Scott Stark > > Chief Technology Officer > > JBoss Group, LLC > > > > > > Kevin Duffey wrote: > > > > > Great stuff. One question, what happened to > Jetty? It seemed JBoss > > > moved to Jetty not too long ago, and as far as I > knew Jetty was a > > > better servlet/jsp/web container than Tomcat. > Can you please advise > > > us as to what is going on here, especially with > Greg sending an > > > email out indicating he and the JEtty team are > no > > > longer able to commit to JBoss? Did you guys > decide to > > > drop Jetty now? I sure would hate to see that. > Jetty > > > is much easier to work than Tomcat! I have > chills at > > > using Tomcat as the main web container for our > > > enterprise site. > > > > > > > > > --- > > This SF.Net email sponsored by: Free pre-built > ASP.NET sites including > > > Data Reports, E-commerce, Portals, and Forums are > available now. > > Download today and enter to win an XBOX or Visual > Studio .NET. > > > http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01 > /01 > > ___ > > JBoss-user mailing list > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > > > > --- > This SF.Net email sponsored by: Free pre-built > ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are > available now. > Download today and enter to win an XBOX or Visual > Studio .NET. > http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01 > /01 > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > --- > This SF.Net email sponsored by: Free pre-built > ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are > available now. > Download today and enter to win an XBOX or Visual > Studio .NET. > http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Jetty vs Tomcat
So if you put the compiled JSP pages in your WAR's WEB-INF/classes then Tomcat will use those instead of compiling the JSP pages? -Original Message- From: Scott M Stark [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 06, 2003 1:23 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] Jetty vs Tomcat Then do the precompile as part of your build, or load each jsp page on startup. Attached is a simply ant script to precompile the jsp pages in the jmx-console.war of a JBoss/Tomcat dist. -- Scott Stark Chief Technology Officer JBoss Group, LLC Rod Macpherson wrote: > I agree this needs clarification and we do not have any > container-specific features so it boils down to which one JBoss > determines is the least problematic in general or the most beneficial in > general. Speaking of web containers and features that are remarkable in > their absense, when deploying large webapps it can be a real burden not > being able to precompile all of the JSP pages. I have brought this up > several times and bascially got a shoulder shrug. The reason that > surprises me is that the time to compile each page during a regression > test has a material impact on the build/test/deploy cycle. This really > takes up a lot of valuable QA time because you have to go through and > hit each page individually rather than having them automatically > compiled as part of the build and deploy process. Anybody else vote for > this? > > Rod --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Jetty vs Tomcat
I agree this needs clarification and we do not have any container-specific features so it boils down to which one JBoss determines is the least problematic in general or the most beneficial in general. Speaking of web containers and features that are remarkable in their absense, when deploying large webapps it can be a real burden not being able to precompile all of the JSP pages. I have brought this up several times and bascially got a shoulder shrug. The reason that surprises me is that the time to compile each page during a regression test has a material impact on the build/test/deploy cycle. This really takes up a lot of valuable QA time because you have to go through and hit each page individually rather than having them automatically compiled as part of the build and deploy process. Anybody else vote for this? Rod -Original Message- From: Joachim Van der Auwera [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 06, 2003 7:23 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] Jetty vs Tomcat Fair enough, but the question remains. It used to be Tomcat, then changed to Jetty and now changed to Tomcat again. I can only assume this has something to do with the feature set and/or integration with JBoss. What are the differences between the two containers? Just to make sure that us users can make an informed choice between the two. Thanks for the info, Joachim - Original Message - From: "Scott M Stark" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, August 06, 2003 2:48 PM Subject: Re: [JBoss-user] July 2003 news > As stated in previous msgs on the question of Jetty, we will continue > to maintain the embedded container service. > > -- > > Scott Stark > Chief Technology Officer > JBoss Group, LLC > > > Kevin Duffey wrote: > > > Great stuff. One question, what happened to Jetty? It seemed JBoss > > moved to Jetty not too long ago, and as far as I knew Jetty was a > > better servlet/jsp/web container than Tomcat. Can you please advise > > us as to what is going on here, especially with Greg sending an > > email out indicating he and the JEtty team are no > > longer able to commit to JBoss? Did you guys decide to > > drop Jetty now? I sure would hate to see that. Jetty > > is much easier to work than Tomcat! I have chills at > > using Tomcat as the main web container for our > > enterprise site. > > > > --- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01 /01 > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01 /01 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Jetty vs Tomcat
Yes, but you have to update the web.xml mappings to use these. -- Scott Stark Chief Technology Officer JBoss Group, LLC JD Brennan wrote: So if you put the compiled JSP pages in your WAR's WEB-INF/classes then Tomcat will use those instead of compiling the JSP pages? --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Jetty vs Tomcat
Lemme look at this script and try to incorporate it by switching from jetty to tomcat and just assuming tomcat. This looks to be a more fixed target in terms of where the translated JSPs and the compiled servlets end up versus the moving target we had with Jetty. Obviously the Jasper jars in jboss-web preserve the directory structure of the source JSPs but that was definitely not the case using the version we got off the apache website. Anyhoo, I will give this a shot. Thanks! Rod -Original Message- From: Scott M Stark [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 06, 2003 1:23 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] Jetty vs Tomcat Then do the precompile as part of your build, or load each jsp page on startup. Attached is a simply ant script to precompile the jsp pages in the jmx-console.war of a JBoss/Tomcat dist. -- Scott Stark Chief Technology Officer JBoss Group, LLC Rod Macpherson wrote: > I agree this needs clarification and we do not have any > container-specific features so it boils down to which one JBoss > determines is the least problematic in general or the most beneficial > in general. Speaking of web containers and features that are > remarkable in their absense, when deploying large webapps it can be a > real burden not being able to precompile all of the JSP pages. I have > brought this up several times and bascially got a shoulder shrug. The > reason that surprises me is that the time to compile each page during > a regression test has a material impact on the build/test/deploy > cycle. This really takes up a lot of valuable QA time because you have > to go through and hit each page individually rather than having them > automatically compiled as part of the build and deploy process. > Anybody else vote for this? > > Rod --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Jetty vs Tomcat
I am building with ant and we even have a JSP compilation task that uses Jasper to compile all of the JSPs but that is only a sanity check and the results are tossed. The problem is that the Jasper compiler no longer respects the directory structure of the JSPs but rather dumps everything in a flat directory. Assuming it maintained the same hierarchy we would still have to determine ahead of time where to direct the output and what the output file names are called. Assume you are running Jetty. Jetty (or at least a particular version that I have used) will create a directory called "1" in $TMP and glue together a directory name that includes the name Jetty, the configuration name (default, minimal, banana)plus the path to the compiled JSP servlet in question. This is a bit of a moving target so having the system run the precompilation for you would be preferable. Compiled JSP that Jetty creates: /tmp/1/Jetty_banana_80__/all/your/base/are/BelongToUs$jsp.class Another point was made about knowing which pages to compile versus which are includes. That is easy to solve and in my opinion an included JSP should never have the JSP extension. Call the included file banana.jspi or banana.jspinc or what have you. You can include anything you want and your JSP compiler task can filter for .jsp files only. Also, precompiling the deployed application pages ensures that whatever tag libraries or beans that the pages use are there. -Original Message- From: Kevin Duffey [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 06, 2003 2:02 PM To: [EMAIL PROTECTED] Subject: RE: [JBoss-user] Jetty vs Tomcat I am guessing you use Ant to build your project? If so, why not compile them as part of the build? I know Ant can do this in some manner. --- Rod Macpherson <[EMAIL PROTECTED]> wrote: > I agree this needs clarification and we do not have > any > container-specific features so it boils down to > which one JBoss > determines is the least problematic in general or > the most beneficial in > general. Speaking of web containers and features > that are remarkable in > their absense, when deploying large webapps it can > be a real burden not > being able to precompile all of the JSP pages. I > have brought this up > several times and bascially got a shoulder shrug. > The reason that > surprises me is that the time to compile each page > during a regression > test has a material impact on the build/test/deploy > cycle. This really > takes up a lot of valuable QA time because you have > to go through and > hit each page individually rather than having them automatically > compiled as part of the build and deploy process. > Anybody else vote for > this? > > Rod > > -Original Message- > From: Joachim Van der Auwera > [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 06, 2003 7:23 AM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] Jetty vs Tomcat > > > Fair enough, but the question remains. > It used to be Tomcat, then changed to Jetty and now > changed to Tomcat > again. I can only assume this has something to do > with the feature set > and/or integration with JBoss. > > What are the differences between the two containers? > Just to make sure > that us users can make an informed choice between > the two. > > Thanks for the info, > Joachim > > - Original Message - > From: "Scott M Stark" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, August 06, 2003 2:48 PM > Subject: Re: [JBoss-user] July 2003 news > > > > As stated in previous msgs on the question of > Jetty, we will continue > > to maintain the embedded container service. > > > > -- > > > > Scott Stark > > Chief Technology Officer > > JBoss Group, LLC > > > > > > Kevin Duffey wrote: > > > > > Great stuff. One question, what happened to > Jetty? It seemed JBoss > > > moved to Jetty not too long ago, and as far as I > knew Jetty was a > > > better servlet/jsp/web container than Tomcat. > Can you please advise > > > us as to what is going on here, especially with > Greg sending an > > > email out indicating he and the JEtty team are > no > > > longer able to commit to JBoss? Did you guys > decide to > > > drop Jetty now? I sure would hate to see that. > Jetty > > > is much easier to work than Tomcat! I have > chills at > > > using Tomcat as the main web container for our > > > enterprise site. > > > > > > > > > --- > > This SF.Net email sponsored by: F
Re: [JBoss-user] Jetty vs Tomcat
Yes, attached are the before (web.xml) and after web.xml files for the jmx-console.war. The before is what you would find in the default dist or source tree, the after (jmxconsole-web.xml) maps the compiled servlets to the jsp URIs. JD Brennan wrote: Do you have an example of what the web.xml mappings would look like? I've checked the Tomcat docs, searched the JBoss 3.2.1 source tree and even read the web.xml DTD, but I still can't figure out how to do this. Thanks, JD http://java.sun.com/dtd/web-app_2_3.dtd";> The standard web descriptor for the html adaptor HtmlAdaptor org.jboss.jmx.adaptor.html.HtmlAdaptorServlet DisplayMBeans displayMBeans_jsp InspectMBean displayOpResult_jsp DisplayOpResult index_jsp displayMBeans_jsp displayMBeans_jsp displayOpResult_jsp displayOpResult_jsp index_jsp index_jsp inspectMBean_jsp inspectMBean_jsp displayMBeans_jsp /displayMBeans.jsp displayOpResult_jsp /displayOpResult.jsp index_jsp /index.jsp inspectMBean_jsp /inspectMBean.jsp HtmlAdaptor /HtmlAdaptor DisplayMBeans /DisplayMBeans InspectMBean /InspectMBean DisplayOpResult /DisplayOpResult index.html BASIC JBoss JMX Console JBossAdmin http://java.sun.com/dtd/web-app_2_3.dtd";> The standard web descriptor for the html adaptor HtmlAdaptor org.jboss.jmx.adaptor.html.HtmlAdaptorServlet DisplayMBeans /displayMBeans.jsp InspectMBean /inspectMBean.jsp DisplayOpResult /displayOpResult.jsp HtmlAdaptor /HtmlAdaptor DisplayMBeans /DisplayMBeans InspectMBean /InspectMBean DisplayOpResult /DisplayOpResult BASIC JBoss JMX Console JBossAdmin
RE: [JBoss-user] Jetty vs Tomcat
Do you have an example of what the web.xml mappings would look like? I've checked the Tomcat docs, searched the JBoss 3.2.1 source tree and even read the web.xml DTD, but I still can't figure out how to do this. Thanks, JD -Original Message- From: Scott M Stark [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 06, 2003 3:51 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] Jetty vs Tomcat Yes, but you have to update the web.xml mappings to use these. -- Scott Stark Chief Technology Officer JBoss Group, LLC JD Brennan wrote: > So if you put the compiled JSP pages in your WAR's WEB-INF/classes > then Tomcat will use those instead of compiling the JSP pages? > --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Jetty vs Tomcat
Then do the precompile as part of your build, or load each jsp page on startup. Attached is a simply ant script to precompile the jsp pages in the jmx-console.war of a JBoss/Tomcat dist. -- Scott Stark Chief Technology Officer JBoss Group, LLC Rod Macpherson wrote: I agree this needs clarification and we do not have any container-specific features so it boils down to which one JBoss determines is the least problematic in general or the most beneficial in general. Speaking of web containers and features that are remarkable in their absense, when deploying large webapps it can be a real burden not being able to precompile all of the JSP pages. I have brought this up several times and bascially got a shoulder shrug. The reason that surprises me is that the time to compile each page during a regression test has a material impact on the build/test/deploy cycle. This really takes up a lot of valuable QA time because you have to go through and hit each page individually rather than having them automatically compiled as part of the build and deploy process. Anybody else vote for this? Rod
Re: [JBoss-user] Jetty vs Tomcat
Fair enough, but the question remains. It used to be Tomcat, then changed to Jetty and now changed to Tomcat again. I can only assume this has something to do with the feature set and/or integration with JBoss. What are the differences between the two containers? Just to make sure that us users can make an informed choice between the two. Thanks for the info, Joachim - Original Message - From: "Scott M Stark" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, August 06, 2003 2:48 PM Subject: Re: [JBoss-user] July 2003 news > As stated in previous msgs on the question of Jetty, we will continue to > maintain the embedded container service. > > -- > > Scott Stark > Chief Technology Officer > JBoss Group, LLC > > > Kevin Duffey wrote: > > > Great stuff. One question, what happened to Jetty? It > > seemed JBoss moved to Jetty not too long ago, and as > > far as I knew Jetty was a better servlet/jsp/web > > container than Tomcat. Can you please advise us as to > > what is going on here, especially with Greg sending an > > email out indicating he and the JEtty team are no > > longer able to commit to JBoss? Did you guys decide to > > drop Jetty now? I sure would hate to see that. Jetty > > is much easier to work than Tomcat! I have chills at > > using Tomcat as the main web container for our > > enterprise site. > > > > --- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: Re: [JBoss-user] jetty vs tomcat
many thanks! I think I will try Jetty and I am now look into the document distributed with Jetty. Anyway, I think you should put the following comparision onto the JBoss download page or FAQ. regards At 01-6-18 18:15:00, you wrote: >Firstly - I am the JBoss-Jetty maintainer and my mate >Greg is Jetty's author - so take everything I say with >a pinch of salt. > >If you stick to JSDK 2.2 and JSP 1.1 you _SHOULD_ >(please let me know if you don't) find that the WAR >part of your EARs deploys and runs fine in either >web-container. This is the idea of having standard >APIs. > >Those are the similarities. > >These are the differences: > >1. Jetty serves both static and dynamic content via >the same infrastructure. AFAIK you need Tomcat AND >Apache in order to otherwise achieve this. > >2. Jetty is designed to be small, lightweight, simple >and embeddable. Apache and TomCat have a larger >footprint. > >3. Apache is de-facto industry standard, with an >enormous user community, whereas Jetty is not. TomCat >also has a far bigger user community than Jetty. > >4. Internal Jetty components are exposed to JBoss' JMX >Agent. AFAIK this is not YET the case with TomCat, but >probably not of much practical use ! > > >5. I believe, although I have no substantiating >evidence, that using Jetty MAY give you a higher >throughput. This is due to it's emphasis on simplicity >and lightweightedness. I am sure that TomCat is >probably demonstrably more functional. > > >In conclusion, there is no clear winner - otherwise >one of us would have thrown in the towel. We represent >different approaches and ideologies. > >If you are not particularly worried about serving high >volume static pages,would benefit from the simplicity >of running your entire setup from within one Java >process and are not worried by the fact that the rest >of the world has not chosen the same path as you - try >Jetty (the mailing list is actually very responsive). >If not go with Tomcat. > >If you are not worried about static content, try both >and post your comparisons to this list so we may all >benefit from your experience. > >Greg may want to add a little here... > >Hope that helps, > > > >Jules > > >--- Sky Yin <[EMAIL PROTECTED]> wrote: > hi :^) >> I am a new comer to JBoss. I notice that JBoss >> releases with alternative two servlet/jsp engine: >> jetty and tomcat. Can anyone make a comparation >> between them? How can I choose from? >> >> regards >> >> >> ___ >> JBoss-user mailing list >> [EMAIL PROTECTED] >> >http://lists.sourceforge.net/lists/listinfo/jboss-user > > > >Do You Yahoo!? >Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk >or your free @yahoo.ie address at http://mail.yahoo.ie > >___ >JBoss-user mailing list >[EMAIL PROTECTED] >http://lists.sourceforge.net/lists/listinfo/jboss-user > ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] jetty vs tomcat
Thanks Guys,
It was getting a bit lonely out there .!!
Jules
Torsten Terp wrote:
> > >
> > > Oh, come on! If you wanna be flamed, you can't go and _qualify_ your
> > > assertions ('no ... evidence ...' '... MAY ...') 8^})
> >
> > We have run our test scripts against our app running under both jBoss/Jetty
> > and jBoss/Tomcat. We have yet to take actual measurements, but watching the
> > looping scripts fly by shows us that Jetty is like a Porsch Boxter while
> > Tomcat more rsembles a Chevy Nova...
> >
> > Someday we'll take the trouble to actually measure it and I'll post the
> > resumts.
> >
> > Jim
> >
>
> Exactly our experience too, we have been running both, but the differrence
> in performance was so obvious, that we havent yet felt the need to make any
> measurements. You should at least do yourself the favour and try out Jetty!
>
> ^terp
>
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] jetty vs tomcat
"danch (Dan Christopherson)" wrote:
Don't believe my bare-faced and self-proclaimed bigotry - suck it and
see - then tell us all how it tasted.
Jules
> Julian Gosnell wrote:
>
> > Firstly - I am the JBoss-Jetty maintainer and my mate
> > Greg is Jetty's author - so take everything I say with
> > a pinch of salt.
> >
> > 1. Jetty serves both static and dynamic content via
> > the same infrastructure. AFAIK you need Tomcat AND
> > Apache in order to otherwise achieve this.
>
> Not completely true - Tomcat can serve static content, it's just slow
> enought that most people seem to assume they need apache.
>
> >
> > 2. Jetty is designed to be small, lightweight, simple
> > and embeddable. Apache and TomCat have a larger
> > footprint.
> >
> > 3. Apache is de-facto industry standard, with an
> > enormous user community, whereas Jetty is not. TomCat
> > also has a far bigger user community than Jetty.
>
> Isn't Tomcat the reference implementation these days?
>
> >
> >
> > 5. I believe, although I have no substantiating
> > evidence, that using Jetty MAY give you a higher
> > throughput. This is due to it's emphasis on simplicity
> > and lightweightedness. I am sure that TomCat is
> > probably demonstrably more functional.
> >
>
> Oh, come on! If you wanna be flamed, you can't go and _qualify_ your
> assertions ('no ... evidence ...' '... MAY ...') 8^})
>
> -danch
>
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] jetty vs tomcat
> >
> > Oh, come on! If you wanna be flamed, you can't go and _qualify_ your
> > assertions ('no ... evidence ...' '... MAY ...') 8^})
>
> We have run our test scripts against our app running under both jBoss/Jetty
> and jBoss/Tomcat. We have yet to take actual measurements, but watching the
> looping scripts fly by shows us that Jetty is like a Porsch Boxter while
> Tomcat more rsembles a Chevy Nova...
>
> Someday we'll take the trouble to actually measure it and I'll post the
> resumts.
>
> Jim
>
Exactly our experience too, we have been running both, but the differrence
in performance was so obvious, that we havent yet felt the need to make any
measurements. You should at least do yourself the favour and try out Jetty!
^terp
___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] jetty vs tomcat
--On Monday, June 18, 2001 12:26 PM -0500 "danch (Dan Christopherson)"
<[EMAIL PROTECTED]> wrote:
>>
>> 5. I believe, although I have no substantiating
>> evidence, that using Jetty MAY give you a higher
>> throughput. This is due to it's emphasis on simplicity
>> and lightweightedness. I am sure that TomCat is
>> probably demonstrably more functional.
>>
>
>
> Oh, come on! If you wanna be flamed, you can't go and _qualify_ your
> assertions ('no ... evidence ...' '... MAY ...') 8^})
We have run our test scripts against our app running under both jBoss/Jetty
and jBoss/Tomcat. We have yet to take actual measurements, but watching the
looping scripts fly by shows us that Jetty is like a Porsch Boxter while
Tomcat more rsembles a Chevy Nova...
Someday we'll take the trouble to actually measure it and I'll post the
resumts.
Jim
___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] jetty vs tomcat
Julian Gosnell wrote:
> Firstly - I am the JBoss-Jetty maintainer and my mate
> Greg is Jetty's author - so take everything I say with
> a pinch of salt.
>
> 1. Jetty serves both static and dynamic content via
> the same infrastructure. AFAIK you need Tomcat AND
> Apache in order to otherwise achieve this.
Not completely true - Tomcat can serve static content, it's just slow
enought that most people seem to assume they need apache.
>
> 2. Jetty is designed to be small, lightweight, simple
> and embeddable. Apache and TomCat have a larger
> footprint.
>
> 3. Apache is de-facto industry standard, with an
> enormous user community, whereas Jetty is not. TomCat
> also has a far bigger user community than Jetty.
Isn't Tomcat the reference implementation these days?
>
>
> 5. I believe, although I have no substantiating
> evidence, that using Jetty MAY give you a higher
> throughput. This is due to it's emphasis on simplicity
> and lightweightedness. I am sure that TomCat is
> probably demonstrably more functional.
>
Oh, come on! If you wanna be flamed, you can't go and _qualify_ your
assertions ('no ... evidence ...' '... MAY ...') 8^})
-danch
___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] jetty vs tomcat
Firstly - I am the JBoss-Jetty maintainer and my mate Greg is Jetty's author - so take everything I say with a pinch of salt. If you stick to JSDK 2.2 and JSP 1.1 you _SHOULD_ (please let me know if you don't) find that the WAR part of your EARs deploys and runs fine in either web-container. This is the idea of having standard APIs. Those are the similarities. These are the differences: 1. Jetty serves both static and dynamic content via the same infrastructure. AFAIK you need Tomcat AND Apache in order to otherwise achieve this. 2. Jetty is designed to be small, lightweight, simple and embeddable. Apache and TomCat have a larger footprint. 3. Apache is de-facto industry standard, with an enormous user community, whereas Jetty is not. TomCat also has a far bigger user community than Jetty. 4. Internal Jetty components are exposed to JBoss' JMX Agent. AFAIK this is not YET the case with TomCat, but probably not of much practical use ! 5. I believe, although I have no substantiating evidence, that using Jetty MAY give you a higher throughput. This is due to it's emphasis on simplicity and lightweightedness. I am sure that TomCat is probably demonstrably more functional. In conclusion, there is no clear winner - otherwise one of us would have thrown in the towel. We represent different approaches and ideologies. If you are not particularly worried about serving high volume static pages,would benefit from the simplicity of running your entire setup from within one Java process and are not worried by the fact that the rest of the world has not chosen the same path as you - try Jetty (the mailing list is actually very responsive). If not go with Tomcat. If you are not worried about static content, try both and post your comparisons to this list so we may all benefit from your experience. Greg may want to add a little here... Hope that helps, Jules --- Sky Yin <[EMAIL PROTECTED]> wrote: > hi :^) > I am a new comer to JBoss. I notice that JBoss > releases with alternative two servlet/jsp engine: > jetty and tomcat. Can anyone make a comparation > between them? How can I choose from? > > regards > > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Jetty vs. Tomcat
Sounds great, Jules! I have been developing with Tomcat buy my hope was to deploy in production with Jetty, since its much slimmer. I'll try it as soon as you release it and thanks! Jim --On Tuesday, April 24, 2001 9:58 AM +0100 Julian Gosnell <[EMAIL PROTECTED]> wrote: > This sounds like the ENC stuff. > > I am putting it into JBossJetty at the moment, expect > it in the next release along with a complete > integration of all Jetty JMX subcomponents. > > ETA - two or three weeks... > > Jules > > --- Jim Archer <[EMAIL PROTECTED]> wrote: > Actually, I > tried Jetty (as part of the jBoss 2.2.1 >> bundle) just the other >> day. It installed fine but when I deployed my EAR I >> got a bunch of errors >> complaining about JNDI. >> >> When I ran my app, I got a bunch of maning >> exceptions. I have not had time >> to look into this further, but it did make me wonder >> if Jetty is fully >> intergrated, like Tomcat is. I would have expected >> the very same EAR to run >> just the same under either Jetty or Tomcat... >> >> Jim >> >> --On Friday, April 20, 2001 1:50 AM -0500 danch >> <[EMAIL PROTECTED]> wrote: >> >> > Alternatively, Tomcat is the reference >> implementation. Jetty is >> > lightweight and fast. >> > >> > The only other thing is that (judging from traffic >> analysis of these >> > mailing lists) Integration of Tomcat with JBoss is >> better tested. (Jetty >> > users, feel free to argue) >> > >> > -danch >> > >> > Alvin Yap wrote: >> > >> >> Tomcat is more robust and extensible. Jetty is >> lightweight and fast. >> >> >> >> Alvin >> >> >> >> Jason Dillon wrote: >> >> >> >> >> >>> Does anyone have any opinions as to which >> contain is more robust, >> >>> easier to use and such? >> >>> >> >>> --jason >> >>> >> >>> ___ >> >>> JBoss-user mailing list >> >>> [EMAIL PROTECTED] >> >>> >> > http://lists.sourceforge.net/lists/listinfo/jboss-user >> >> >> >> >> >> >> >> ___ >> >> JBoss-user mailing list >> >> [EMAIL PROTECTED] >> >> >> > http://lists.sourceforge.net/lists/listinfo/jboss-user >> > >> > >> > >> > ___ >> > JBoss-user mailing list >> > [EMAIL PROTECTED] >> > >> > http://lists.sourceforge.net/lists/listinfo/jboss-user >> >> >> >> >> I shall be telling this with a sigh >> Somewhere ages and ages hence: >> Two roads diverged in a wood, and I - >> I took the one less traveled by, >> And that has made all the difference. >> >> - Robert Frost, 1916 >> >> >> ___ >> JBoss-user mailing list >> [EMAIL PROTECTED] >> > http://lists.sourceforge.net/lists/listinfo/jboss-user > > > > Do You Yahoo!? > Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk > or your free @yahoo.ie address at http://mail.yahoo.ie > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user I shall be telling this with a sigh Somewhere ages and ages hence: Two roads diverged in a wood, and I - I took the one less traveled by, And that has made all the difference. - Robert Frost, 1916 ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Jetty vs. Tomcat
I just downloaded the latest integrated versions and have had no problems utilizing the same .ear file I used with the Tomcat integration. (That was the JBoss 2.2.1 w/ Jetty configuration). Robert Jim Archer <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 04/23/2001 03:04 PM Please respond to jboss-user To: [EMAIL PROTECTED] cc: Subject: Re: [JBoss-user] Jetty vs. Tomcat Actually, I tried Jetty (as part of the jBoss 2.2.1 bundle) just the other day. It installed fine but when I deployed my EAR I got a bunch of errors complaining about JNDI. When I ran my app, I got a bunch of maning exceptions. I have not had time to look into this further, but it did make me wonder if Jetty is fully intergrated, like Tomcat is. I would have expected the very same EAR to run just the same under either Jetty or Tomcat... Jim --On Friday, April 20, 2001 1:50 AM -0500 danch <[EMAIL PROTECTED]> wrote: > Alternatively, Tomcat is the reference implementation. Jetty is > lightweight and fast. > > The only other thing is that (judging from traffic analysis of these > mailing lists) Integration of Tomcat with JBoss is better tested. (Jetty > users, feel free to argue) > > -danch > > Alvin Yap wrote: > >> Tomcat is more robust and extensible. Jetty is lightweight and fast. >> >> Alvin >> >> Jason Dillon wrote: >> >> >>> Does anyone have any opinions as to which contain is more robust, >>> easier to use and such? >>> >>> --jason >>> >>> ___ >>> JBoss-user mailing list >>> [EMAIL PROTECTED] >>> http://lists.sourceforge.net/lists/listinfo/jboss-user >> >> >> >> ___ >> JBoss-user mailing list >> [EMAIL PROTECTED] >> http://lists.sourceforge.net/lists/listinfo/jboss-user > > > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user I shall be telling this with a sigh Somewhere ages and ages hence: Two roads diverged in a wood, and I - I took the one less traveled by, And that has made all the difference. - Robert Frost, 1916 ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Jetty vs. Tomcat
This sounds like the ENC stuff. I am putting it into JBossJetty at the moment, expect it in the next release along with a complete integration of all Jetty JMX subcomponents. ETA - two or three weeks... Jules --- Jim Archer <[EMAIL PROTECTED]> wrote: > Actually, I tried Jetty (as part of the jBoss 2.2.1 > bundle) just the other > day. It installed fine but when I deployed my EAR I > got a bunch of errors > complaining about JNDI. > > When I ran my app, I got a bunch of maning > exceptions. I have not had time > to look into this further, but it did make me wonder > if Jetty is fully > intergrated, like Tomcat is. I would have expected > the very same EAR to run > just the same under either Jetty or Tomcat... > > Jim > > --On Friday, April 20, 2001 1:50 AM -0500 danch > <[EMAIL PROTECTED]> wrote: > > > Alternatively, Tomcat is the reference > implementation. Jetty is > > lightweight and fast. > > > > The only other thing is that (judging from traffic > analysis of these > > mailing lists) Integration of Tomcat with JBoss is > better tested. (Jetty > > users, feel free to argue) > > > > -danch > > > > Alvin Yap wrote: > > > >> Tomcat is more robust and extensible. Jetty is > lightweight and fast. > >> > >> Alvin > >> > >> Jason Dillon wrote: > >> > >> > >>> Does anyone have any opinions as to which > contain is more robust, > >>> easier to use and such? > >>> > >>> --jason > >>> > >>> ___ > >>> JBoss-user mailing list > >>> [EMAIL PROTECTED] > >>> > http://lists.sourceforge.net/lists/listinfo/jboss-user > >> > >> > >> > >> ___ > >> JBoss-user mailing list > >> [EMAIL PROTECTED] > >> > http://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > > > > ___ > > JBoss-user mailing list > > [EMAIL PROTECTED] > > > http://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > I shall be telling this with a sigh > Somewhere ages and ages hence: > Two roads diverged in a wood, and I - > I took the one less traveled by, > And that has made all the difference. > > - Robert Frost, 1916 > > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Jetty vs. Tomcat
Actually, I tried Jetty (as part of the jBoss 2.2.1 bundle) just the other day. It installed fine but when I deployed my EAR I got a bunch of errors complaining about JNDI. When I ran my app, I got a bunch of maning exceptions. I have not had time to look into this further, but it did make me wonder if Jetty is fully intergrated, like Tomcat is. I would have expected the very same EAR to run just the same under either Jetty or Tomcat... Jim --On Friday, April 20, 2001 1:50 AM -0500 danch <[EMAIL PROTECTED]> wrote: > Alternatively, Tomcat is the reference implementation. Jetty is > lightweight and fast. > > The only other thing is that (judging from traffic analysis of these > mailing lists) Integration of Tomcat with JBoss is better tested. (Jetty > users, feel free to argue) > > -danch > > Alvin Yap wrote: > >> Tomcat is more robust and extensible. Jetty is lightweight and fast. >> >> Alvin >> >> Jason Dillon wrote: >> >> >>> Does anyone have any opinions as to which contain is more robust, >>> easier to use and such? >>> >>> --jason >>> >>> ___ >>> JBoss-user mailing list >>> [EMAIL PROTECTED] >>> http://lists.sourceforge.net/lists/listinfo/jboss-user >> >> >> >> ___ >> JBoss-user mailing list >> [EMAIL PROTECTED] >> http://lists.sourceforge.net/lists/listinfo/jboss-user > > > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user I shall be telling this with a sigh Somewhere ages and ages hence: Two roads diverged in a wood, and I - I took the one less traveled by, And that has made all the difference. - Robert Frost, 1916 ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Jetty vs. Tomcat
> Does anyone have any opinions as to which contain is more robust, > easier to use and such? There was a slashdot story about Tomcat over the weekend which sparked a whole bunch of posts about just this topic. As always, take /. with a grain of salt... ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Jetty vs. Tomcat
Alternatively, Tomcat is the reference implementation. Jetty is lightweight and fast. The only other thing is that (judging from traffic analysis of these mailing lists) Integration of Tomcat with JBoss is better tested. (Jetty users, feel free to argue) -danch Alvin Yap wrote: > Tomcat is more robust and extensible. Jetty is lightweight and fast. > > Alvin > > Jason Dillon wrote: > > >> Does anyone have any opinions as to which contain is more robust, easier to >> use and such? >> >> --jason >> >> ___ >> JBoss-user mailing list >> [EMAIL PROTECTED] >> http://lists.sourceforge.net/lists/listinfo/jboss-user > > > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Jetty vs. Tomcat
Tomcat is more robust and extensible. Jetty is lightweight and fast. Alvin Jason Dillon wrote: > Does anyone have any opinions as to which contain is more robust, easier to > use and such? > > --jason > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
