Well in struts you could always extend the RequestProcessor and wrap the processActionPerform, which could do the thread notify.
The problem I have is that the javassist part of the integration of hivemind can't find the interface. It seems it may be a classloading thing, but haven't figured out exactly what it might be. I am almost wondering if it makes sense to have a preprocessor before you deploy a hivemind app that does the byte code manipulation, instead of a runtime? I am running under weblogic 8.1. So not sure if it works under tomcat or resin, but could try that out. > Put the jars into WEB-INF/lib > > Have a servlet initialize the registry. > > That's something that's pretty missing; a servlet filter that would construct the registry and take > care of the end-of-request call to the ThreadNotifier. > > -- > Howard M. Lewis Ship > Creator, Tapestry: Java Web Components > http://jakarta.apache.org/tapestry > http://jakarta.apache.org/commons/sandbox/hivemind/ > http://javatapestry.blogspot.com > > > -----Original Message----- > > From: Dan Marchant [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, October 15, 2003 4:51 PM > > To: Howard M. Lewis Ship [EMAIL PROTECTED] > > Cc: [EMAIL PROTECTED] > > Subject: Best way to deploy hivemind in a web application > > > > > > > > What is the best way to deploy Hivemind in a web application? > > > > Thanks > > > > Dan > > > > -------------------------------------------------------------------- - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
