If you have a complex type that requires a customer serializer on the server, you can assume that you will also require one on the client.
On Apr 12, 2005 5:59 PM, Soti, Dheeraj <[EMAIL PROTECTED]> wrote: > Anne, > > That's what I am trying to do as well (remove the cyclic loops by normalizing > the internal structures) so that the schema exposed through WSDL is simple. > But > do you think that my understanding of the fact that "WSDL alone should be > enough > for a client to interact with a web service" is correct and a good approach to > follow. > > Thanks > > Dheeraj > > -----Original Message----- > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 12, 2005 2:48 PM > To: axis-user@ws.apache.org > Subject: Re: General Question about having custom Serializer/Deserializer > > Don't put cyclic loops in your schema. > > On Apr 12, 2005 4:39 PM, Soti, Dheeraj <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I have a schema which has cyclic loops and AXIS goes into a circular > > loop while trying to serialize the objects (throws Stack overflow > > exception). I can write my own serializer/deserializer but I am > > confused that how it is going to work on client's end. In addition to > > WSDL wouldn't the client also need the serializer/deserializer? Till > > now I have been thinking that the best approach is to just write a > > WSDL and that is the only thing any client would need to get access to > > my service. If I make sure that it is interoperable then they can > > generate client side proxies in any environment and they should be > > ready to go. I can generate server side classes using AXIS or anything > > other tool. > > > > Am I correct or I am missing some very basic concept here? > > > > Thanks > > > > Dheeraj > > >
