[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6588) BPEL deployment to ODE running in Tomcat

[Robert (Bob) Brodt (JIRA)]

    [ https://jira.jboss.org/browse/JBIDE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563482#comment-12563482 ] 

Robert (Bob) Brodt commented on JBIDE-6588:
-------------------------------------------

I reverted all changes for this fix - we will have to figure out a better migration path for existing BPEL projects.
The BPEL face name will be changed from jbt.bpel.facet.core to bpel.facet.core which affects Savara as well.


> BPEL deployment to ODE running in Tomcat
> ----------------------------------------
>
>                 Key: JBIDE-6588
>                 URL: https://jira.jboss.org/browse/JBIDE-6588
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: bpel
>    Affects Versions: 3.2.x
>            Reporter: Gary Brown
>            Assignee: Robert (Bob) Brodt
>             Fix For: 3.2.0.Final
>
>         Attachments: JBIDE-6588.patch
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> Currently the BPEL plugins in JBoss Tools support deployment of a BPEL process and ODE deployment descriptor to RiftSaw (ODE running in JBossAS).
> It may be useful to allow users to also deploy the same processes to ODE running inside Tomcat.
> This would enable existing ODE/Tomcat users to benefit from a supported version of the BPEL editor, and easily switch to using RiftSaw if they wanted.
> The Eclipse BPEL project already provides a deploy for ODE in Tomcat. The only change that would be required is to change the bpel-deploy.xml to deploy.xml during deployment, as ODE does not recognize bpel-deploy.xml.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira