Hi - I think I am seriously missing something here ...
That's my problem (talking tomcat 5.5.20 here)
Ingredients:
a) A business object (think it large)
b) A Jsp tag which references the business object (i.e. spring message tag)
c) A Jsp page containing the tag
With default config tomcat will
Try this in your web.xml:
jsp
org.apache.jasper.servlet.JspServlet
fork
false
xpoweredBy
false
tagpoolClassName
org.apache.jasper.runtime.PerThreadTagHandlerPo
ls event.close() (no exception)
Wait a bit
9. Keep alive timeout -> END
I know that you can just wrap the event object into some facade and keep
track of its state to prevent all this. It just whished it would behave it
bit different. And whishes are free right?
Filip Hanik - Dev Lists wro
nd to the connection life cycle. You get an END (or ERROR etc)
when the connection gets closed. But when you are writing something that
still looks like a servlet you would expect that the event life cycle is
bound to the request / response model. As soon as the response is closed you
would expect a
Hi this post is a follow up from
http://issues.apache.org/bugzilla/show_bug.cgi?id=42198 where this post does
not belong.
I want to find out if my understanding of the comet api in tomcat is right
concerning how connections are handled and event are triggered. I have a
very simple test webapp whi
