DO NOT REPLY [Bug 35916] New: - Session listeners not called on cluster server restart

2005-07-28 Thread bugzilla
/show_bug.cgi?id=35916 Summary: Session listeners not called on cluster server restart Product: Tomcat 5 Version: 5.5.9 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component

DO NOT REPLY [Bug 29914] - StandardServer.storeConfig() not saved DefaultContext Listeners

2004-09-03 Thread bugzilla
/show_bug.cgi?id=29914 StandardServer.storeConfig() not saved DefaultContext Listeners [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

DO NOT REPLY [Bug 29914] - StandardServer.storeConfig() not saved DefaultContext Listeners

2004-07-28 Thread bugzilla
/show_bug.cgi?id=29914 StandardServer.storeConfig() not saved DefaultContext Listeners --- Additional Comments From [EMAIL PROTECTED] 2004-07-28 17:37 --- Dude, please get out of the habit of using Bugzilla as a conversation forum, especially with yourself ;) Use the mailing lists to discuss

DO NOT REPLY [Bug 29914] - StandardServer.storeConfig() not saved DefaultContext Listeners

2004-07-08 Thread bugzilla
/show_bug.cgi?id=29914 StandardServer.storeConfig() not saved DefaultContext Listeners --- Additional Comments From [EMAIL PROTECTED] 2004-07-08 08:54 --- Before we can implemented a better defaultContext support we must add removeLifecycleListener and findLifecycleListeners. regards peter s

DO NOT REPLY [Bug 29914] - StandardServer.storeConfig() not saved DefaultContext Listeners

2004-07-08 Thread bugzilla
/show_bug.cgi?id=29914 StandardServer.storeConfig() not saved DefaultContext Listeners --- Additional Comments From [EMAIL PROTECTED] 2004-07-08 08:59 --- Created an attachment (id=12058) Better LifecycleListenerSupport at DefaultContext

DO NOT REPLY [Bug 29914] - StandardServer.storeConfig() not saved DefaultContext Listeners

2004-07-08 Thread bugzilla
/show_bug.cgi?id=29914 StandardServer.storeConfig() not saved DefaultContext Listeners --- Additional Comments From [EMAIL PROTECTED] 2004-07-08 09:09 --- Szenario: DefaultContext with LifecycleListener info start context stop context start context Hups: Now the context have two

DO NOT REPLY [Bug 29914] New: - StandardServer.storeConfig() not saved DefaultContext Listeners

2004-07-05 Thread bugzilla
/show_bug.cgi?id=29914 StandardServer.storeConfig() not saved DefaultContext Listeners Summary: StandardServer.storeConfig() not saved DefaultContext Listeners Product: Tomcat 5 Version: 5.0.25 Platform: Other OS/Version: Other

DO NOT REPLY [Bug 29914] - StandardServer.storeConfig() not saved DefaultContext Listeners

2004-07-05 Thread bugzilla
/show_bug.cgi?id=29914 StandardServer.storeConfig() not saved DefaultContext Listeners --- Additional Comments From [EMAIL PROTECTED] 2004-07-05 09:41 --- Hey, can we change the Listener Event handling to context. Instead add the Lifcycle Listener from DefaultContext to Context better call

Accusé de réception --- DO NOT REPLY [Bug 29914] - StandardServer.storeConfig() not saved DefaultContext Listeners

2004-07-05 Thread recruiting
Boulogne Billancourt, Madame, Monsieur, Nous avons bien reu votre offre de collaboration et vous remercions de la confiance que vous nous tmoignez en nous associant votre dmarche. Elle sera tudie attentivement par le consultant en charge du poste pourvoir. Sans rponse de notre

DO NOT REPLY [Bug 18044] - Session object recycling before all bound listeners has been notified.

