Hummm.. You could try generating the WSDL2Java Bean from the WSDL, then editing the meta-data in the Bean to remove the properties that you don't want exposed. Axis uses this meta data in WSDL generation.
You could also try adding a BeanInfo class, which I believe the code that Axis uses (The JDK Java Properties interface) will see it and use it. No promises on this approach though, I haven't ever tried it. Tom Jordahl Macromedia Server Development -----Original Message----- From: Mark Rowell [mailto:[EMAIL PROTECTED]] Sent: Friday, January 31, 2003 3:47 AM To: '[EMAIL PROTECTED]' Subject: RE: BeanSerializer Hi Tom I think what I was really asking was if there was a way to turn off serialization in Java2WSDL for certain properties? Is it something that other users have requested? It would help me as I have a lot of prexisting classes, some of which I want to expose for WebService usage (calling from .NET clients). I got round this problem for me by renaming the method from getXXX to retrieveXXX (as it is a method which materializes an object from a database). Many thanks Mark Rowell -----Original Message----- From: Tom Jordahl [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 6:47 PM To: '[EMAIL PROTECTED]' Subject: RE: BeanSerializer All the data in the Bean is serialized, so all the element show up in the Schema. It's the other sides responsibility to deserialize the data in to a data type. The thing on the other end of the wire may not be Java, or may not have access to the original Java type. For instance WSDL2Java will emit a class that will allow the Schema to be deserialized in to it. Tom Jordahl Macromedia Server Development -----Original Message----- From: Mark Rowell [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 9:19 AM To: '[EMAIL PROTECTED]' Subject: BeanSerializer Hi I was wondering why it was necessary for Java2WSDL generate an element in a complex type for properties of a class that are read-only? After all when deserializing an instance of a class with read-only properties how is it going to set the value of the property in the new instance? Am I wrong on this one? I have patched a local copy so that when it writes out the schema complexType definition it ignores read-only properties by using the isWriteable() method on the BeanPropertyDescriptor class. Regards, Mark ---------------------------------------------------------------- Mark Rowell CreditTrade T: +44 (020) 7400 5078 M: mailto:[EMAIL PROTECTED] CreditTrade Limited is regulated by the FSA. (c) CreditTrade 2002. All rights reserved. The information and data contained in this email is provided for the information purposes of the addressee only and should not be reproduced and/or distributed to any other person. It is provided without any warranty whatsoever and unless stated otherwise consists purely of indicative market prices and other information. Any opinion or comments expressed or assumption made in association with the data or information provided in this email is a reflection of CreditTrades judgement at the time of compiling the data and is subject to change. CreditTrade hereby makes no representation and accepts no responsibility or liability as to the completeness or accuracy of this email. The content of this email is not intended as an offer or solicitation for, or recommendation of, the purchase or sale of any financial instrument, or as an official confirmation of any transaction, and should not be construed as investment advice. CreditTrade Limited is regulated by the FSA. (c) CreditTrade 2002. All rights reserved. The information and data contained in this email is provided for the information purposes of the addressee only and should not be reproduced and/or distributed to any other person. It is provided without any warranty whatsoever and unless stated otherwise consists purely of indicative market prices and other information. Any opinion or comments expressed or assumption made in association with the data or information provided in this email is a reflection of CreditTrades judgement at the time of compiling the data and is subject to change. CreditTrade hereby makes no representation and accepts no responsibility or liability as to the completeness or accuracy of this email. The content of this email is not intended as an offer or solicitation for, or recommendation of, the purchase or sale of any financial instrument, or as an official confirmation of any transaction, and should not be construed as investment advice.
