This content has been marked as final.
Show 4 replies
-
1. Re: JNDI datasource name bound but not accessible
juhalindfors Jul 23, 2003 10:22 AM (in response to eric_lemaitre)You cannot bind a datasource to the global namespace.
-- Juha -
2. Re: JNDI datasource name bound but not accessible
eric_lemaitre Jul 27, 2003 3:31 PM (in response to eric_lemaitre)Hi Juha !
I don't want to extend too much, but WHY isn't it possible to bind a datasource to global namespace ? For example, WebLogic an WebSphere do, while JBoss and BES don't. what are the reasons, EJB specs or editor's personnal choice ?
Thanks for having answered anyway. -
3. Re: JNDI datasource name bound but not accessible
juhalindfors Jul 27, 2003 4:32 PM (in response to eric_lemaitre)From maintainability and scalability point of view it makes more sense to have a server side component (such as a stateless session bean) to interact with your datasource rather than having a remote client using the datasource directly.
-- Juha -
4. Re: JNDI datasource name bound but not accessible
eric_lemaitre Jul 28, 2003 3:53 AM (in response to eric_lemaitre)Hi Juha !
Thanks for satisfactory comprehensive answer.
Best regards.