Sorry..... I was having some problems finding examples since I was looking
for *.scdl files not *.composite files.
So here's the issue..
I'm writing the SCDL like this:
<component name="Component_...">
<implementation.java class="..."/>
<reference name="helloWorldService">
<interface.wsdl interface="..."/>
<binding.ws wsdlElement="..."/>
</reference>
</component>
and I think all that works at the moment is to promote the reference to
Composite-level and to add a <interface.wsdl> within the Composite-level
reference.
This would be useful for top-down (SCDL-first) development.
Does this sound like some work which needs to be done?
Scott
On 6/11/07, Scott Kurz <[EMAIL PROTECTED]> wrote:
I'm having problems using <interface.wsdl> with the Axis2 WS binding.
On the reference side, I'm noticing that JDKInvocationHandler.match()
returns false when it's trying to match the Java-based Contract's operation
of the impl's reference with the WSDL-based Contract's operation on the
other side of the invocation.
The JDKInvocationHandler.match() method has the line:
if
(!clazz.equals(operation.getInputType().getLogical().get(i).getPhysical()))
{
matched = false;
}
This is always returning false as the 'physical' of the WSDL operation is
the QName of a wrapper elem which does not match my Java class name.
Can anyone suggest an angle to look at this from?
I tried to go back to some old code at which I had success but it's hard
to compare. For example, we used to have
AbstractOutboundInvocationHandler. I did notice this old class had a chain
with operation passed into the invoke() method and it did not have to do
something like matching operations in the invocation handler logic.
Thanks
Scott
