t to share your original server side classes with the
client.
Keep up the good work!
Martin Jericho
- Original Message -
From:
[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, June 11, 2002 11:23
PM
Subject: Re: WSDL2Java Design Issue
I won't disagree
ase respond to [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
cc:
Subject: Re: WSDL2Java Design Issue
Good point, but I still think the amount of time and effort it would save developers is worth the trouble of adding a flag and requiring the original class in the classpath. Maybe it could
of?
Any comment on the second
suggestion? It doesn't suffer from the problems you
mentioned.
- Original Message -
From:
[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, June 10, 2002 11:37
PM
Subject: Re: WSDL2Java Design Issue
There is no sure way for WS
t;[EMAIL PROTECTED]>
cc:
Subject: WSDL2Java Design Issue
Can someone please tell me why WSDL2Java creates new classes for any data
sent via RPC rather than using the original classes?
For example, if I have a bean called MyBean which contains a property called
MyProperty and some other
Can someone please tell me why WSDL2Java creates new classes for any data
sent via RPC rather than using the original classes?
For example, if I have a bean called MyBean which contains a property called
MyProperty and some other public methods as follows:
public class MyBean {
protected Str
