glassfish
  1. glassfish
  2. GLASSFISH-16430

Embedded GlassFish should have fidelity with regular GlassFish.

    Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.0
    • Fix Version/s: 3.1.1, 3.1.2, 4.0
    • Component/s: embedded
    • Labels:
      None
    • Environment:

      ALL

      Description

      The GlassFish embedded inside user's application using org.glassfish.embeddable APIs should have fidelity with the regular GlassFish.

      This does NOT mean the running mode should be same (OSGi or non-OSGi). But it means that the functionality of the GlassFish must be same in terms of being able to run all Java EE applications as is.

        Issue Links

          Activity

          Hide
          Bhavanishankar added a comment -

          In 3.1, there is already some degree of fidelity in the web technology areas.

          In 3.2, the uncovered areas of full Java EE profile should also be covered.

          Show
          Bhavanishankar added a comment - In 3.1, there is already some degree of fidelity in the web technology areas. In 3.2, the uncovered areas of full Java EE profile should also be covered.
          Hide
          Bhavanishankar added a comment -

          Unable to run full profile CTS tests without having a fix for GLASSFISH-16546.

          Show
          Bhavanishankar added a comment - Unable to run full profile CTS tests without having a fix for GLASSFISH-16546 .
          Hide
          Bhavanishankar added a comment -

          This is resolved in 3.1.1.

          Show
          Bhavanishankar added a comment - This is resolved in 3.1.1.
          Hide
          shreedhar_ganapathy added a comment -

          Which build of 3.1.1 has this issue's resolution? Could you update the fix version to right release and build number? If this has been fixed in 3.1.2 branch, please use the 3.1.2_<buildnumber> fixVersion.

          Show
          shreedhar_ganapathy added a comment - Which build of 3.1.1 has this issue's resolution? Could you update the fix version to right release and build number? If this has been fixed in 3.1.2 branch, please use the 3.1.2_<buildnumber> fixVersion.
          Hide
          Bhavanishankar added a comment -

          Final build of 3.1.1 and all 3.1.2 builds would have this fix. Marking it resolved.

          Show
          Bhavanishankar added a comment - Final build of 3.1.1 and all 3.1.2 builds would have this fix. Marking it resolved.

            People

            • Assignee:
              Bhavanishankar
              Reporter:
              Bhavanishankar
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: