| Summary: | Add migration path for SOA-P 5.1 to 5.2 for BPEL project facets | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Robert (Bob) Brodt <bbrodt> |
| Component: | Deployment | Assignee: | Robert (Bob) Brodt <bbrodt> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.1.0 GA | CC: | bbrodt, rob.stryker |
| Target Milestone: | --- | ||
| Target Release: | 5.2.0 GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-3008 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-11-08 01:00:37 UTC | Type: | Feature Request |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Robert (Bob) Brodt
2011-04-05 15:31:35 UTC
Link: Added: This issue relates to JBIDE-8533 Hi Bob: Have we changed the facet name in OUR svn? Or only in the eclipse branch? Currently I have noticed the following files that might be affected: - VCFUtil (one line patch), very easy fix. - Large amounts of org.jboss.tools.bpel.runtimes/plugin.xml The second is the more worrisome version here. I need to know whether this plugin or some other integration plugin like it is going to continue to be distributed at all times. Before I can move forward with this, I need to understand the migration path in general, when we will switch from using our svn version to eclipse-released versions, and whether our svn will continue to hold an integration plugin of some sort. Ready to help, though. =] Assigning back to you just so this doesn't get lost... If we need to set up a chat one day to hash it out I'm willing, but this might require discussions with Max / Nick etc to understand the roadmap. OK, after thinking about this some more, I've come to the conclusion that we should leave our jbt facet alone since we'll be pushing this stuff back into eclipse anyway. I'm thinking we leave the "bpel.facet.core" that's currently defined in the org.eclipse.bpel.apache.ode.runtime plugin (in the eclipse.org repo) as is, and we leave the "jbt.bpel.facet.core" defined in org.jboss.tools.bpel.runtimes as is, but rename it to something like "JBoss Riftsaw BPEL 2.0 Project Facet". Project facets appear to be bound to specific runtimes anyway, so this kind of makes sense. The two adapter plugins that define these facets could then become separate, installable features; so we'd have the features: 1. BPEL Editor 2. JBoss Riftsaw Runtime Adapter 3. Apache ODE Runtime Adapter Then you (the user) can switch between the two facets if you want to deploy to different runtimes. Is this reasonable? Just an afterthought: the ODE runtime requires that the service address include "ode/processes" in its URL, whereas Riftsaw does not. So for example, a "hello_world" process would be addressed as: http://localhost:8080/ode/processes/hello_world when deployed to ODE and as: http://localhost:8080/hello_world when deployed to Riftsaw. This means that the WSDL (where the service binding is defined) needs to be changed depending on which runtime the service is deployed to. Should this service URL change become part of the facet installation (esp. considering that each runtime may have defined different host and port#s) ? Link: Added: This issue is related to JBIDE-6588 Release Notes Text: Added: Verified in jbdevstudio-product-eap-linux-gtk-4.1.0.v201105011951R-H359-M1 Temporarily reopening for release note status. Release Notes Docs Status: Added: Not Required Writer: Added: dlesage Release Notes Docs Status: Removed: Not Required Added: Documented as Resolved Issue Release Notes Text: Removed: Verified in jbdevstudio-product-eap-linux-gtk-4.1.0.v201105011951R-H359-M1 Added: https://issues.jboss.org/browse/SOA-3008 The BPEL jbt.bpel.facet.core project facet id has been deprecated in favour of bpel.facet.core in the BPEL editor plug-in but backward compatibility has been retained. To facilitate this, support for the new facet id has been added to the org.jboss.ide.eclipse.as.wtp.core plug-in and also to the SOA-P 5.2 (and beyond) run-times. |