This is from Asynchrousnous Sample Project. Attached are wsdl and xsd files.
Note that AsynchronousSampleClient.wsdl and AsynchronousSample.wsdl both have
same targetNamespace (http://www.mycomp.org/AsynchronousSample)
AsynchronousSampleClient.wsdl imports AsynchronousSample.wsdl.
AsynchronousSampleClient.wsdl has binding:
<binding name="CallbackSoapBinding" type="tns:MyCallbackPortType">
which refers to portType MyCallbackPortType which is defined in
The problem is because of same targetNamespace in both of these wsdls,
when calling getPortType().get() on binding CallbackSoapBinding
it just finds out first matching wsdl which is AsynchronousSampleClient.wsdl.
And this does not have this MyCallbackPortType defined.
The solution should be to look into all the wsdl documents matching a
targetNamespace and then find out first matching portType.
Created attachment 32275 [details]
wsdl/xsd exhibiting problem
Target for FCS, will fix in next milestone build.
Possible temporary work-around in the Asynchronous sample for beta is to rename
the targetNamespace of the client?
This is a bug since WSDL specs allow imported wsdl to have same target namespace
as the importing as well as multiple other wsdl's. The fix is xml/wsdl/api
module class GlobalReferenceImpl to search for the referenced in all wsdl's
having the target namespace.
Justification for BETA waiver:
- Could be worked-around by rename namespace or reordering import's.
Nam, can you please expand on the waiver justification so that the release note
engineer can document the workaround.
Nam, if the sample is adjusted, is the workaround still needed? Ideally, we can
just update the sample so that it doesn't encounter this bug.
Praveen - need you to check/adjust Asynch sample with required workaround... it
is *OK* if this comes after B17 cutoff of 10pm tonight.
We already update the Asynchronous sample and it runs fine now wihtout any
intervention from user. However, we still have to document the work-around in
case user hit this limitation in non-sample app.
The work-around is simply to assign a namespace the imported WSDL file, distinct
from the namespace of the importing WSDL.
Can you verify whether this is fixed or not?
This is fixed. Duplicate of issue 81842.
*** This issue has been marked as a duplicate of 81842 ***
Issue 81842 has already been verified. Scenario cannot be duplicated because of