That would work, but it would lead to a weakly typed solution. I'd prefer for my clients to generate their code from the wsdl and get strongly typed stubs, with correct data structures and correct number of parameters for each call. I don't have control over the clients to this system, only the server side. Client side will probably mostly be .NET but could be anything.
That, plus I have hundreds of classes full of transactions to expose and don't fancy maintaining a big if statement for which one to call. :-) Tim. <[EMAIL PROTECTED]> wrote : > The whole point of using a message-oriented approach is not having to expose > your complete interface method-by-method to the > outside world. > > What you need to do is build a single handler for all incoming messages, and > then check out the mesage parameters to forward the request to the > appropriate internal handler. Then, pass the response back, and send it on > it's way ... > > O:] > > > ----- Original Message ----- > From: "Tim Sawyer" &lang=en">[EMAIL PROTECTED]> > To: &lang=en">[EMAIL PROTECTED]> > Cc: "Tim Sawyer" &lang=en">[EMAIL PROTECTED]> > Sent: Friday, July 30, 2004 4:35 PM > Subject: [jibx-users] Operation Methods with Multiple Parameters > > > > Hi, > > > > I'm currently evaluating jibx-soap for use in a large software > application. > > > > I've just come up against the documentation for the tag in the > service.xml file, where it says that the method that is used to handle the > SOAP request must only have one parameter. > > > > The methods I'm trying to expose were originally designed for Axis, but > I'm trying jibx-soap first. This means that they have multiple parameters. > > > > How difficult would it be to change jibx-soap to handle process methods > with multiple parameters? I'd rather not create a whole new set of classes > just for parameters to my soap transactions. > > > > Regards, > > > > Tim. > > > > > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by OSTG. Have you noticed the changes on > > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, > > one more big change to announce. We are now OSTG- Open Source Technology > > Group. Come see the changes on the new OSTG site. www.ostg.com > > _______________________________________________ > > jibx-users mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jibx-users > > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by OSTG. Have you noticed the changes on > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, > one more big change to announce. We are now OSTG- Open Source Technology > Group. Come see the changes on the new OSTG site. www.ostg.com > _______________________________________________ > jibx-users mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jibx-users ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ jibx-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jibx-users
