+1
- James M Snell/Fresno/IBM
Web services architecture and strategy
Internet Emerging Technologies, IBM
544.9035 TIE line
559.587.1233 Office
919.486.0077 Voice Mail
[EMAIL PROTECTED]
Programming Web Services With SOAP, O'reilly & Associates, ISBN
0596000952
==
Have I not commanded you? Be strong and courageous. Do not be terrified,
do not be discouraged, for the Lord your God will be with you wherever you
go.
- Joshua 1:9
Please respond to [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject: RE: Quick question!!
The basic idea is that you don't want to automatically emit methods like
hashCode() and toString() in your WSDL. The same is true for
javax.ejb.EJBObject methods, etc.
--Glen
> -----Original Message-----
> From: Sedukhin, Igor [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 07, 2002 3:38 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Quick question!!
>
>
> May I ask why was it a problem? I just want to know... Thanks.
>
> -----Original Message-----
> From: Glen Daniels [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 07, 2002 3:18 PM
> To: 'Axis-Dev (E-mail)'
> Subject: Quick question!!
>
>
>
> Is it OK to always stop emitting WSDL for Java classes that are in the
> "java.*" or "javax.*" packages? Would people be alright with
> that being the
> default behaviour for the emitter (you'd be able to override it if you
> really wanted to)?
>
> --Glen
>
