[jboss-jira] [JBoss JIRA] Resolved: (BPEL-276) generate bpel application descriptor along with wsdl service description

Tue Aug 28 23:20:18 EDT 2007

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

Alejandro Guizar resolved BPEL-276.
-----------------------------------

    Resolution: Done

SOLUTION Modified the wsdl service generation tool to produce an application descriptor object. Introduced a descriptor writer that transforms the descriptor object into a DOM tree which is later saved as XML.

> generate bpel application descriptor along with wsdl service description
> ------------------------------------------------------------------------
>
>                 Key: BPEL-276
>                 URL: http://jira.jboss.com/jira/browse/BPEL-276
>             Project: JBoss jBPM BPEL
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Engine
>            Reporter: Alejandro Guizar
>         Assigned To: Alejandro Guizar
>             Fix For: jBPM BPEL 1.1 GA
>
>
> PROBLEM The associations between the partner links and the published WSDL ports are declared in bpel-application.xml. 
> In the provided examples, such associations can be inferred and are not present in the descriptor. This is because only one port in the WSDL document implements the port type associated with each partner link. In the general case, however, multiple ports may implement the same port type, making the association to partner links ambiguous.
> During the procedure to generate a WSDL service description, the tool generates the WSDL port for each partner link and retains the unambiguous associations, but does not preserve them.
> PROPOSAL Have the service description tool write the associations between partner links and WSDL ports to a generated bpel-application.xml file.

-- 
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