Uploaded image for project: 'Red Hat CodeReady Studio (devstudio)'
  1. Red Hat CodeReady Studio (devstudio)
  2. JBDS-2365

ESB projects cannot be deployed using Server Add/Remove

    XMLWordPrintable

Details

    • Release Notes
    • Hide
      JBoss Enterprise Service Bus (ESB) 4.11 and 4.12 projects were not recognized as compatible for deploying on runtime server instances of JBoss Enterprise Application Platform and JBoss Application Server and, as a result, the associated applications could not be deployed to these servers. The list of compatible facets held by Server Tools has been extended to include JBoss ESB 4.11 and 4.12. Consequently, the applications of JBoss ESB 4.11 and 4.12 projects can now be deployed on runtime server instances of JBoss Enterprise Application Platform and JBoss Application Server without errors or warnings.
      Show
      JBoss Enterprise Service Bus (ESB) 4.11 and 4.12 projects were not recognized as compatible for deploying on runtime server instances of JBoss Enterprise Application Platform and JBoss Application Server and, as a result, the associated applications could not be deployed to these servers. The list of compatible facets held by Server Tools has been extended to include JBoss ESB 4.11 and 4.12. Consequently, the applications of JBoss ESB 4.11 and 4.12 projects can now be deployed on runtime server instances of JBoss Enterprise Application Platform and JBoss Application Server without errors or warnings.
    • Documented as Resolved Issue

    Description

      • Create a new server runtime for SOA-P 5.3
        • Preferences -> Server -> Runtime Environments
      • Create a new ESB project with the defaults
      • Right click the server and chosse "Add and Remove" and the project cannot be added. Error message is, "The server does not support version 4.11 of the JBoss ESB Module specification.

      The project can be deployed after right clicking and choosing "Mark as deployable," but it can never be added using "Add and Remove."

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBDS-2394 CLONE - ESB projects cannot be deployed using Server Add/Remove

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBDS-1889 JBoss ESB runtime check cannot determine correct runtime for SOA-P 5.2.0.ER5 build

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-13328 as.core plugin should understand the idea of ESB 4.x instead of needing to explicitly list versions like 4.8,4,9,4.10,4.11,4.12

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. JBDS-2388 Tracker issue - JBDS6 and SOA Tooling Issues

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBDS-2431 JBDS5 - Does not recognize ESB 4.11 - deployments to SOA-P servers fail

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. JBIDE-13209 Need to add ESB 4.12 option with constraints

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              nickboldt Nick Boldt
              jdavis-se-jboss Jeremy Davis
              Michelle Murray Michelle Murray (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: