Uploaded image for project: 'HAL'
  1. HAL
  2. HAL-370

Admin Console does not handle resource adapter address properly

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Done
    • None
    • Unknown
    • None
    • None

    Description

      console seems to handle RA entities in a a bad way. Not sure if this is by design and I am the one missing something.

      In case of anonymous declaration( as per JCA specs ? ):

      <resource-adapters>
      <resource-adapter>
      <archive>test</archive>
      <transaction-support>NoTransaction</transaction-support>
      </resource-adapter>
      </resource-adapters>

      Name of adapter( in model ) is set to to "test" - archive name. However if there are more adapters, model names become:
      /subsystem=resource-adapters/resource-adapter=test
      /subsystem=resource-adapters/resource-adapter=test->1
      /subsystem=resource-adapters/resource-adapter=test->2
      ...
      /subsystem=resource-adapters/resource-adapter=test->n++

      Now, there is another trick. AS supports custom "ID":

      <resource-adapters>
      <resource-adapter id="XXX">
      <archive>test</archive>
      <transaction-support>NoTransaction</transaction-support>
      </resource-adapter>
      </resource-adapters>

      In this case the model address is "/subsystem=resource-adapters/resource-adapter=XXX".

      In case of second definition, console keeps displaying RA as "test" - since its the archive name. In case of definition with ID or one with '->#' this fails, since console depends on "getArchive()":

      https://github.com/hal/core/blob/master/gui/src/main/java/org/jboss/as/console/client/shared/subsys/jca/ResourceAdapterPresenter.java#L411

      This affects WFLY and all previous release.

      Attachments

        Issue Links

          Activity

            People

              rhn-cservice-bbaranow Bartosz Baranowski
              rhn-cservice-bbaranow Bartosz Baranowski
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: