Your jboss-web. Xml file is referencing the wrong JNDI name. Your ldcDataSource-ds.
Xml data source file specifies this JNDI name.
Your jboss-web. Xml file is referencing the wrong JNDI name. Your ldcDataSource-ds.
Xml data source file specifies this JNDI name: jdbc/ldcDataSource However, your jboss-web. Xml file references it as such: java:ldcDataSource Change your jboss-web. Xml file so it is as follows: java:jdbc/ldcDataSource That should correct the issue.
Also, @skaffman is correct that you do not need to use the comp/env if you don't want to, but by specifying your resource-ref within the WAR's web. Xml file, your webapp will not deploy unless the necessary resources are found. The data source file binds the provided resource-ref to a JNDI name.
Your web. Xml file specifies that your webapp requires a specific resource-ref name. What ties these together is the jboss-web.
Xml which ties a specific resource-ref to a JNDI name and makes it available under java:comp/env/{res-ref-name}. This is the proper way to do it. Good luck!
And @skaffman. Thank you so much guys. That did the trick.
– dionysus Jan 26 at 15:53.
Why are you configuring bernate to use java:comp/env/jdbc/ldcDataSource You're not using EJBs here, you shouldn't need all that comp/env rubbish. Try just java:jdbc/ldcDataSource instead, since that what your -ds. Xml file is configured to expose.
You are able to do it this way, but it is cleaner within JBoss to tie the resources together to a JNDI name so the webapp will not deploy unless the required resources are available. – Brian Riehman Jan 26 at 14:08.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.