Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 9.0pe
    • Fix Version/s: 9.1pe_dev
    • Component/s: packaging
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      1,176

      Description

      GlassFish bundles dbschema.jar which comes from NetBeans (not sure about its
      version, but I guess it's from 5.0) w/o any modifications = w/o NB modules this
      module depends on. If one tryes to create appclication client beased on NetBeans
      platform then dbschema.jar is recognized as NB module by the application client
      and the application tryes to load dbschema module, but w/o success because of
      missing dependencies. This has following consequences:

      -in case of running appclient using appclient script from command line there's
      shown a warning to the user about missing dependencies, but he is able to continue

      -in case of running appclient using java web start there's a deadlock -
      warning dialog is not fully painted - there's no text, no UI components, simply
      said there's no way to continue or close the application

      -in case of creating custom classloaders hierarchy as I've described here[1] to
      workaround problem with dbschema.jar there's no way to get access to any
      enterprise resources from NetBeans module (there's at least no way to call EJB)

      Possible solution for this is to remove all "Openide-*" entries from
      dbschema.jar's manifest file, other one is to add dbschema's dependencies to
      glassfish or to work with NB engineers on spliting dbschema module into two
      parts - into a library which will be independent on anything else and could be
      shared between NB and GlassFish and a NB module which will provide "integration"
      of this library in the IDE

      [1]: http://blogs.sun.com/blog/entry/java_ee_application_client_on

        Activity

        Hide
        pjiricka added a comment -

        I don't know what are the plans regarding the appclient container for AS 9.1 (I
        saw in some e-mails that e.g. substantial reduction in size of the container is
        considered). Either way, I think it is an important goal to make sure that the
        NetBeans RCP can be used in application clients, as a frontend for Java EE
        applications.

        If several aspects are combined:

        • using webstart to launch appclients
        • small download size of the appclient container
        • rich application framework that NetBeans platform offers beyond Swing
        • NetBeans GUI builder (Matisse) as a productive way of building client apps
        • simplified programming model of Java EE 5 in the areas of persistence, EJB and
          web services
        • modularization/reduction of JRE size targetted for JDK 7 and making the JRE
          more competitive with Flash

        then we could have a very viable and competitive rich client environment.

        Show
        pjiricka added a comment - I don't know what are the plans regarding the appclient container for AS 9.1 (I saw in some e-mails that e.g. substantial reduction in size of the container is considered). Either way, I think it is an important goal to make sure that the NetBeans RCP can be used in application clients, as a frontend for Java EE applications. If several aspects are combined: using webstart to launch appclients small download size of the appclient container rich application framework that NetBeans platform offers beyond Swing NetBeans GUI builder (Matisse) as a productive way of building client apps simplified programming model of Java EE 5 in the areas of persistence, EJB and web services modularization/reduction of JRE size targetted for JDK 7 and making the JRE more competitive with Flash then we could have a very viable and competitive rich client environment.
        Hide
        raccah added a comment -

        For 9.1, we should try split the jar on the glassfish side. But, NB could
        really deliver the library jar instead, so that is filed in NB's issuezilla:
        <http://www.netbeans.org/issues/show_bug.cgi?id=87703>

        Show
        raccah added a comment - For 9.1, we should try split the jar on the glassfish side. But, NB could really deliver the library jar instead, so that is filed in NB's issuezilla: < http://www.netbeans.org/issues/show_bug.cgi?id=87703 >
        Hide
        mf125085 added a comment -

        reassigning to myself.

        Show
        mf125085 added a comment - reassigning to myself.
        Hide
        Tim Quinn added a comment -

        Shrinking the footprint of the app client container bits is a very important
        goal for us, but it depends on and would need to be part of work that is planned
        for 9.2. So this part, at least, is probably not going to be able to make it
        for 9.1

        Show
        Tim Quinn added a comment - Shrinking the footprint of the app client container bits is a very important goal for us, but it depends on and would need to be part of work that is planned for 9.2. So this part, at least, is probably not going to be able to make it for 9.1
        Hide
        mf125085 added a comment -

        The dbschema.jar in glassfish has been cleaned up and integrated into the build
        system:

        http://fisheye5.cenqua.com/changelog/glassfish/?cs=MAIN:mf125085:20061110195017

        Show
        mf125085 added a comment - The dbschema.jar in glassfish has been cleaned up and integrated into the build system: http://fisheye5.cenqua.com/changelog/glassfish/?cs=MAIN:mf125085:20061110195017
        Hide
        raccah added a comment -

        Details of what is in the subset can be found in the attachment in issue 1478
        which was filed to track the fact that we were not able to use the nb 5.5 fcs
        version because of some capture schema issues.

        Show
        raccah added a comment - Details of what is in the subset can be found in the attachment in issue 1478 which was filed to track the fact that we were not able to use the nb 5.5 fcs version because of some capture schema issues.

          People

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

            Dates

            • Created:
              Updated:
              Resolved: