I didn't think so as the RuntimeComponentReference instance passed in to the
createReferenceBindingProvider method has the InterfaceContract of the
component's reference not the interface inside the <reference>. Maybe thats
just a bug?

You can see this if you change sample-helloworld-ws-reference
helloworldwsclient.composite to use the interface.wsdl from the previous
email and then with a break point at
Axis2BindingProviderFactory.createReferenceBindingProvider (or anywhere else
in the Axis2 binding code), I couldn't find anything pointing to the WSDL
interface.

  ...ant


On 5/11/07, Raymond Feng <[EMAIL PROTECTED]> wrote:

Hi,

Do the following methods give you enough information?

ReferenceBindingProvider<M>
createReferenceBindingProvider(RuntimeComponent
component, RuntimeComponentReference reference, M binding);
ServiceBindingProvider<M> createServiceBindingProvider(RuntimeComponent
component, RuntimeComponentService service, M binding);

The binding class should be able to take the interface contracts from the
service/reference when the binding providers are created.

Thanks,
Raymond

----- Original Message -----
From: "ant elder" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, May 10, 2007 7:28 AM
Subject: How to get to the <interferface> defined on a <reference> from
the
<binding>?


> I'm trying to get <binding.ws> to work without specifying all the WSDL
> info,
> for example like this:
>
>    <reference name="HelloWorldService"
> promote="HelloWorldServiceComponent/helloWorldService">
>        <interface.wsdl interface="
> http://helloworld#wsdl.interface(HelloWorld)" />
>        <binding.ws uri="HelloWorldServiceComponent/HelloWorldWebService"
> />
>    </reference>
>
> but i can't find any way to get to the whats defined in the <interface>
> element of the <reference>. None of the runtime objects seem to have any
> link back to the references InterfaceContract.
>
> Should this be possible?
>
>   ...ant
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to