Details

    • Type: Task
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 3.3.0.Beta1
    • Fix Version/s: 3.3.0.Beta1
    • Component/s: server
    • Labels:
      None

      Description

      I added some unit tests when working on JBIDE-9724, and discovered some unit test weirdness when dealing with EAP 6.0. Basically, it cannot confirm the full version. It comes back with 7.1.

      If the task was simple, I would simply fix the code (as I did with the EAP6 condition class), but in this case, the logic to discover the version is hard-coded in the ServerBeanLoader with no reference to a ServerType, and so no way to customize the logic per server type. If it were entirely my code, I'd go ahead and change it, but I know others use this, and wanted to solicit input.

      If you look at ServerBeanLoaderTest.testEAP60, you will see a failure inside a try/catch statement. The question here ultimately is what should ServerBeanLoader.getFullServerVersion reply when presented with an EAP6 installation: the EAP version? Or the AS version?

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  rob.stryker Rob Stryker
                  Reporter:
                  rob.stryker Rob Stryker
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: