It was just changed to make the ServiceDesc-based introspection code easier to deal with, and the intent was always to figure out what kind of support we really wanted and then do that. It's been the current way for quite a while and this is the first time anyone's really mentioned it, so I doubt it broke too many people.
I'm fine with a QName->operation map, and it would be nice if we could embed or import schemas into the WSDD for the various operations, too, so we could generate useful WSDL.... --Glen > -----Original Message----- > From: Doug Davis [mailto:[EMAIL PROTECTED]] > Sent: Monday, September 23, 2002 12:16 AM > To: [EMAIL PROTECTED] > Subject: RE: Only one operation if Msg style? > > I'm wondering though why we changed it. In the old version > of the code if > someone entered just a single method name in the > WSDD/allowedMethods field > then they got what your suggesting (current behavior). If > they entered in > multiple names then they get what Rick is looking for. It > seems to be the > old way was more flexible. So why did we change it? Seem like an > unnecessary restriction - not to mention I'm pretty sure > it'll break quite > a few people (I know of at least two groups that are counting > on the old > behavior). > -Dug > > ps. sigh - can't get on irc (if you're there) > > > Glen Daniels <[EMAIL PROTECTED]> on 09/22/2002 11:57:59 PM > > Please respond to [EMAIL PROTECTED] > > To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> > cc: > Subject: RE: Only one operation if Msg style? > > > > It's not so much a reasonable limitation as an implementation > convenience, > which could certainly be changed. In Axis, "Message" style services > involve just handing the raw XML in some form to the back end > method. As > such, we currently assume that there is only one of those, > and it will deal > with any further dispatch (on QName, for instance) by itself. > This allows > us to resolve the OperationDesc ASAP. > > A "document" style service, however, has N operations, > dispatched by QName. > "Document" style services also do data binding, and will > deserialize XML > into Java objects. > > WSDL doesn't have a concept of "message" style, that's just > an Axis thing. > If your WSDL defines several doc/lit operations, that's fine, > since either > a) you use WSDL2Java to build your classes and it makes a > "document" style > service for you (1 method per operation w/data binding), or > b) you have a > "message" style service in which case it's up to your "xml > handling" method > to figure out what to do. > > We could easily add a QName-based dispatch so that you could > direct the XML > at several different methods in a message-style service, > though. Is this > what you're interested in? > > --Glen > > > -----Original Message----- > > From: Rick Rineholt [mailto:[EMAIL PROTECTED]] > > Sent: Sunday, September 22, 2002 3:59 PM > > To: [EMAIL PROTECTED] > > Subject: Only one operation if Msg style? > > > > > > There seems to have been a limitation put in since B3 that > > message style > > services can support only > > one operation. MessageContext.java 634 to 644. May I ask > > why was this > > done? Is this a reasonable > > limitation? I don't believe SOAP or WSDL make any such > > restrictions. If I > > want to use URL mapping to > > target my service class and my WSDL defines several message style > > operations in that service it > > appears this is not possible unless there some other means > > I'm not aware of > > to get this done. > > > > Rick Rineholt > > "The truth is out there... All you need is a better search engine!" > > > > [EMAIL PROTECTED] > > > > > > > > >
