Oh I see.
No sorry I can not help you here.  I am running web to ejb through a
unique "command pattern" session beans that I leaved on remote.  And
because the call is optimized (no serialization) with Jboss I do not
care a lot here.
On jboss-dev, they are working very hard for the moment on a lot of
stuff, have you tried looking for info there ?

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED]] On Behalf 
> Of Dmitri Colebatch
> Sent: mercredi 13 février 2002 21:43
> To: [EMAIL PROTECTED]; 'Jozsa Kristof'
> Cc: [EMAIL PROTECTED]
> Subject: Re: [Xdoclet-user] JNDI names for JBoss 3
> 
> 
> Vincent,
> 
> What about lookups from Jetty or Tomcat?
> 
> I haven't been able to get links to work from there (with the 
> appropriate link code in the web.xml) - have you had success there?
> 
> cheers
> dim
> 
> ----- Original Message -----
> From: "Vincent Harcq" <[EMAIL PROTECTED]>
> To: "'Jozsa Kristof'" <[EMAIL PROTECTED]>; "'Dmitri 
> Colebatch'" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Thursday, February 14, 2002 6:49 AM
> Subject: 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

Reply via email to