[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-6661) Deploying BPEL process with dependent jars

[Feng Qian (JIRA)]

     [ https://jira.jboss.org/browse/JBIDE-6661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Feng Qian resolved JBIDE-6661.
------------------------------

    Fix Version/s: 3.2.0.Beta2
                       (was: 3.2.x)
       Resolution: Done


have done

> Deploying BPEL process with dependent jars
> ------------------------------------------
>
>                 Key: JBIDE-6661
>                 URL: https://jira.jboss.org/browse/JBIDE-6661
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: bpel
>    Affects Versions: 3.2.0.M1
>            Reporter: Gary Brown
>            Assignee: Feng Qian
>             Fix For: 3.2.0.Beta2
>
>         Attachments: Quickstart_bpel_service_handler-1.jar
>
>
> The current BPEL deployer packages up BPEL, WSDL and XSD artifacts found in the bpelContent folder, and deploys the packaged jar to the JBossAS server.
> Although the BPEL process cannot invoke Java code, occasionally the Web Service configuration references Java classes - e.g. JAX-WS handlers.
> In this situation, it would be necessary for those Java classes to be deployed to the server along with the BPEL process. One approach would be for the user to independently deploy the dependent Java code to the server (e.g. in the server/default/lib folder) although this assumes that the code will not need to change during the lifetime of the server.
> An alternative approach would be to bundle the dependent jar inside the BPEL deployment jar. This can be achieved by placing the dependent jar at the top level of the BPEL jar.
> The RiftSaw quickstart service_handler example has been attached, as an example of how this can be done.
> One solution maybe to offer the user the option to reference external jars, or other Java Eclipse projects that could be packaged on deployment, that can then be included in the packaged BPEL jar. Although this may be simply a case of the user packaging the jar manually, and placing it in the bpelContent folder themselves?

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