Ingo,
What you wrote here is of interest to me:
> (Note that the latter way is very easy, but it is generally
> bad practise to
> open HTTP connections from within a servlet container to a
> servlet in the
> same container. In systems under high load, the
> EcsServletElement sould
> only be used with remote servlets.)
Isn't that what TurbineJspService does with a RequestDispatcher?
This implies that the current Jetspeed/JSP impl. is 'bad practice'.
Is this subject covered in the servlet spec?
Could you point me to some sources on this subject?
I'd like to learn more about the reasons why this is bad practice.
If you remember, last week I posted a message about the Jetspeed-JSP code
failing to run under one particular servlet container.
Well, it turns out that problem is that the RequestDispatcher in
TurbineJspService fails to include. I have reported a bug to the vendor,
they have acknowledged that it is a bug, but I haven't heard back from them
yet....
Thanks,
- david
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
