This is really a question for Ajith, but since others will probably be
facing similar problems in the future I thought it best to get it on the
list...
Since it looks like the code generation changes for ADB unwrapped
support are now in place I'm back to working on unwrapped support for
JiBX. As discussed previously on the list, I want to take a different
approach to the unwrapped implementation for JiBX from that used for
ADB. The main difference is that in ADB's case a wrapper object class is
always used, and then the individual parameters for an operation method
call are inserted into that wrapper object (on the client side) or
extracted from that wrapper (on the server side). I don't want to use a
wrapper for JiBX, instead generating the code directly to marshal or
unmarshal the parameters.
In order to do this I need to pass additional custom XML to the JiBX
code generation, and also I need to add a switch (in the form of an
attribute to the <method> element, most likely) for the common templates
(InterfaceImplementationTemplate.xsl and MessageReceiverTemplate.xsl) so
that they can delegate the entire handling of the wrapping/unwrapping to
the JiBX template. There doesn't seem to be an easy way to customize the
XML passed to the code generation templates at present, so I'd like to
know how best to handle this.
Thanks,
- Dennis
--
Dennis M. Sosnoski
SOA, Web Services, and XML
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-296-6194 - Wellington, NZ +64-4-298-6117
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
