Hi,
I'll add a "setDefaultDataBinding()" method the "Interface" interface for
now so that componentType/binding builders can provide a desired
databinding.
I checked in the changes under r529001. Now the echo-databinding sample is
working again. Please see the EchoBindingBuilder to see an example of
Interface.setDefaultDataBinding().
I suggest that we review all these designs after we get all the basic things
working.
Thanks,
Raymond
----- Original Message -----
From: "ant elder" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, April 15, 2007 4:56 AM
Subject: How to specify databinding in bindings and implementations?
In the old code a binding or implementation could say what data binding it
wanted to use by setting the name on the ServiceContract, but now the
InterfaceContract doesn't have a setDataBinding method so how should this
be
done? (eg the Axis2 binding used to set the Axiom databinding).
There is a setDataBinding method on Operation which I've tried to use, and
that does caused the data binding interceptor to get used but then that
fails as the target DataType ends up with a null in the databinding field
so
the DB Mediator throws a "No path found for the transformation" exception.
I
have tried just using the IDE debugger to set the target DataType to have
the Axiom databinding and that almost all works except then the
databinding
doesn't add the wrapper element to the resulting OMElement.
Any guidance on how this all should be done now? Are then any existing
tests
that use Axiom and wrapped WSDL that work that I could look at?
...ant
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
