ejb-spec
  1. ejb-spec
  2. EJB_SPEC-105

Remote JNDI naming convention isn't clear enough

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      Based on this thread:

      http://java.net/projects/ejb-spec/lists/users/archive/2012-11/message/17

      It seems as though vendors are still not clear that Remote JNDI names should not be any different from Local JNDI names. Based on some initial feedback from the EG, it seems as though the EG believes it is clear enough in the spec. I would like to request that the EJB EG provide further clarity, or that members representing organizations that don't believe the standard JNDI names apply to remote (Apache, JBoss/RedHat) clarify why they believe as such.

        Activity

        Hide
        John D. Ament added a comment -

        Title should be "Remote JNDI naming convention isn't clear enough."

        Show
        John D. Ament added a comment - Title should be "Remote JNDI naming convention isn't clear enough."
        Hide
        marina vatkina added a comment -

        fixed

        Show
        marina vatkina added a comment - fixed

          People

          • Assignee:
            marina vatkina
            Reporter:
            John D. Ament
          • Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: