This content has been marked as final.
Show 2 replies
-
1. Re: Problem with custom data type holder
thomas.diesler Aug 25, 2005 4:55 PM (in response to xtremebytes)Could you please create a JIRA issue and attach a sample deployment that allows us to reproduce what you are seeing. Idealy, the sample deployment is a webapp packaged as a war that will show the issue when we click on a link. The war should also contain the sources.
-
2. Re: Problem with custom data type holder
xtremebytes Aug 26, 2005 5:12 AM (in response to xtremebytes)Correct me if I am wrong. I don't see a J2EE spec violation for JAX-RPC accepted value types if my WSStatus class looks like this.
public class WSStatus extends Status { public WSStatus() {} //...no other methods }
where Status looks likepublic class Status implements Serializable { public static final int OK = 0; public static final int SYSTEMERR = -1; //and similar other constants private int type; private String fieldName; private String fieldValue; public Status() {} //...other constructors and accessor methods for the private fields }
I thought such value classes can implement any interface except Remote. Funny enough, when I redeclared the WSStatus aspublic class WSStatus { private int type; private String fieldName; private String fieldValue; public WSStatus() {} //...other constructors and accessor methods for the private fields }
and its RPC holder class as I mentioned before, it started working fine. Was I missing something?
Thanks.