Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: V3
    • Fix Version/s: not determined
    • Component/s: deployment
    • Labels:
      None
    • Environment:

      Operating System: Mac OS X
      Platform: Macintosh

    • Issuezilla Id:
      10,496

      Description

      Glassfish v3 comes with compatibility feature: asadmin deploy --property compatibility=v2 foo.ear

      The problem: this feature is only available from the CLI. There should be global e.g. setting (in
      domain.xml) and accessible from the admin UI (EJB container node) to be set persistently. A local setting,
      e.g. in the deployment descriptor: sun-*.xml .

      Reason: a majority of GF v2 projects is using Hudson + Maven / Ant for deployment. Most of the projects,
      are not 100% Java EE compatible but can be deployed to GF v2 without any problems. The migration even
      of such projects should be as smooth, as possible.

        Activity

        Hide
        Hong Zhang added a comment -

        Right, from the further information provided by the user, the NB (ant) is doing
        the right packaging (item 1 of Section 8.2.1). The user case was NB (maven).

        Show
        Hong Zhang added a comment - Right, from the further information provided by the user, the NB (ant) is doing the right packaging (item 1 of Section 8.2.1). The user case was NB (maven).
        Hide
        Hong Zhang added a comment -

        I have checked in the changes to add a compatibility element in the
        sun-application.xml. This will provide a way for autodeploy/JSR88 to set the
        compatibility flag to have v2 jar visibility behavior. I will keep the issue
        open but downgrade to P3 for further enhancements on providing useful warning
        messages for the cases where we could detect such packaging.

        Show
        Hong Zhang added a comment - I have checked in the changes to add a compatibility element in the sun-application.xml. This will provide a way for autodeploy/JSR88 to set the compatibility flag to have v2 jar visibility behavior. I will keep the issue open but downgrade to P3 for further enhancements on providing useful warning messages for the cases where we could detect such packaging.
        Hide
        Hong Zhang added a comment -

        One more request that's related to this property came from this forum thread:
        http://forums.java.net/jive/post!reply.jspa?messageID=375716

        Seems in v2, we also added module root level jars to the classpath, we should
        probably also provide this jar visibility through the property in v3.1

        Show
        Hong Zhang added a comment - One more request that's related to this property came from this forum thread: http://forums.java.net/jive/post!reply.jspa?messageID=375716 Seems in v2, we also added module root level jars to the classpath, we should probably also provide this jar visibility through the property in v3.1
        Hide
        Tom Mueller added a comment -

        Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

        Show
        Tom Mueller added a comment - Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.
        Hide
        erpomata added a comment -

        Any new about this issue?

        Show
        erpomata added a comment - Any new about this issue?

          People

          • Assignee:
            Hong Zhang
            Reporter:
            abien
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated: