[jboss-jira] [JBoss JIRA] Closed: (BPEL-274) wsdl service generator: eliminate reliance on transitive imports

[Alejandro Guizar (JIRA)]

     [ http://jira.jboss.com/jira/browse/BPEL-274?page=all ]

Alejandro Guizar closed BPEL-274.
---------------------------------


> wsdl service generator: eliminate reliance on transitive imports
> ----------------------------------------------------------------
>
>                 Key: BPEL-274
>                 URL: http://jira.jboss.com/jira/browse/BPEL-274
>             Project: JBoss jBPM BPEL
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Engine
>    Affects Versions: jBPM BPEL 1.1 beta 3
>            Reporter: Alejandro Guizar
>         Assigned To: Alejandro Guizar
>             Fix For: jBPM BPEL 1.1 GA
>
>
> PROBLEM Consider the following network of WSDL documents.
> <definitions name="d3" targetNamespace="ns3">
>  <portType name="pt" />
> </definitions>
> <definitions name="d2" targetNamespace="ns2">
>  <import namespace="ns3" location="d3" />
>  <partnerLinkType name="plt">
>   <role portType="ns3:pt" />
>  </partnerLinkType>
> </definitions>
> <definitions name="d1" targetNamespace="ns1">
>  <import namespace="ns2" location="d2" />
>  <binding name="b" type="ns3:pt" />
> </definitions>
> When parsing d2, ns2:plt is able to resolve the reference to ns3:pt. However, when parsing d1, ns1:b is not able to resolve the reference to ns3:pt. The import element in d1 is not scanned because the binding refers to a port type in namespace ns3 and the import namespace URI is ns2. 
> jBPM BPEL resolves such transitive references, but products like the Eclipse BPEL designer and JBossWS do not. 
> PROPOSAL While generating d1, create a direct import for d3.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira