Details

    • Similar Issues:
      Show 10 results 

      Description

      Unable to create a runtime for latest AS 5.1.0.CR1 that can be built from:

      http://anonsvn.jboss.org/repos/jbossas/branches/Branch_5_x/

      Rob, let me know when this is fixed and what update site I should use to get this update.

        Gliffy Diagrams

          Activity

          Hide
          galder.zamarreno Galder Zamarreño added a comment -

          This probably means a new Runtime type needs to be added for AS 5.1

          Show
          galder.zamarreno Galder Zamarreño added a comment - This probably means a new Runtime type needs to be added for AS 5.1
          Hide
          rob.stryker Rob Stryker added a comment -

          What (if any) are the structural changes between 5.0 and 5.1? Anything major? Any jar renames? Anything absolutely requiring a new runtime type?

          Show
          rob.stryker Rob Stryker added a comment - What (if any) are the structural changes between 5.0 and 5.1? Anything major? Any jar renames? Anything absolutely requiring a new runtime type?
          Hide
          rob.stryker Rob Stryker added a comment -

          Better yet, what exactly is preventing you from making a runtime for the latest 5.1? What's it say?

          In my workspace it says " This server type expects a version of 5.0 but the server directory is of version 5.1.0.CR1." as a warning but completing the wizard still works.

          Any more details?

          Show
          rob.stryker Rob Stryker added a comment - Better yet, what exactly is preventing you from making a runtime for the latest 5.1? What's it say? In my workspace it says " This server type expects a version of 5.0 but the server directory is of version 5.1.0.CR1." as a warning but completing the wizard still works. Any more details?
          Hide
          rob.stryker Rob Stryker added a comment -

          I checked out the source, built the AS, and it seems to work with the 5.0 server type. Wizard can finish, server can start. If there are no severe structural changes, then for now I'll say a new servertype is not necessary.

          Show
          rob.stryker Rob Stryker added a comment - I checked out the source, built the AS, and it seems to work with the 5.0 server type. Wizard can finish, server can start. If there are no severe structural changes, then for now I'll say a new servertype is not necessary.
          Hide
          maxandersen Max Rydahl Andersen added a comment -

          if not for structural changes I would have thought the new JMX api's would require a new server version ?

          Show
          maxandersen Max Rydahl Andersen added a comment - if not for structural changes I would have thought the new JMX api's would require a new server version ?
          Hide
          galder.zamarreno Galder Zamarreño added a comment -

          Hmmm, I still can't. I keep getting this message when trying to create the runtime:

          "The home directory does not exist, is missing key files, or is of the incorrect version."

          I'm running Tools 3.0.GA. Rob, did you verify this with GA or some other branch?

          Show
          galder.zamarreno Galder Zamarreño added a comment - Hmmm, I still can't. I keep getting this message when trying to create the runtime: "The home directory does not exist, is missing key files, or is of the incorrect version." I'm running Tools 3.0.GA. Rob, did you verify this with GA or some other branch?
          Hide
          galder.zamarreno Galder Zamarreño added a comment -

          p.s. that message should be more explicit

          Show
          galder.zamarreno Galder Zamarreño added a comment - p.s. that message should be more explicit
          Hide
          rob.stryker Rob Stryker added a comment -

          Sorry Galder. I didn't read the issue thoroughly. It should be committed to both 3.0.1 and 3.1.0 streams already. And the messages have already been clarified.

          @Max: While you're right that new API's are a difference, the problem is that they've backported the fixes to 5.0.x stream, which means that if they do come out with a 5.0.2 or 5.0.3 stream, the new API's will still be there.

          In all honesty, If I were ever to rewrite this stuff entirely, I could probably have only 1 server type and make everything absolutely dynamic, reading the server's version from the installation folder and then calculate everything from classpath container information to startup information to deployment stuff. The need for a new "Server Type" really is not great at all. The only primary difference here is whether the server starts with "deploy to the server area" or "deploy to metadata". That's basically all that changes. And the user can adjust that at his will in the server editor.

          Show
          rob.stryker Rob Stryker added a comment - Sorry Galder. I didn't read the issue thoroughly. It should be committed to both 3.0.1 and 3.1.0 streams already. And the messages have already been clarified. @Max: While you're right that new API's are a difference, the problem is that they've backported the fixes to 5.0.x stream, which means that if they do come out with a 5.0.2 or 5.0.3 stream, the new API's will still be there. In all honesty, If I were ever to rewrite this stuff entirely, I could probably have only 1 server type and make everything absolutely dynamic, reading the server's version from the installation folder and then calculate everything from classpath container information to startup information to deployment stuff. The need for a new "Server Type" really is not great at all. The only primary difference here is whether the server starts with "deploy to the server area" or "deploy to metadata". That's basically all that changes. And the user can adjust that at his will in the server editor.
          Hide
          galder.zamarreno Galder Zamarreño added a comment -

          Rob, so, that means you reproduced the problem? Did you get it working in any of the branches?

          Show
          galder.zamarreno Galder Zamarreño added a comment - Rob, so, that means you reproduced the problem? Did you get it working in any of the branches?
          Hide
          rob.stryker Rob Stryker added a comment -

          Galder:

          This was verified in 3.0.GA and was fixed in both 3.0.1 maintenance and 3.1 trunk a while ago. No commits were made on this JIRA as they were made in a previous commit. (commits 14204 and 14251)

          Show
          rob.stryker Rob Stryker added a comment - Galder: This was verified in 3.0.GA and was fixed in both 3.0.1 maintenance and 3.1 trunk a while ago. No commits were made on this JIRA as they were made in a previous commit. (commits 14204 and 14251)
          Hide
          maxandersen Max Rydahl Andersen added a comment -

          Rob, as a comment to "make everything absolutely dynamic, reading the servers version from the installation folder" would not be the solution - having a static version is relevant in context of runtime components i believe.

          Removing some of the static types does make sense though since they should just be a configuration option IMO (i.e. "deploy only server")

          Show
          maxandersen Max Rydahl Andersen added a comment - Rob, as a comment to "make everything absolutely dynamic, reading the servers version from the installation folder" would not be the solution - having a static version is relevant in context of runtime components i believe. Removing some of the static types does make sense though since they should just be a configuration option IMO (i.e. "deploy only server")
          Hide
          aklimkovich Anton Klimkovich added a comment -

          Verified on 2.0.0.GA-R200905020417-H7.
          Steps to verify:
          EXECUTE: Preferences - > Server -> Runtime environments
          EXECUTE: Press Add buttom and select JBoss AS 5.0
          EXECUTE: Add Jboss AS 5.1.0.CR1.
          ASSERT: Warning message: This server type expects a version of 5.0 but the server directory is of version 5.1.0.CR1.
          Finish button should be enabled.

          Show
          aklimkovich Anton Klimkovich added a comment - Verified on 2.0.0.GA-R200905020417-H7. Steps to verify: EXECUTE: Preferences - > Server -> Runtime environments EXECUTE: Press Add buttom and select JBoss AS 5.0 EXECUTE: Add Jboss AS 5.1.0.CR1. ASSERT: Warning message: This server type expects a version of 5.0 but the server directory is of version 5.1.0.CR1. Finish button should be enabled.

            People

            • Assignee:
              rob.stryker Rob Stryker
              Reporter:
              galder.zamarreno Galder Zamarreño
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development