Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.0
    • Fix Version/s: 3.0.0
    • Component/s: javaee6, Web Profile
    • Security Level: public (Regular issues)
    • Labels:
      None

      Description

      Enhancements for the java ee 6 global JNDI additions specified by JSR 316,

        Activity

        Hide
        David Jencks added a comment -

        This is mostly implemented. Further work is needed to make the openejb and geronimo naming systems work better together, and to figure out exactly what is supposed to be exposed in the app client and what "global" means there. Also whether global datasources need to be redefined on the app client and what that means for jta.

        Show
        David Jencks added a comment - This is mostly implemented. Further work is needed to make the openejb and geronimo naming systems work better together, and to figure out exactly what is supposed to be exposed in the app client and what "global" means there. Also whether global datasources need to be redefined on the app client and what that means for jta.
        Hide
        David Jencks added a comment -

        I have a working solution for exposing server side global datasources to app clients based on:
        1. representing datasource definitions as naming References
        2. using an ObjectFactory service using aries jndi to turn these definitions into the osgi services needed to supply the datasource from jndi lookups
        3. copying all the global jndi entries into the openejb global tree
        4. using the openejb jndi transport to pull the datasource Reference back to the app client where it can be set up using step (2) just like all other datasources.

        This is currently in the osgi-friendly code I periodically push. I'll work on getting it committed to svn.

        Show
        David Jencks added a comment - I have a working solution for exposing server side global datasources to app clients based on: 1. representing datasource definitions as naming References 2. using an ObjectFactory service using aries jndi to turn these definitions into the osgi services needed to supply the datasource from jndi lookups 3. copying all the global jndi entries into the openejb global tree 4. using the openejb jndi transport to pull the datasource Reference back to the app client where it can be set up using step (2) just like all other datasources. This is currently in the osgi-friendly code I periodically push. I'll work on getting it committed to svn.
        Hide
        David Jencks added a comment -

        pushed to svn in rev 1140357

        Show
        David Jencks added a comment - pushed to svn in rev 1140357
        Hide
        Rex Wang added a comment -

        has been resolved. close it.

        Show
        Rex Wang added a comment - has been resolved. close it.

          People

          • Assignee:
            David Jencks
            Reporter:
            Rick McGuire
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development