Could you please elaborate a little more on that? In what way exactly? Have my class implement BeanInfo interface and describe the properties I'd like to see returned in getPropertyDescriptors() method?
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 30, 2004 11:40 AM > To: [EMAIL PROTECTED] > Subject: RE: hiding a property from Axis serializer? > > > Try using the bean info class to define what properties exist > for the bean. > Axis seems to obey this Java Bean rule. > > -----Original Message----- > From: Sheptunov, Bogdan [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 23, 2004 11:57 AM > To: [EMAIL PROTECTED] > Subject: RE: hiding a property from Axis serializer? > > > > A "filter all those properties" approach is to create a > > interface for > > each of those beans you would like to serialize, but just including > > getters and setters for those properties you really want to be > > serialized; then let your bean implement that interface > > (already does!) > > and alter all your web services to not use the bean class but the > > "filtered inteface". The main drawback (and innaceptable > for me) is > > I already tried that. Defined an interface, had a class (that > has some other > properties besides the one declared in the bean interface) > implement it, put > the interface name in WSDD file. Axis ended up putting all of > the properties > (not only the ones defined in WSDD) into the response object > anyway. This > looks like a bug to me. Shouldn't only the properties listed > in the WSDL be > serialized? > > Ideas anyone? > > Bogdan >
