[jboss-user] [JNDI/Naming/Network] - Re: EJB3: @Resource name only EJBContext, not in InitialCont

2008-02-15 Thread wingtung.leung
jaikiran wrote : Which version of JBoss do you use? I tested this on my local JBoss-4.2.2 setup with an sample application: | JBoss-4.0.5 with extra EJB3 support. I have tested it on JBoss-4.2.2, and it works fine there. So we will need to update our EJB3 component, or upgrade JBoss

[jboss-user] [JNDI/Naming/Network] - Re: EJB3: @Resource name only EJBContext, not in InitialCont

2008-02-14 Thread jaikiran
anonymous wrote : new InitialContext().lookup(java:comp/env/jms/vpoToEmotiveQueue); It depends on where you are doing the lookup using the InitialContext. Is this being done in the same bean where the @Resource is defined? In which case, this should work. However, if you are doing the lookup

[jboss-user] [JNDI/Naming/Network] - Re: EJB3: @Resource name only EJBContext, not in InitialCont

2008-02-14 Thread wingtung.leung
jaikiran wrote : | It depends on where you are doing the lookup using the InitialContext. Is this being done in the same bean where the @Resource is defined? In which case, this should work. However, if you are doing the lookup in some other component of your application, then this wont

[jboss-user] [JNDI/Naming/Network] - Re: EJB3: @Resource name only EJBContext, not in InitialCont

2008-02-14 Thread jaikiran
Which version of JBoss do you use? I tested this on my local JBoss-4.2.2 setup with an sample application: | @Stateless | @Remote ({UserManager.class}) | @RemoteBinding (jndiBinding = RemoteUserManagerBean) | @Resources( { | @Resource(type = Queue.class, name = jms/A,