Re: comp_name problem

"[email protected]" <[email protected]>
Newsgroups gmane.comp.java.xdoclet.user
Message-ID <[email protected]>
You r not help me so much...
Any other idea?
---------- Initial Header -----------

>From      : [email protected]
To          : "End-user support for the XDoclet code generator" [email protected]
Cc          : 
Date      : Thu, 15 Jun 2006 11:54:26 -0700 (PDT)
Subject : Re: [Xdoclet-user] comp_name problem







> 
> 
> --- "[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
> >
> AFAIR - Physiocal jndi name shall be specified with 
> specific jboss tags. 
> ( Though I wrote significant part  of this stuff
> myself, I forgot a lot in last 3 years )
> 
> regards,
> 
> ----[ Konstantin Pribluda http://www.pribluda.de ]----------------
> Still using XDoclet 1.x?  XDoclet 2 is released and of production quality.
> check it out: http://xdoclet.codehaus.org
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> 
> 
> _______________________________________________
> xdoclet-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/xdoclet-user
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.