Hi, Ignacio.
We have discussed some related issues here on other threads. The callback
case could be insteresting and let's talk about this on IRC.
Thanks,
Raymond
----- Original Message -----
From: "Ignacio Silva-Lepe" <[EMAIL PROTECTED]>
To: "Tuscany Dev" <[email protected]>
Sent: Thursday, September 28, 2006 2:56 PM
Subject: Outbound contract for an Axis2Reference
Hi Raymond,
I am not sure how a composite reference with a ws binding is supposed to be
getting its inbound and outbound contracts so that on the inbound it matches
a Java contract with a wired component and on the outbound it has the wsdl
service contract. But I see that InterfaceWSDLLoader produces a
WSDLServiceContract onto which it adds an introspected callback port type if
there is a callbackInterface in the scdl. However, Axis2BindingBuilder is
itself introspecting the outbound contract explicitly, at which point it
does not seem to have a way of telling that it needs to include a callback
port type in the introspection.
You probably went through all this but, is there a reason why
Axis2BindingBuilder needs to do the introspection explicitly? This is a
problem since at this point it has lost the information from the scdl about
the existence of a callback interface.
If it would be more convenient to discuss this via some more immediate
medium, like IRC or google talk, let me know and we can do that.
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
