Raymond,
Ok, I thought I understood this. In particular, an Axis2Reference's inbound
wire would be able to see an 'interface.contract', which I take to mean a
contract derived from the interface between the reference and, say, a
component wired to it, e.g., an interface.java.
However, for helloworldwsclient, when Axis2Reference does
inboundWire.getServiceContract it gets a WSDLServiceContract, from which it
gets null when it asks for getCallbackClass. Perhaps I misunderstood, but
the Axis2Reference needs to be able to get a handle on the callback method
for the interface with the component wired to it, in order to set up the
appropriate callback target invoker.
Thoughts?
----- Original Message -----
From: "Jim Marino" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, September 22, 2006 12:43 PM
Subject: Re: How can we insert a DataBindingInterceptor for the outbound
wire of a composite-level reference?
<snip/>
2. For references
inbound wire (interface.contract) --->outbound wire
(interface.contract) -->target invoker (binding.contract)
Which would mean the target invoker would have to perform the mapping
(similar to a service receiver)
My version:
inbound wire (interface.contract) ---> outbound wire
(binding.contract) -->target invoker (binding.contract)
Or, the second option would look like:
inbound wire (interface.contract) --->outbound wire
(binding.contract) -->target invoker (binding.contract)
I prefer to have the 2nd.
ok me too
The connector would be responsible for performing the mapping when it
connects the wires.
What do you think?
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
