The same interface type can be referenced by many references/services XML declarations. At this moment, whenever an <interface.xxx> is present in the SCDL, we create an instance of XXXInterface. Ideally, we should have a separate model to capture the representation of an interface type, for example, JavaInterfaceType for a java interface. The Interface is for the XML declaration of <interface.xxx> and InterfaceType is for the underlying interface type (such as Java interface or WSDL portType).

public interface Interface {
   ...
   InterfaceType getType(); // return the type of the interface
}

Thanks,
Raymond

----- Original Message ----- From: "Simon Laws" <[EMAIL PROTECTED]>
To: <tuscany-dev@ws.apache.org>; <[EMAIL PROTECTED]>
Sent: Wednesday, December 12, 2007 9:23 AM
Subject: Re: How to set a specific data binding to be used by a binding?


On Dec 12, 2007 3:23 PM, ant elder <[EMAIL PROTECTED]> wrote:

I'm probably not going to provide enough information to get much of an
answer but I'll ask now anyway in case anyone has an obvious answer right
away...

Is there a simple way for a binding to say what data binding it wants
used?

I know there's Interface.resetDataBinding but to use that you need the
same
Interface object that is used by the DataBindingRuntimeWireProcessor when
working out if a transformation is required and that doesn't seem to be
the
one thats use by the RuntimeComponentReference/Service which is passed in
to
a Service or Reference BindingProvider. Even in a simple testcase with a
component using a reference there seems to be about 6 instances of
JavaInterface instantiated for the interface class used by the reference
so
making sure resetDataBinding is called on the correct one doesn't seem
straight forward.

  ...ant

Ant

An aside. Any idea why there are so many copies of the interface object?

Simon



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

Reply via email to