Thanks a lot for your input Adam. If I understand properly, there is no clear winner between single method vs multiple methods, it's really a matter of choosing the one that fits best. And thanks for reminding me about the bare/wrapped parameter styles.
-denis > -------- Original Message -------- > Subject: Re: [xfire-user] Document style best practices > From: Adam Kramer <[EMAIL PROTECTED]> > Date: Mon, April 10, 2006 6:53 pm > To: [email protected] > > I want to clarify, document-style requires one root element in the > soap-body, but it doesn't mean you can't send different messages on > different calls that get dispatched to different methods in the service..... > > Adam Kramer wrote: > > Document-style doesn't call for one single root element. Messages > > (and supporting schema defs) are most often designed on a per method > > basis. If you are designing the entire message that gets dispatched > > (e.g. CreateThisRequest, UpdateThatRequest) to the method on receiving > > it, using the Bare parameter style is preferred, else the with wrapped > > parameter style, the method name will be used to wrap the method > > parameters in the service description. If you are designing a service > > that just accepts command strings (and possibly other arbitrary data), > > then does something according to the particular command, then perhaps > > a single method is appropriate. Hopefully I understood the question. > > > > Adam > > > > > > Denis Goeury wrote: > >> We are currently designing a new web service (and its XML Schema) which > >> is intended to execute a set of commands like "create this", "update > >> that"... Should all these commands be sent under a single root XML > >> element and therefore only require a single method in XFire's service > >> class? What's the most common way to design/implement this type of > >> service? > >> > >> Thanks in advance, > >> > >> -denis > >> > >> > >> > > > >
