Any beans exposed in your web service will be pure dataholders. No logic at all. If you want some logic on the client side then you will have to provide your clients with a client side library - external to the webservice.
[EMAIL PROTECTED] wrote:
Can any one reply for my questions please. I sent it a week back but still didn't get any response. thanks -kannan Hi Friends, Iam at the design stage of my webservice components. I have decided to start with WSDL design and use WSDL2Java for further developments like Creation of java beans and other service objects.
I tired converting WSDL to Java, I can see that the Complex types are created as a Java Beans, which is correct. But I also see that some Meta Data (Static block) is also created in that Java Beans. I referred the documents, it says that it is used for type mapping xml to java type. Which is true.
But my questions are: 1. I referred the example guide supplied with Axis (userguide/example5), where there is a Java bean Order.java which doesn't have any meta data in it. So, it is ok to create my java bean components with these meta-data ?
2. As per java bean spec, I have written a Java bean which will be used by axis to convert the xml to bean. Can I have any other methods in it, like toXML() which will be returning the xml contents as well ?
Expecting ur help, thanks, -kannan
This email and any attachments to it may contain confidential information intended for the addressee only. If you are not the intended addressee, you are strictly prohibited from disclosing, copying, distributing or using this email in any way. Unauthorised use of the information contained in this email is unlawful. If you have received this email in error please notify us on [EMAIL PROTECTED] and delete the email from your system.
Information contained in this email can not be disclosed, copied, distributed or used in any way without the prior consent of the sender. Any opinions, advice or facts given in this email are given without warranty or the intention to enter into an agreement unless specifically stated and confirmed by agreement, letter or such other documentation signed by an authorised signatory of BCA Holdings Limited or any of its subsidiary companies.
Any personal information contained in this email is strictly the view of the sender and is in no way authorised or attributable to BCA Holdings Limited or any of its subsidiary companies in any way. All emails through the company gateway are subject to monitoring. The company cannot be held liable for any errors or viruses contained in this message.
This email and any attachments to it may contain confidential information intended for the addressee only. If you are not the intended addressee, you are strictly prohibited from disclosing, copying, distributing or using this email in any way. Unauthorised use of the information contained in this email is unlawful. If you have received this email in error please notify us on [EMAIL PROTECTED] and delete the email from your system.
Information contained in this email can not be disclosed, copied, distributed or used in any way without the prior consent of the sender. Any opinions, advice or facts given in this email are given without warranty or the intention to enter into an agreement unless specifically stated and confirmed by agreement, letter or such other documentation signed by an authorised signatory of BCA Holdings Limited or any of its subsidiary companies.
Any personal information contained in this email is strictly the view of the sender and is in no way authorised or attributable to BCA Holdings Limited or any of its subsidiary companies in any way. All emails through the company gateway are subject to monitoring. The company cannot be held liable for any errors or viruses contained in this message.
