Re: comp_name problem

Well, I'm no expert, but it seems OK though it's been a while since I
did any JNDI and that was on WebLogic, not JBoss, so I could be way
off here...

Does a request for the EJB actually fail, or is it just that it
doesn't appear in the JNDI viewer?
  If the former, then I'd double-check to be sure it's not a
difference somewhere between "RequestDispatcher" and
"RequestDispatcherHome", as there seems to be some confusion in your
post - could just be a typo/edit though...
  If the latter, then maybe the viewer is looking in a different
namespace from the EJB - it depends how JBoss works, but maybe you'll
see it there as "ejb/RequestDispatcherHome"?  The "java:comp/env/"
part is the local, 'logical' namespace populated for the application
context using the jboss.xml, & which may not be available to the JNDI
viewer if that's running at a 'server' level.

  Other than that, search the logs to see if there's any info relating
to the EJB being loaded - with WLS you'll see some info, but I don't
know about JBoss.

/Gwyn

On 16/06/06, [email protected] <[email protected]> wrote:
>
> I create muy jboss.xml I post you it:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 2.4//EN" "http://www.jboss.org/j2ee/dtd/jboss_2_4.dtd">
>
> <jboss>
>
>    <enterprise-beans>
>
>      <!--
>        To add beans that you have deployment descriptor info for, add
>        a file to your XDoclet merge directory called jboss-beans.xml that contains
>        the <session></session>, <entity></entity> and <message-driven></message-driven>
>        markup for those beans.
>      -->
>
>       <session>
>          <ejb-name>RequestDispatcher</ejb-name>
>          <jndi-name>ejb/RequestDispatcherHome</jndi-name>
>          <local-jndi-name>RequestDispatcherLocal</local-jndi-name>
>
>       </session>
>
>       <message-driven>
>          <ejb-name>CtsToFrontEnd</ejb-name>
>          <destination-jndi-name>queue/ctsToFrontEnd</destination-jndi-name>
>
>       </message-driven>
>     <!--
>       write a merge file jboss-webservices.ent for webservice-description
>     -->
>
>    </enterprise-beans>
>
>    <resource-managers>
>    </resource-managers>
>
>   <!--
>     | for container settings, you can merge in jboss-container.xml
>     | this can contain <invoker-proxy-bindings/> and <container-configurations/>
>   -->
>
> </jboss>
>
>
> ---------- Initial Header -----------
>
> >From      : [email protected]
> To          : "End-user support for the XDoclet code generator" [email protected]
> Cc          :
> Date      : Thu, 15 Jun 2006 17:02:23 +0100
> Subject : Re: [Xdoclet-user] comp_name problem
>
>
>
>
>
>
>
> > Are you generating the JBoss-specific ejb xml file, as unless I
> > mis-remember, the actual mapping of the ejb to the jndi is the
> > appserver-specific part, e.g. with weblogic, it's in the
> > weblogic-ejb-jar.xml.
> >
> > /Gwyn
> >
> > On 15/06/06, [email protected] <[email protected]> wrote:
> > > hi all
> > > i'm using xdoclet with myeclipse for generating ejb.
> > > these are my tags :
> > >
> > >  * @ejb.bean name="RequestDispatcher"
> > >  *           display-name="Name for RequestDispatcher"
> > >  *           description="Description for RequestDispatcher"
> > >  *           jndi-name="ejb/RequestDispatcherHome"
> > >  *           type="Stateless"
> > >  *           view-type="remote"
> > >  *           transaction-type="Bean"
> > >
> > > the problem is that xdoclet create in  RequestDispatcherHome
> > > the COMP_NAME="java:comp/env/ejb/RequestDispatcher";
> > > I mean there is nothing wrong in that but when I try to see my jndi tree in my jboss jndi viewer I cannot see that path bound.
> > > What's wrong?
> > > regards
> >
> >
> > _______________________________________________
> > xdoclet-user mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/xdoclet-user
> >
>
>
>
> _______________________________________________
> xdoclet-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/xdoclet-user
>