DO NOT REPLY [Bug 19701] - array of custom class cannot be serialized in session persistance

2004-09-02 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=19701.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=19701

array of custom class cannot be serialized in session persistance

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2004-09-02 18:47 ---
OK. I have ported the patch and it will be included in the upcoming 4.1.31 
release.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 19701] - array of custom class cannot be serialized in session persistance

2004-06-04 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=19701.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=19701

array of custom class cannot be serialized in session persistance

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |



--- Additional Comments From [EMAIL PROTECTED]  2004-06-04 21:21 ---
This is actually a duplicate of bug 22146 that affects Tomcat 4.1.x.
It was fixed in Tomcat 5, but Remy couldn't reproduce it in 4.1 so
he didn't apply the same fix for 4.1.  I'm seeing this bug in 4.1.27,
and it looks like it should still affect the latest 4.1.

Can you apply this patch to 4.1?

http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/util/CustomObjectInputStream.java?r1=1.1r2=1.2

I have verified in my working copy that it does fix the problem for
Tomcat 4.1.27.

Thanks.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 19701] - array of custom class cannot be serialized in session persistance

2004-04-28 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=19701.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=19701

array of custom class cannot be serialized in session persistance

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2004-04-28 22:57 ---
To clarify Remy's comment he believes that this is a JDK issue where 
java.io.ObjectInputStream passes an invalid classname to Tomcat. Hence this is 
not a tomcat bug.

Given that String[] works it is likely that there is something in your class - 
through no fault of yours - that is hitting some form of JDK bug.

Have you tried searching the sun JDK bug list? How about trying a later 
version of the JDK?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



DO NOT REPLY [Bug 19701] - array of custom class cannot be serialized in session persistance

2003-06-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19701.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19701

array of custom class cannot be serialized in session persistance





--- Additional Comments From [EMAIL PROTECTED]  2003-06-18 18:22 ---
Hey guys, is this being looked into at all? Is more info needed? Or am I doing
something wrong and this really isn't a bug at all - in which case can someone
point me in the right direction please?

Thanks

Chris

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]