That's what I'm doing now. And it does work like a charm :) Stupid me, I didn't think of this before (I was the one who originally posted this question). This really makes you independent of JNDI, is much more performant and increases your flexibility. For local beans it doesn't really matter what the official JNDI name is (i.e. what's in jboss.xml) if you use the ejb-local-ref tag in ejb-jar.xml :)
Cheers, Bernhard -----Urspr�ngliche Nachricht----- Von: Vincent Harcq [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 13. Februar 2002 20:50 An: 'Jozsa Kristof'; 'Dmitri Colebatch' Cc: [EMAIL PROTECTED] Betreff: RE: [Xdoclet-user] JNDI names for JBoss 3 This one is driving everybody mad I see. Do you really REALLY need to use a jndi-name to look local beans. Ejb-link is a trick that avoid jndi lookup and use internal ejb jar lookup to find a bean. Why not use simply * @ejb:ejb-ref * view-type="local" * ejb-name="TargetBean" No ejb-ref No jndi-name It works like a charm on 2.4. I am quite sure it does as well on 3.0 This is completely independant of local-jndi-name and of local/remote access > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf > Of Jozsa Kristof > Sent: mercredi 13 f�vrier 2002 20:28 > To: Dmitri Colebatch > Cc: [EMAIL PROTECTED] > Subject: Re: [Xdoclet-user] JNDI names for JBoss 3 > > > On Wed, Feb 13, 2002 at 11:42:48PM +1100, Dmitri Colebatch wrote: > > > > I want my beans to have JNDI names in the style of > ejb/beanname. > > > > Problem is, for bean with local interface only (eg. local CMP > > > > entity > > > > beans) > > > > the jndi-name attribute of the @ejb:bean tag doesn't > work. Well it > > > works > > > > but > > > > if puts my only the beanname as jndi name in jboss.xml. > If I use > > > > the local-jndi-name attribute it works, however this of course > > > > puts local-jndi-name tags in my jboss.xml. Those > local-jndi-names > > > > don't > > > work > > > > for > > > > me because JBoss has trouble with finding the beans in > JNDI then. > > > > > > > > Has anyone had similar problems? > > > > > > Use local-jndi-name for local beans, jndi-name is for > remote ones. I > > > don't know about local-jndi-name in jboss.xml, but I've heard > > > jboss2.4 can't lookup from global jndi namespace (or > something like > > > that). I'm sure Vincent or Dimtri will comment on it.... > > > > yeah, I'm still trying to get my head around this one. As > soon as I > > know how I'm suppose to make my local beans available in jndi I'll > > ensure XDoclet can do it with a tag. Problem at the moment is my > > understanding of JBoss - as you noticed, local-jndi-name > doesn't seem > > to work :( > > So the current JBoss3 snapshot + current XDoclet is not > usable at the moment, right? (I'm asking only, because I > still couldn't move away from the jboss 2002-01-14 cvs snap, > CMP2 just doesn't work further that point (or if anyone can > confirm the opposite, please do so). > > Dim, if you're working on xdoclet's jboss3 support, can > please (*please*) drop a note to the list when it arrives to > an actually working point..? It'd be important, and I guess > not only for me than other jboss+xdoclet users as well. > (Until that point, I'll continue developing with the snapshot > mentioned above). > > thanks, > > Christopher > -- > .Digital.Yearning.for.Networked.Assassination.and.Xenocide > > _______________________________________________ > 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 _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
