On 01/14/2011 01:08 PM, Scott Kurz wrote:
I haven't had time to try this in the past couple days, but, before
the week ends I'll just suggest a sketch of what I had in mind along
the lines of Simon's last response:
- creating a new isBareStyle() method on Operation, defaulting to 'false'
- setting the underlying boolean to 'true' in JAXWSJavaInterfaceProcessor
- In Input2InputTransformer do something like:
boolean sourceBare = sourceOp != null&& sourceOp.isBareStyle()
and otherwise keeping the main if-blocks with the same check as they
have today, e.g:
if ((!sourceWrapped&& !sourceBare)&& targetWrapped) {
// Unwrapped --> Wrapped
------------------------------------------------------------------------------
Besides actually trying it out on your updated tests, I'd also wanted
to give some thought to how to name these methods to make them most
understandable...
Scott
Sounds like a good idea. I find these flags confusing.
It'd be good to have crisp definitions of wrapped, bare and unwrapped
(as mentioned in the above the code comments) in the context of the
databinding framework.
If wrapped != !bare and wrapped != !unwrapped (as per the above code),
what did we intend to mean by 'bare' and 'unwrapped'?
Also, earlier in this thread [1] you said 'There is a wrapper, (IIRC we
build this in JAXWSJavaInterfaceProcessor), but the wrapperStyle is
false'. Is that intentional or a bug?
[1] http://marc.info/?l=tuscany-dev&m=129471942908213&w=2
--
Jean-Sebastien