David, Jeff, I tried setting J2EEApplication (and J2EEServer) for WebModules. I set the values on o.a.c.StandardContext from GeronimoStandardContext.setContextProperties(). The servlets had the correct setting for J2EEApplication and J2EEServer. Everything seems to work fine, except that at
Hi All,In response to the following issue raised by David Jencks, I am thinking of changing the the implementation of Servlet and ServletStats (required by jsr77) for tomcat. The older implementation (GERONIMO-1035) will have 2 of each servlets! I am thinking of a ServletsHolder, which will be a
On May 7, 2006, at 6:11 PM, Davanum Srinivas wrote:
David,
Could u please post a message on [EMAIL PROTECTED], let's see if we can
get someone there to push out a release for us.
Thanks for the suggestion Dims, I think we finally have some evidence
that my synchronization patch to fix an
On May 7, 2006, at 6:56 PM, anita kulshreshtha wrote:
I have a similar concern with *Connectors. The attributes of the
connectors should be set only via GBeans. But using Jconsole one could
easily modify the attributes of the tomcat connector Mbeans, thereby
creating an inconsistent state
Comments inline..
--- David Jencks [EMAIL PROTECTED] wrote:
On May 7, 2006, at 6:56 PM, anita kulshreshtha wrote:
I have a similar concern with *Connectors. The attributes of
the
connectors should be set only via GBeans. But using Jconsole one
could
easily modify the attributes
David,
Could u please post a message on [EMAIL PROTECTED], let's see if we can
get someone there to push out a release for us.
thanks,
dims
On 5/7/06, David Jencks [EMAIL PROTECTED] wrote:
I've run into a couple fair-sized problems with the tomcat
integration and I'm not sure how to proceed.
I have a similar concern with *Connectors. The attributes of the
connectors should be set only via GBeans. But using Jconsole one could
easily modify the attributes of the tomcat connector Mbeans, thereby
creating an inconsistent state and unpredictable behavior. It is very
easy to mistake one
