Using an interface was my first thought, but how would I get Axis serialize the interface? A super class is a good idea as well but the object model I'm working with is rather complex, classes within it are already extending other classes within the hierarchy so that is out as well.
Anyone else has any other ideas? Thanks, Doug -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Larry Meadors Sent: Monday, August 07, 2006 10:36 AM To: [email protected] Subject: Re: Hiding exposed fields on serialized objects Could you create an interface (or even super class) that only exposed the properties you wanted exposed, and use that for the web service? Just a guess..not terribly familiar with axis. Larry On 8/7/06, Bell, Douglas <[EMAIL PROTECTED]> wrote: > > > I am using iBatis on the back end of my application and need to expose > several fields to it that I would rather not have the client see. > Short of pushing the data into a separate object and sending that back > or removing them directly from the WSDL is there any simple way to > limit the exposure of these fields? I'm using java2wsdl to generate > the WSDL and then using the Admin util to deploy via an ant script and > would rather not mess with the output. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
