JBoss Enterprise SOA Platform
  1. JBoss Enterprise SOA Platform
  2. SOA-3693

SOA-P 5 ESB Deployment options prompts are asking for wrong information

    Details

    • Steps to Reproduce:
      Hide

      #. Start SOA5
      #. From Admin Console (admin-console) expand and select localhost -> JBossAS Servers - JBoss SOA-P 5 (default) -> JBoss ESB -> Deployments
      #. Click 'Add a new resource' button

      Show
      #. Start SOA5 #. From Admin Console (admin-console) expand and select localhost -> JBossAS Servers - JBoss SOA-P 5 (default) -> JBoss ESB -> Deployments #. Click 'Add a new resource' button
    • Bugzilla Update:
      Perform
    • Similar Issues:
      Show 10 results 

      Description

      When deploying a new ESB using admin-console or JBoss Operations Network, the ESB plug-in is asking for deployment options which are only valid for SOA 4. For example, Deployment Location is asking for a path but in SOA 5 ProfileService is used to deploy managed components meaning that a destination directory can not be selected but instead the user should be selecting whether to deploy farmed or not.

        Gliffy Diagrams

          Activity

          Hide
          RH Bugzilla Integration added a comment -

          Larry O'Leary <loleary@redhat.com> made a comment on bug 767981

          Logged against downstream JBossESB SOA-P bug tracker as https://issues.jboss.org/browse/SOA-3693

          The JBoss ESB plug-in is managed/maintained by the JBossESB project.

          Show
          RH Bugzilla Integration added a comment - Larry O'Leary <loleary@redhat.com> made a comment on bug 767981 Logged against downstream JBossESB SOA-P bug tracker as https://issues.jboss.org/browse/SOA-3693 The JBoss ESB plug-in is managed/maintained by the JBossESB project.
          Hide
          RH Bugzilla Integration added a comment -

          This issue has been migrated to Bugzilla bug 781191. Please note that this JIRA issue has been closed as part of the migration and therefore you will need to check the Bugzilla issue to find the current status.

          Show
          RH Bugzilla Integration added a comment - This issue has been migrated to Bugzilla bug 781191 . Please note that this JIRA issue has been closed as part of the migration and therefore you will need to check the Bugzilla issue to find the current status.

            People

            • Assignee:
              Unassigned
              Reporter:
              Larry O'Leary
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development