[jboss-jira] [JBoss JIRA] Updated: (BPEL-217) convert bpel-definition.xml into master wsdl document

Alejandro Guizar (JIRA) jira-events at lists.jboss.org
Tue Feb 27 02:49:35 EST 2007


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

Alejandro Guizar updated BPEL-217:
----------------------------------

        Summary: convert bpel-definition.xml into master wsdl document  (was: make bpel-definition.xml optional)
    Description: 
The definition descriptor only exists to provide an import mechanism missing in BPEL 1.1.  BPEL 2 does provide such a mechanism, making the definition descriptor a redundant annoyance for BPEL 2 deployments.

For BPEL 1.1 deployments, we can introduce the concept of a "master" WSDL file in lieu of the definition descriptor. This master WSDL file would import other WSDL and XML Schema documents required by the BPEL process through the WSDL import mechanism. Said mechanism allows for relative and absolute locations just as the definition descriptor does.

Apart from declaring imports, the definition descriptor also points to the BPEL file. To locate the BPEL file in absence of the definition descriptor,  jBPM BPEL would search a file whose extension is "bpel". The master WSDL file would have the same name of the BPEL file and a "wsdl" extension.

  was:the definition descriptor fills the gap of a document import mechanism in v1.1. v2 does provide such a mechanism, making the descriptor redundant for v2 deployments.


> convert bpel-definition.xml into master wsdl document
> -----------------------------------------------------
>
>                 Key: BPEL-217
>                 URL: http://jira.jboss.com/jira/browse/BPEL-217
>             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
>
>
> The definition descriptor only exists to provide an import mechanism missing in BPEL 1.1.  BPEL 2 does provide such a mechanism, making the definition descriptor a redundant annoyance for BPEL 2 deployments.
> For BPEL 1.1 deployments, we can introduce the concept of a "master" WSDL file in lieu of the definition descriptor. This master WSDL file would import other WSDL and XML Schema documents required by the BPEL process through the WSDL import mechanism. Said mechanism allows for relative and absolute locations just as the definition descriptor does.
> Apart from declaring imports, the definition descriptor also points to the BPEL file. To locate the BPEL file in absence of the definition descriptor,  jBPM BPEL would search a file whose extension is "bpel". The master WSDL file would have the same name of the BPEL file and a "wsdl" extension.

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

        



More information about the jboss-jira mailing list