When an wsdl (1.1) is in aar, dispatching would not work.
---------------------------------------------------------
Key: AXIS2-2135
URL: https://issues.apache.org/jira/browse/AXIS2-2135
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Environment: any
Reporter: Saminda Wishwajith Abeyruwan
Priority: Critical
Attachments: version.aar
When an aar has a WSDL (1.1), dispatching would not work due to following
reasons.
If service binding of the wsdl is as follows,
...
<wsdl:service name="foo">
<wsdl:port binding="ns1:foo1Binding" name="foo1Port">
<soap:address
location="https://localhost:9443/axis2/services/foo1"/>
</wsdl:port>
<wsdl:port binding="ns1:foo2Binding" name="foo2Port">
<soap:address location="http://localhost:9762/axis2/services/foo2"/>
</wsdl:port>
</wsdl:service>
...
and when evaluate the AxisConfiguration#allServices Map; it has the service
name as (key)
foo.foo1Port
foo.foo2Port
Thus no "foo"; this cause service URL to be calculated as;
<protocol>://<host>:<port>/axis2/services/foo.foo1Port/
or
<protocol>://<host>:<port>/axis2/services/foo.foo2Port/
Is the above behavior correct if the given WSDL is 1.1. I agree if the given
WSDL is 2.0; the behavior is acceptable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
