Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-5038

With changes to BPEL project wizard, BPEL deployment is broken in UI

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 3.1.0.M4
    • Component/s: bpm
    • Labels:
      None

      Description

      Rob helped out with getting the BPEL project structure working like the ESB project structure so we are more consistent down the line and have more flexibility. We now have a JBoss-provided BPEL project wizard instead of what came from the Eclipse project.

      The downside to this is that we lose the Apache ODE Descriptor code that used to work (in fact, it's broken and throws an error when you try to use it or open a non-ODE deployment descriptor with it - NLS missing message: runtimeComponentTypeNotDefined in: org.eclipse.wst.common.project.facet.core.internal.FacetedProjectFrameworkImpl). It's now not connected to our BPEL project. So we need to create a new mechanism for generating the JBoss Riftsaw deployment descriptor.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                dennyxu Denny Xu
                Reporter:
                bfitzpat Brian Fitzpatrick
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: