glassfish
  1. glassfish
  2. GLASSFISH-18869

deploy --type does not accept valid archive types

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0_b59
    • Component/s: deployment
    • Labels:
      None

      Description

      I would expect --type option in deployment to accept all valid archive types supported in a runtime. That's not the case; it only accepts osgi for some reason. See the error below:

      ss141213@Sahoo:/tmp$ asadmin deploy --type war ~/bugs/FirstV3Test/dist/FirstV3Test.war
      remote failure: Error occurred during deployment: There is no installed container capable of handling this application FirstV3Test. Please see server.log for more details.
      Command deploy failed.

        Activity

        Hide
        Hong Zhang added a comment -

        Yeah, I will do that.

        Show
        Hong Zhang added a comment - Yeah, I will do that.
        Hide
        Sanjeeb Sahoo added a comment -

        We should update the help text for deploy to mention about all the allowable types. Could you do that Hong?

        Show
        Sanjeeb Sahoo added a comment - We should update the help text for deploy to mention about all the allowable types. Could you do that Hong?
        Hide
        Hong Zhang added a comment -

        Yes, I have made some changes in this area when I was working on another issue. But I haven't got a chance to verify if that set of the changes were all the changes needed to address this requirement. Thanks for verifying this for me. I will go ahead and mark the issue as fixed.

        Show
        Hong Zhang added a comment - Yes, I have made some changes in this area when I was working on another issue. But I haven't got a chance to verify if that set of the changes were all the changes needed to address this requirement. Thanks for verifying this for me. I will go ahead and mark the issue as fixed.
        Hide
        Jeremy_Lv added a comment -

        Environment to test
        version:GFv4(update by 2012/10/24)
        Platform:Win 7
        JDK:jdk1.7.0_04

        Show
        Jeremy_Lv added a comment - Environment to test version:GFv4(update by 2012/10/24) Platform:Win 7 JDK:jdk1.7.0_04
        Hide
        Jeremy_Lv added a comment -

        related applications have been attached

        Show
        Jeremy_Lv added a comment - related applications have been attached
        Hide
        Jeremy_Lv added a comment - - edited

        Hong:
        Have anyone fixed this scenario already? Nowadays, I can deploy with --type option successfully. The commands are as follows:
        1.asadmin deploy --type war test_sample1.war
        2.asadmin deploy --type ejb singleton-osgi-1.0.jar
        3.asadmin deploy --type osgi singleton-osgi-1.0.jar
        4.asadmin deploy --type ear Jar.ear


        I will attached my test applications to JIRA later

        Show
        Jeremy_Lv added a comment - - edited Hong: Have anyone fixed this scenario already? Nowadays, I can deploy with --type option successfully. The commands are as follows: 1.asadmin deploy --type war test_sample1.war 2.asadmin deploy --type ejb singleton-osgi-1.0.jar 3.asadmin deploy --type osgi singleton-osgi-1.0.jar 4.asadmin deploy --type ear Jar.ear I will attached my test applications to JIRA later
        Hide
        Tom Mueller added a comment -

        Marking the fix version field as "future-release". This is based on an evaluation by John, Michael, and Tom WRT to the PRD for the Java EE 7 RI/SDK. This issues was deemed to not be a P1 for that release. If this is in error or there are other reasons why this RFE should be targeted for the Java EE 7 RI/SDK release, then change the fix version field back to an appropriate build.

        Show
        Tom Mueller added a comment - Marking the fix version field as "future-release". This is based on an evaluation by John, Michael, and Tom WRT to the PRD for the Java EE 7 RI/SDK. This issues was deemed to not be a P1 for that release. If this is in error or there are other reasons why this RFE should be targeted for the Java EE 7 RI/SDK release, then change the fix version field back to an appropriate build.
        Hide
        Sanjeeb Sahoo added a comment -

        For the sake of completeness, we should support --type=<any supported archive type in current runtime>. I don't mind you making it an improvement or bug as long as it is done and not lost in the stack somewhere.

        Show
        Sanjeeb Sahoo added a comment - For the sake of completeness, we should support --type=<any supported archive type in current runtime>. I don't mind you making it an improvement or bug as long as it is done and not lost in the stack somewhere.
        Hide
        Hong Zhang added a comment -

        This is the expected behavior, currently the supported value of the type option is only "osgi", I think we discussed before about the history/reasoning behind this , we could possibly enhance the type option to support more archive types.

        Show
        Hong Zhang added a comment - This is the expected behavior, currently the supported value of the type option is only "osgi", I think we discussed before about the history/reasoning behind this , we could possibly enhance the type option to support more archive types.

          People

          • Assignee:
            Hong Zhang
            Reporter:
            Sanjeeb Sahoo
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: