Scott Anderson wrote:
I was not as clear as I could have been. I was
referring to a problem Tomcat was having preserving
portlet application sessions so that portlets within
the same portlet application could share data and find
the right application context. This problem was
related to Tomcat not
Scott Anderson wrote:
I built a minimal war and ran into deployment issues
with both Jetty and Tomcat...
Jetty
-
In my first attempt I noticed that Jetty was ignoring
the context name I had specified in
META-INF/context.xml and used the name of the war file
instead.
I don't think we support
On Thu, Mar 31, 2005 at 02:46:32PM -0800, Scott Anderson wrote:
Deployment failed
Server reports: No deployer present in kernel
I use the distribute command to deploy my application and get this
error if there's an instance of Geronimo running when I run the
deployer. Not sure whether it
David Jencks wrote:
In my first attempt I noticed that Jetty was
ignoring
the context name I had specified in
META-INF/context.xml and used the name of the war
file
instead.
We ignore all jetty-specific deployment info.
It turns out that this is a Tomcat specific mechanism
for specifying
On Apr 1, 2005, at 10:33 AM, Scott Anderson wrote:
David Jencks wrote:
In my first attempt I noticed that Jetty was
ignoring
the context name I had specified in
META-INF/context.xml and used the name of the war
file
instead.
We ignore all jetty-specific deployment info.
It turns out that this is a
