Al & all,
Al Fogleson wrote:
> OK weird question here, since I worked this problem and found that orion is
> placing the binding in the / heirarchy and not the java:comp/env heirarchy,
> is there any reason for that???
>
> Maybe I am lost but isnt the java:comp/env/ejb heirarchy where they should
> go? (although I vaguely recall that in 1.1 it is not required to be placed
> there, it seems like every other app server I have used puts them there. I
> had to resort to using forte and its JNDI browser to find the hello bean
> that Ernst has made. once I found that it was a simple matter of changing
> his "java:comp/ejb/hello" call to a "hello.ejb.Hello" and it was found
> easily.
Thanks for pointing this out. I tried to lookup entries under
java:comp/env, but I could not find anything there. Magnus pointed out
that there needs to be a reference in the web.xml to the bean used. So I
added in the web.xml the following:
<ejb-ref>
<ejb-ref-name>ejb/hello</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>hello.ejb.HelloHome</home>
<remote>hello.ejb.Hello</remote>
</ejb-ref>
According to section 7.3.1.1 in `Designing Enterprise Application with
the Java 2 Platform, Enterprise Edition', that should do the trick. But
it doesn't. I think this piece of XML should allow me to do the lookup
as `java:comp/env/ejb/hello', can anybody point out where I go wrong?
Is there a way to see what Orion thinks of a deployment descriptor? Some
secret --verbose option, perhaps? I would like to see what it places in
JNDI contexts.
> Probably something for Magnus or Karl to aqnswer for me. :) maybe i am just
> totally confused after evaluating so many servers.
Thanks again, (P)Al :)
Ernst
