From: cristi [mailto:[EMAIL PROTECTED]
Is there any way to make a copy of an object implementing
the HttpServletRequest interface ?
Alter the Tomcat codebase to implement that copy facility, remembering
to check through the codebase for pieces that would break. You would
then be maintaining
Can you tell us what you are trying to achieve? There is almost
certainly an alternative way of getting to the same end without having
to copy requests but, until you give us a bit more detail, we can't help
you.
We have a software project up an running but some modifications are
required.
I got a doubt .
is your problem is not solved by putting the data computed by first
JSP in the session object ??
or putting all the required data in a bean (which is created by
jsp:useBean in first jsp) with session scope and accessing that bean
in second jsp ??
with out seeing the entirety of
I got a doubt .
is your problem is not solved by putting the data computed by first
JSP in the session object ??
or putting all the required data in a bean (which is created by
jsp:useBean in first jsp) with session scope and accessing that bean
in second jsp ??
with out seeing the entirety of
From: cristi [mailto:[EMAIL PROTECTED]
The requirement of making a copy of the HttpServletRequest is
generated by the fact that the former programmers have used (in a
natural manner):
1) the HttpServletRequest.setAttributes() to send data to the jsp
pages creating
Um. Yes, until someone makes another change in the original pages that
breaks your code to pull out the data. The approach is fast to code,
but fragile in the face of changes.
Yes. You are right. Besides the problem I presented to Peddireddy
(one of the guys who has answered my question)
