[jboss-jira] [JBoss JIRA] Updated: (BPEL-216) Fully automated process deployment

[Alejandro Guizar (JIRA)]

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

Alejandro Guizar updated BPEL-216:
----------------------------------

    Description: 
The current process deployment procedure has many moving pieces, hence it has became tedious and error-prone. The tasks incorporated by this issue will enable users to deploy a BPEL process (and its related WSDL definitions) with no further requirements for additional descriptors or resources.

The intent is *not* to create a new procedure, but to simplify the existing one with the aid of generation tools. A second design objective is the ability to selectively provide descriptors and resources in order to have fine control over specific portions of the deployment. For example, you might want to specify the URL pattern used by your endpoints. You will be able to provide a custom web.xml file containing the URL patters you want, and let jBPM BPEL generate the rest of the artifacts for you.

The original goal of the new deployment model was integration with the Eclipse BPEL designer. Along the way, it became clear that the simplified deployment procedure could be made independent of the client software used to initiate it. The client could be an Ant build, a web page or the Eclipse designer. Nevertheless, the development of an adapter for each client is the topic of a separate issue.

Ant build: BPEL-281
Web page: BPEL-283
Eclipse designer: BPEL-285

  was:
The current process deployment procedure has many moving pieces, hence it has became tedious and error-prone. The tasks incorporated by this issue will enable users to deploy a BPEL process (and its related WSDL definitions) with no further requirements for additional descriptors or resources.

The intent is *not* to create a new procedure, but to simplify the existing one with the aid of generation tools. A second design objective is the ability to selectively provide descriptors and resources in order to have fine control over specific portions of the deployment. For example, you might want to specify the URL pattern used by your endpoints. You will be able to provide a custom web.xml file containing the URL patters you want, and let jBPM BPEL generate the rest of the artifacts for you.

The original goal of the new deployment model was integration with the Eclipse BPEL designer. Along the way, it became clear that the simplified deployment procedure could be made independent of the client software used to initiate it. The client could be an Ant build, a web page or the Eclipse designer. Nevertheless, the development of an adapter for each client is the topic of a separate issue.

Ant build: BPEL-281
Web page: BPEL-283


> Fully automated process deployment
> ----------------------------------
>
>                 Key: BPEL-216
>                 URL: http://jira.jboss.com/jira/browse/BPEL-216
>             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 current process deployment procedure has many moving pieces, hence it has became tedious and error-prone. The tasks incorporated by this issue will enable users to deploy a BPEL process (and its related WSDL definitions) with no further requirements for additional descriptors or resources.
> The intent is *not* to create a new procedure, but to simplify the existing one with the aid of generation tools. A second design objective is the ability to selectively provide descriptors and resources in order to have fine control over specific portions of the deployment. For example, you might want to specify the URL pattern used by your endpoints. You will be able to provide a custom web.xml file containing the URL patters you want, and let jBPM BPEL generate the rest of the artifacts for you.
> The original goal of the new deployment model was integration with the Eclipse BPEL designer. Along the way, it became clear that the simplified deployment procedure could be made independent of the client software used to initiate it. The client could be an Ant build, a web page or the Eclipse designer. Nevertheless, the development of an adapter for each client is the topic of a separate issue.
> Ant build: BPEL-281
> Web page: BPEL-283
> Eclipse designer: BPEL-285

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