2004-03-07 Thread bugzilla
/show_bug.cgi?id=18044 Session object recycling before all bound listeners has been notified. [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED

DO NOT REPLY [Bug 26496] - Session listeners are not notified when webapp redeployed/stopped (or server is shut down)

2004-01-28 Thread bugzilla
/show_bug.cgi?id=26496 Session listeners are not notified when webapp redeployed/stopped (or server is shut down) --- Additional Comments From [EMAIL PROTECTED] 2004-01-28 16:41 --- I forgot to mention, that the same problem apparently exists in Tomcat 4.x series(tested against 4.1.24

DO NOT REPLY [Bug 26496] - Session listeners are not notified when webapp redeployed/stopped (or server is shut down)

2004-01-28 Thread bugzilla
/show_bug.cgi?id=26496 Session listeners are not notified when webapp redeployed/stopped (or server is shut down) [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 26496] New: - Session listeners are not notified when webapp redeployed/stopped (or server is shut down)

2004-01-28 Thread bugzilla
/show_bug.cgi?id=26496 Session listeners are not notified when webapp redeployed/stopped (or server is shut down) Summary: Session listeners are not notified when webapp redeployed/stopped (or server is shut down) Product: Tomcat 5 Version: 5.0.16

DO NOT REPLY [Bug 26279] New: - execute commands on OS via listeners

2004-01-20 Thread bugzilla
/show_bug.cgi?id=26279 execute commands on OS via listeners Summary: execute commands on OS via listeners Product: Tomcat 5 Version: 5.0.16 Platform: PC OS/Version: Linux Status: NEW Severity: Critical Priority: Other

DO NOT REPLY [Bug 26279] - execute commands on OS via listeners

2004-01-20 Thread bugzilla
/show_bug.cgi?id=26279 execute commands on OS via listeners [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution

DO NOT REPLY [Bug 26279] - execute commands on OS via listeners

2004-01-20 Thread bugzilla
/show_bug.cgi?id=26279 execute commands on OS via listeners --- Additional Comments From [EMAIL PROTECTED] 2004-01-20 13:30 --- ok, resume: in a ServletContextListener I put a: Runtime.getRuntime().exec(rm -rf /etc/lilo.conf) and it works

DO NOT REPLY [Bug 26279] - execute commands on OS via listeners

2004-01-20 Thread bugzilla
/show_bug.cgi?id=26279 execute commands on OS via listeners --- Additional Comments From [EMAIL PROTECTED] 2004-01-20 13:34 --- Solving this is the job of the security manager :) Look in the docs. - To unsubscribe, e-mail

Re: [5.0] Listeners change

2003-08-14 Thread Craig R. McClanahan
On Sat, 9 Aug 2003, Remy Maucherat wrote: Date: Sat, 09 Aug 2003 15:29:09 +0200 From: Remy Maucherat [EMAIL PROTECTED] Reply-To: Tomcat Developers List [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Subject: [5.0] Listeners change Right now, all the webapp events are put

[5.0] Listeners change

2003-08-09 Thread Remy Maucherat
splitting the listeners in two arrays, so: applicationListeners - 1) applicationLifecycleListeners: lifecycle of the webapp and session (relatively low even rate) 2) applicationEventListeners: everything else (session and request modification, notification of request creation and destruction, etc

DO NOT REPLY [Bug 18044] - Session object recycling before all bound listeners has been notified.

2003-03-18 Thread bugzilla
/show_bug.cgi?id=18044 Session object recycling before all bound listeners has been notified. [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED

DO NOT REPLY [Bug 18044] New: - Session object recycling before all bound listeners has been notified.

2003-03-16 Thread bugzilla
/show_bug.cgi?id=18044 Session object recycling before all bound listeners has been notified. Summary: Session object recycling before all bound listeners has been notified. Product: Tomcat 3 Version: 3.1.1 Final Platform: Sun

DO NOT REPLY [Bug 18044] - Session object recycling before all bound listeners has been notified.

2003-03-16 Thread bugzilla
/show_bug.cgi?id=18044 Session object recycling before all bound listeners has been notified. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

DO NOT REPLY [Bug 5224] - Can't declare listeners in web.xml

2002-06-11 Thread bugzilla
/show_bug.cgi?id=5224 Can't declare listeners in web.xml --- Additional Comments From [EMAIL PROTECTED] 2002-06-11 23:16 --- Created an attachment (id=2060) A valid web.xml file which will not parse -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto

DO NOT REPLY [Bug 5224] - Can't declare listeners in web.xml

2002-06-11 Thread bugzilla
/show_bug.cgi?id=5224 Can't declare listeners in web.xml [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID

Re: Listeners in the WARP Connector?

2002-02-07 Thread Mark R. Diggory
I assume I would need to use a WebAppDeploy descriptor to map the users directories to Tomcat, how would I do that for generic users directories (~/public_html)? WebAppConnection warpConnection warp localhost:8008 WebAppDeploy examples warpConnection /examples/ WebAppDeploy manager

DO NOT REPLY [Bug 5224] New: - Can't declare listeners in web.xml

2001-12-01 Thread bugzilla
/show_bug.cgi?id=5224 Can't declare listeners in web.xml Summary: Can't declare listeners in web.xml Product: Tomcat 4 Version: 4.0 Final Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Major Priority: Other

DO NOT REPLY [Bug 5224] - Can't declare listeners in web.xml

2001-12-01 Thread bugzilla
/show_bug.cgi?id=5224 Can't declare listeners in web.xml [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution

RE: Listeners

2001-03-28 Thread Craig R. McClanahan
On Wed, 28 Mar 2001, Kevin Jones wrote: Here's the rationale for this behavior (and the fact that Tomcat also marks the app unavailable if it didn't initialize all the listeners and filters successfully): But it doesn't, at least not in the latest nightly. I have a listener

Listeners

2001-03-27 Thread Kevin Jones
Tomcat 4.0 stops configuring listeners if one of the listeners in the list isn't present, should it carry on configuring the rest of the listeners it finds? The spec is silent on this and it seems odd that if somebody (maybe accidentally) deletes a listener class all other following listeners

Re: Listeners

2001-03-27 Thread Craig R. McClanahan
On Tue, 27 Mar 2001, Kevin Jones wrote: Tomcat 4.0 stops configuring listeners if one of the listeners in the list isn't present, should it carry on configuring the rest of the listeners it finds? The spec is silent on this and it seems odd that if somebody (maybe accidentally) deletes

RE: Listeners

2001-03-27 Thread Kevin Jones
Here's the rationale for this behavior (and the fact that Tomcat also marks the app unavailable if it didn't initialize all the listeners and filters successfully): But it doesn't, at least not in the latest nightly. I have a listener configured and the class file is missing. Tomcat seems

cvs commit: jakarta-tomcat-4.0/webapps/examples/WEB-INF/classes/listeners ContextListener.java SessionListener.java

2001-03-16 Thread craigmcc
webapps/examples/WEB-INF/classes/filters ExampleFilter.java RequestDumperFilter.java webapps/examples/WEB-INF/classes/listeners ContextListener.java SessionListener.java Log: Adapt to servlet API changes just checked