Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.0
    • Fix Version/s: 3.0.0
    • Component/s: deployment, naming
    • Security Level: public (Regular issues)
    • Labels:
      None

      Description

      Javaee platform spec describes some new jndi java: contexts that are more shared between components.
      java:comp (existing)
      java:module
      java:app
      java:global

      My first idea for implementing this:

      1. in RootContext, have the thread local represent java: rather than java:comp. So all the namespaces will be in the Context object.
      2. Construct this Context by federating objects for each scope. We'll have to maintain a global context somewhere. The others can presumably be constructed during deployment and set up in the existing gbeans for the app components.
      3. Modify the naming builders to put stuff into the right namespace.

        Activity

        Hide
        David Jencks added a comment -

        rev 901935 basically does the work described above. There aren't really any tests yet.

        More stuff to do:

        1. detect if an entry is specified twice and object if it is specified differently.
        2. find out what is meant for web apps about java:comp and java:module being "the same"
        3. figure out if/how to get the global context available to app clients.

        Also we could probably have a urlHandler for jca: and ger: contexts. What we used to do was bogus, treating the "scheme" part as a name component.

        Show
        David Jencks added a comment - rev 901935 basically does the work described above. There aren't really any tests yet. More stuff to do: 1. detect if an entry is specified twice and object if it is specified differently. 2. find out what is meant for web apps about java:comp and java:module being "the same" 3. figure out if/how to get the global context available to app clients. Also we could probably have a urlHandler for jca: and ger: contexts. What we used to do was bogus, treating the "scheme" part as a name component.
        Hide
        David Jencks added a comment -

        rev 902527 moves web app jndi context setup to a different object since jsf needs to be set up before the web app. Both the myfaces instance construction service and the web context now have a reference to the jndi object.

        Show
        David Jencks added a comment - rev 902527 moves web app jndi context setup to a different object since jsf needs to be set up before the web app. Both the myfaces instance construction service and the web context now have a reference to the jndi object.
        Hide
        David Jencks added a comment -

        Rev 945814 and 945820 add support for jndi configuration in application.xml

        Show
        David Jencks added a comment - Rev 945814 and 945820 add support for jndi configuration in application.xml
        Hide
        David Jencks added a comment -

        rev 947211 moves around jndi configuration in openejb so that the jndi enc context in openejb is an immutable federation of the global, app, module, and comp context constructed by geronimo, and an additional writable comp context that openejb can bind stuff like TimerService and EJBContext into. Injections now seem to work in openejb.

        Show
        David Jencks added a comment - rev 947211 moves around jndi configuration in openejb so that the jndi enc context in openejb is an immutable federation of the global, app, module, and comp context constructed by geronimo, and an additional writable comp context that openejb can bind stuff like TimerService and EJBContext into. Injections now seem to work in openejb.
        Hide
        David Jencks added a comment -


        rev 950397 (see also GERONIMO-5117) moves jndi support directly into Modules and straightens out when contexts are shared between submodules and ears and modules.

        Show
        David Jencks added a comment - rev 950397 (see also GERONIMO-5117 ) moves jndi support directly into Modules and straightens out when contexts are shared between submodules and ears and modules.
        Hide
        Rick McGuire added a comment -

        I believe this work is complete now, correct?

        Show
        Rick McGuire added a comment - I believe this work is complete now, correct?
        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:
            David Jencks
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development