1 Reply Latest reply on Jul 1, 2003 3:02 PM by Erik Hansen

    EJB not bound using XDoclet generated Util class

    Erik Hansen Newbie

      The XDoclet generated Util classes look pretty straightforward, but when I try to use getHome/getLocalHome I get "ejb not bound" for the name. It looks like the generated classes aren't looking up the JNDI name of the bean properly (I see them in JNDIView). Has anyone used these util classes without a problem?

        • 1. Re: EJB not bound using XDoclet generated Util class
          Erik Hansen Newbie

          Well, I found a solution to my problem, yet I don't understand fully why the default works the way it does.

          I needed to add an @ejb.util generate="physical" tag to the bean class.

          It's a bit confusing that the tag in the build.xml file will generate a util class, while the @ejb.util tag in the class file (if omitted) would normally mean that a util class wouldn't be generated. Why does this exist in two places? A question for the XDoclet group for sure, but I wanted to pass on my finding.

          Followup question: when does one use physical vs. logical lookups? Is there a reason to use the fully qualified component name over the JNDI name or vice versa?