glassfish
  1. glassfish
  2. GLASSFISH-18020

[UB]Errors in JNDI chapter of Application Development Guide

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.1
    • Fix Version/s: 3.1.2
    • Component/s: docs
    • Labels:
      None

      Description

      Issue GLASSFISH-17356 reports the following errors and omissions in the JNDI chapter of the Application Development Guide:

      Additionally, actual documentation is poor and has many errors.
      In http://docs.oracle.com/cd/E18930_01/html/821-2418/beans.html#beanv and http://download.oracle.com/docs/cd/E18930_01/html/821-2418/beans.html the examples presents typo erros resulting in badly formatted XML.

      In reference http://glassfish.java.net/javaee5/ejb/EJB_FAQ.html, the doc looks like a bit clearer. Otherwise, in section "What is the relationship between @EJB and ejb-ref/ejb-local-ref?" it gives hints about the relationship between @EJB and ejb-ref but is unclear about the relationship with jndi-name inside glassfish-web.xml.

      What is preferred to make remote invocation? lookup name inside web.xml or jndi-name inside glassfish-web.xml? What are the differences between these strategies?
      I couldn't make work any of these alternatives. It worked for me just specifying mapped-name inside web.xml and referencing the IP 127.0.0.1.

      Could someone add comments about which kind of network issues may arise from these configuration?
      Could someone at least improve logging to make possible to identify the bugs in each specific environment?

      1. jndi.pdf
        93 kB
        Rebecca Parks

        Issue Links

          Activity

          Hide
          Rebecca Parks added a comment -

          I cannot answer these questions myself. I need input from engineering. I'm told that Cheng is the JNDI expert, so I'm assigning this issue to him temporarily so he can supply the info I need. He can then reassign to me.

          Show
          Rebecca Parks added a comment - I cannot answer these questions myself. I need input from engineering. I'm told that Cheng is the JNDI expert, so I'm assigning this issue to him temporarily so he can supply the info I need. He can then reassign to me.
          Hide
          Rebecca Parks added a comment -

          By the way, "documentation is poor and has many errors" is not helpful. Only ONE specific error was pointed out. I did fix this, the typo where a slash was missing from a closing element.

          Show
          Rebecca Parks added a comment - By the way, "documentation is poor and has many errors" is not helpful. Only ONE specific error was pointed out. I did fix this, the typo where a slash was missing from a closing element.
          Hide
          Cheng Fang added a comment -

          change from

          <ejb-ref>
             <ejb-ref-name>ejb/Foo</ejb-ref-name>
             <jndi-name>corbaname:iiop:host:port#a/b/Foo</jndi-name>
          <ejb-ref>
          

          to

          <ejb-ref>
             <ejb-ref-name>ejb/Foo</ejb-ref-name>
             <jndi-name>corbaname:iiop:host:port#a/b/Foo</jndi-name>
          </ejb-ref>
          

          change from

          The only difference is that the deployer maps the ejb-reference element to an interoperable name in a GlassFish Server deployment descriptor file instead of to a simple global JNDI name.

          to

          The only difference is that the deployer maps the ejb-ref element to an interoperable name in the GlassFish deployment descriptor instead of to a simple global JNDI name.

          Show
          Cheng Fang added a comment - change from <ejb-ref> <ejb-ref-name>ejb/Foo</ejb-ref-name> <jndi-name>corbaname:iiop:host:port#a/b/Foo</jndi-name> <ejb-ref> to <ejb-ref> <ejb-ref-name>ejb/Foo</ejb-ref-name> <jndi-name>corbaname:iiop:host:port#a/b/Foo</jndi-name> </ejb-ref> change from The only difference is that the deployer maps the ejb-reference element to an interoperable name in a GlassFish Server deployment descriptor file instead of to a simple global JNDI name. to The only difference is that the deployer maps the ejb-ref element to an interoperable name in the GlassFish deployment descriptor instead of to a simple global JNDI name.
          Hide
          Cheng Fang added a comment -

          assign back to Rebecca. This chapter is about JNDI and its coverage looks fine to me.

          Show
          Cheng Fang added a comment - assign back to Rebecca. This chapter is about JNDI and its coverage looks fine to me.
          Hide
          Rebecca Parks added a comment -

          Attached the edited JNDI chapter of the Dev Guide.

          Show
          Rebecca Parks added a comment - Attached the edited JNDI chapter of the Dev Guide.
          Hide
          Rebecca Parks added a comment -

          The companion bug is closed. The filer of that bug is unlocatable and the assignee is deceased.

          I did due diligence with this bug, enlisting Cheng's help. This is as fixed as it's likely to get.

          Show
          Rebecca Parks added a comment - The companion bug is closed. The filer of that bug is unlocatable and the assignee is deceased. I did due diligence with this bug, enlisting Cheng's help. This is as fixed as it's likely to get.

            People

            • Assignee:
              Rebecca Parks
              Reporter:
              Paul Davies
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: