Hi Tim,
This is the next issue on the agenda for JibxSoap, basically handling wrapped-style web services where the doc-lit payload of a request message actually represents a sequence of parameters for a method call. So the method call:
myCall(int a, float b, BeanlikeObject c, BeanlikeObject[] d)
would be represented by something like:
<tns:myCall>
<a>5</a>
<b>1.2</b>
<c>
...
</c>
<d>
...
</d>
<d>
...
</d>
</tns:myCall>I talked with Cameron Taggart, who's implementing the Xsd2Jibx support, about the client-side support for this (where I'd probably have a generated stub class package up an object from the method call parameters and then process that object as in the current JibxSoap client handling) just last week. The server-side handling is actually simpler in theory; there I just need to generate the actual method parameter values as objects (using wrappers for the primitive types) and pass them in the reflection method call to the actual service implementation. To do things right I'd also want to generate the schema description of the wrapped XML for the method call.
For a first cut I'd probably require the user to define a binding for any complex values (objects that don't serialize to simple strings) in the parameter list. Adding default binding generation for beanlike objects would be pretty easy.
So I guess the answer to your question is that it's not too hard, and I've already planned it out; it's just a matter of my finding time to do it (unless you want to try this yourself - unlike the base JiBX code, JibxSoap is simple enough that you could probably jump in and start putting this together without a big learning curve).
- Dennis
Tim Sawyer wrote:
Hi,
I'm currently evaluating jibx-soap for use in a large software application.
I've just come up against the documentation for the <operation> 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
