"[EMAIL PROTECTED]" wrote : There is a bug with JBoss Serialization 1.0 about
arrays.
Hmmm, as far as I can see, JBoss Serialization is not used. I digged a little
bit around, found the source for
org.jboss.remoting.loading.ObjectInputStreamWithClassLoader (I think in the
1_4_1 branch) and replaced
protected Class resolveClass(java.io.ObjectStreamClass v)
| throws java.io.IOException, ClassNotFoundException
| {
| if(cl == null)
| {
| return super.resolveClass(v);
| }
| else
| {
| return cl.loadClass(v.getName());
| }
| }withprotected Class resolveClass(java.io.ObjectStreamClass v)
| throws java.io.IOException, ClassNotFoundException
| {
| if(cl == null)
| {
| return super.resolveClass(v);
| }
| return Class.forName(v.getName(), false, cl);
| }
and finally updated the original jboss-remoting.jar with the compiled class.
That fixes the problem.
anonymous wrote : You could or upgrade JBoss to 4.0.4.SP1, or upgrade
jboss-serialization.jar in your lib to 1.0.1.GA.
Ohhh, missed the announcement. So, I'll try it with SP1.
anonymous wrote : What you mean to not compatible to 1.6?
| on that context we are using JBossSerialization to serialize
StatefulSessionBeans, which the specification doesn't require implementing
java.io.Serializable.
Ehmmm, with 1.6 incompatible I just mean, the client runs with jdk1.5, but not
with jdk1.6 beta2 aka b86 because of the shown exception. Not tried SFSB yet ...
BTW: Is there a way, to force either JBoss or Java "native" Serialization?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951567#3951567
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3951567
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
