Hi, not reliably but you can implement you own InitialContextFactory to translate jndi names easily Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau
2014-01-29 Jarek Dąbrowski <[email protected]>: > Hi, > yes, it's not standard jndi, but this jndi is used by application and work > when application is deployed on WAS 6.1. > My question is: > Is it possible to use this jndi in OpenEJB? > > > 2014-01-29 Romain Manni-Bucau <[email protected]> > >> Hi >> >> what's com/starts/pl/AccountsBean? doesn't look standard jndi >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >> >> >> >> 2014-01-29 Jarek Dąbrowski <[email protected]>: >> > Hello, >> > I have an ear with application which works on WAS 6.1. >> > Bean PersonBean (which is in this ear) gets another bean (AccountsBean) >> by >> > jndi: >> > context.lookup("com/starts/pl/AccountsBean"); >> > It works on WAS 6.1 >> > >> > I try to test PersonBean using OpenEJB in Eclipse. >> > I have a problem with this jndi, when I try to set AccountsBean in >> context >> > with this jndi, >> > context.bind("com/starts/pl/AccountsBean"); >> > I have error: >> > "An exception occurred: javax.naming.NamingException" >> > >> > Is it possible to work with this jndi in OpenEjb? >>
