Looks like Jetty in JBoss 3.0 (perhaps 3.1 too) will start servicing requests
before a web application has been fully deployed, leaving the deployment and
the jetty in a very odd state of funk where nothing works.
--jason
___
Don't
PROTECTED]
Subject: [JBoss-dev] JBoss 3.0 and Jetty
Marc,
I'm trying to gauge requirements for Jetty within a
JBoss-3 context.
This is what I have figured so far:
1. JettyService needs to be delivered as a self
contained SAR. So it can be hot-deployed onto a JBoss
node. My
Marc,
I'm trying to gauge requirements for Jetty within a
JBoss-3 context.
This is what I have figured so far:
1. JettyService needs to be delivered as a self
contained SAR. So it can be hot-deployed onto a JBoss
node. My major concern here is whether the SAR is run
packed/unpacked. Unpacked
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
Julian Gosnell
Sent: Friday, August 31, 2001 7:18 AM
To: marc fleury
Cc: Greg Wilkins; [EMAIL PROTECTED]
Subject: [JBoss-dev] JBoss 3.0 and Jetty
Marc,
I'm trying to gauge requirements
