glassfish
  1. glassfish
  2. GLASSFISH-19036

Deployment of the same EJB app with a different name should succeed by default

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 4.0_b51
    • Fix Version/s: 4.1
    • Component/s: ejb_container
    • Labels:
      None

      Description

      Currently the 2nd deployment of the same EJB app but with a different --name option fails because of the conflict in GF-specific (non-portable) JNDI names. It should succeed with a warning and either the 2nd app shouldn't get non-portable JNDI names, or get some adjusted version.

        Activity

        Hide
        marina vatkina added a comment -

        The same problem is happening if 2 EJBs share the same interface

        Show
        marina vatkina added a comment - The same problem is happening if 2 EJBs share the same interface

          People

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

            Dates

            • Created:
              Updated: