This week's book giveaway is in the Agile and other Processes forum. We're giving away four copies of The Mikado Method and have Ola Ellnestam and Daniel Brolund on-line! See this thread for details.
I have a doubt here. Will there be any issues if the same DataSource with the same JNDI Name being used by two different applications? I have NOT yet tested the same.
Will the Application Server try to rebind the DataSource during the deployment of the new EAR file which happens to use the same JNDI name?
I talk about the J2EE Enterprise applications used. We do use WebSphere Application Server. Though i think it may not be an issue, just wanted to get it confirmed.
Will the Application Server try to rebind the DataSource during the deployment of the new EAR file which happens to use the same JNDI name?
It depends on whether you bind to a local or global JNDI name. as long as you refer to it via the java:comp/env InitialContext, the context that you refer to each time will be local to each EAR and will not overlap.