Hi,
>In effect, it is like your 2nd case, since Strings are also Serialized
objects (The object
>graph of my SerialObjectA contains Strings which in turn must be serialized
and de-
>serialized).
You mean your parameter is a String ?
>i.e., I return an Object like this:
>public class SerialObjectA implements Serializable {
> private String testString;
> public String getTestString() { return testString; }
> public void setTestString(String testString) { this.testString =
testString; }
>}
I am not sure to follow you: the problem I have is not in the type of the
return object.
The problem is in the type of the parameter.
If the parameter is java.lang.String , int, java.lang.anything that is
Serializable : NO PROB.
If the parameter is com.mycompany.anything that is Serializable : PROBLEM.
The parameter. Noit the returned object.
>Does your serialized object hold remote references? I don't think that
those will serialize
>at all. I guess it depends on what that 2nd method is trying to do with
the parameter passed >in.
No, in fact I am even not receiving anything I pass an Object (Serializable)
with 2 String in it.
>-jason
It really drives me crazy, it is not very important but these rmi, jndi,
classloading are less and less clear in my head...
Vincent.
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
