:[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
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
]
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
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
[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
: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
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
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
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
]
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
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
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.
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
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
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
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
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
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
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
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
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]
21 matches
Mail list logo
