glassfish
  1. glassfish
  2. GLASSFISH-11529

[spec request] The global jndi namespace should not contain local session beans if interapplication calls are not supported.

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: V3
    • Fix Version/s: future release
    • Component/s: ejb_container
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      11,529

      Description

      This is kind of a follow up to a bug where I was asking for default JNDI names
      before EJB 3.1 (https://glassfish.dev.java.net/issues/show_bug.cgi?id=577).

      I love the new default JNDI names and I think the different namespaces
      (global,app,module) where a great idea however I have one complaint.

      The specs don't require support for inter-application calls on local session
      beans. Even though some app servers allow it I'm fine with GlassFish not
      allowing it. However I think it unnecessary and confusing to publish global JNDI
      names for local session beans that can't be called.

      I'd like to see the spec and GlassFish only require the creation of global JNDI
      names for EJBs that support inter-application calling.

        Activity

        Hide
        chasetec added a comment -

        To clarify "I'd like to see the spec and GlassFish only require the creation of
        global JNDI names for EJBs that support inter-application calling."

        I mean just the global namespace. There should still be standard jndi names for
        local session beans in the app and module namespaces.

        Show
        chasetec added a comment - To clarify "I'd like to see the spec and GlassFish only require the creation of global JNDI names for EJBs that support inter-application calling." I mean just the global namespace. There should still be standard jndi names for local session beans in the app and module namespaces.
        Hide
        marina vatkina added a comment -

        The current spec says this: "The container registers a separate JNDI name entry
        for each local business interface, each remote business interface, and any
        no-interface view, 2.x local home interface, and 2.x remote home interface."

        Show
        marina vatkina added a comment - The current spec says this: "The container registers a separate JNDI name entry for each local business interface, each remote business interface, and any no-interface view, 2.x local home interface, and 2.x remote home interface."

          People

          • Assignee:
            marina vatkina
            Reporter:
            chasetec
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: