Thanks for the idea, but I don't think an attachment will work. I don't want the client of the service to have to parse to attachment themselves.
I'd like it to look like a normal rpc soap service, that follows the schema declared in the types section. I just want to be able get lower level access to the response so that I can skip the marshal/unmarshal/serialize steps. Jason On Wednesday 17 March 2004 11:50 pm, Dario Di wrote: > To combine the rpc and the message style, why don't > you use the rpc style adding an xml document as > attachment? > > --- Jason Calabrese <[EMAIL PROTECTED]> ha > scritto: > Hi everyone, > > > Is there anyway combine the rpc and message styles? > > > > What I would like is to have a method signature > > something like this: > > > > Document doSomething(CustomRequest req); > > > > I will be using the data in the CustomRequest to > > interface with an existing > > application that returns a DOM document and I don't > > want to manually marshal > > it into beans just to have it get unmarshaled again. > > > > Also it would be nice to be able to return the > > String representing the DOM > > document so I could do some caching to a file or db > > and not need to reparse > > the xml again. > > > > > > Thanks, > > > > Jason > > ______________________________________________________________________ > Yahoo! Mail: 6MB di spazio gratuito, 30MB per i tuoi allegati, l'antivirus, > il filtro Anti-spam > http://it.yahoo.com/mail_it/foot/?http://it.mail.yahoo.com/
