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

Define how BPEL users handle JBoss BPEL migration

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 3.3.0.Beta2-SOA
    • 3.3.0.Beta1-SOA
    • bpel
    • None
    • Documentation (Ref Guide, User Guide, etc.)

      JBDS-1909 is talking about keeping the old way of creating JBoss Legacy BPEL projects without outlining how migration works
      and which packaging approach is used.

      I want to be aligned on what this migration means:

      It seems we will have:

      2 different facets old jboss and new bpel
      2 different packaging - one using WTP style packaging that is compatible with JBoss AS adapters (old jboss) and one using non-WTP style packing which is not compatible with anything but specific tomcat server adapter (new jboss)
      2 different wizards for creating projects

      And could we please not keep old packaging styles around if we could just migrate them over one way or the other.
      And please let us not make another deployment/packaging approach.

      I hope i'm wrong in the above observations so please let us once and for all document what the migration plan is and what reality we have

              bbrodt_jira Robert (Bob) Brodt (Inactive)
              manderse@redhat.com Max Andersen
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: