Hi Tom, Sorry if my explanations are not very clear. Let me please explain with an example. If I call the service I get an object A. This object A contains object B and object C and so on. Some where in this structure is an object D that has a method getMethode that contains java.lang.Methode. The problem is that object D is an internal class. I only like to configure the beanserializer that he omits the serialization of class D. If there is no way to stop serialization on special classes I see only the possibility to change the standard implementation of AXIS.
Regard Philipp [EMAIL PROTECTED] schrieb am 18.05.04 01:42:05: > > Philipp Bolle wrote: > > Hi Tom, > > > > Tank you for the answer. I read your thread. The funny thing is that > > I do the same for another workflow system, called jbpm. > > Makes sense really, a workflow engine is an obvious consumer of dynamic > invocation code. I took a look at your website, it's interesting stuff. > You might be able to pull out some of our graphical workflow > construction environment if you don't already have that capability, it's > all LGPL. Let me know if you'd be interested in some kind of > collaboration and we can continue this offline. > > > But all works > > fine with the default Bean serializer. I don�t like to create my own > > serializer. > > Well, you don't really have to, just use the existing ElementSerializer. > > > I would like to configure the Bean serializer to stop serializing at > > defined classes. > > Wouldn't this result in you not getting your return information back? > When you say 'stop serializing' what _exactly_ do you mean? > > Cheers, > > Tom _______________________________________________________________________ Moechten Sie Ihre SMS noch ausdrucksstaerker und emotionaler gestalten? Fuegen Sie einfach ein Bild hinzu! http://freemail.web.de/?mc=021194
