----- Original Message -----
From: "Chabbewal, Navjeet" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 17, 2001 9:58 PM
Subject: RE: cactus and Iplanet App Server 6.0
> Vincent,
>
> OK I have been able to make some progress. The first problem was that
> ResultHolder class must be serializable if you are adding it to
> ServletContext for Iplanet web container.
Good finding ! I checked the Servlet spec and there is no mention that
anything put in the Servlet Context should be serializable. However, I have
found this (section 7.7.2 of Servlet 2.2 spec) :
"
Distributed Environments
Within an application that is marked as distributable, all requests that are
part of a session can only
be handled on a single VM at any one time. In addition all objects placed
into instances of the
HttpSession class using the setAttribute or putValue methods must implement
the
Serializable interface. The servlet container may throw an
IllegalArgumentException if a non serializable object is placed into the
session.
"
Anyway, the change is little so I'll make it (done !).
> After I did that now it is
> hanging in getResult() method of ResultHolder class as the result
> attribute is always null. I added some debug code at the end of
> setResult() method in ResultHolder and it is not null at the exit from
> this method. I am wondering what could be nullifying this attribute.
> Give me some pointers here.
I have discovered a bug in the Jsp Redirector and am correcting it now (it
may be linked to your problem). At the same time, I am performing some
refactoring of org.apache.commons.cactus.server.* classes. I will have
finished tomorrow morning. I'll tell you when I have finished and maybe you
can give it a try with the new version.
>
>
> --Navjeet
Thanks a lot.
-Vincent
