Suresh, running the example through Maven is not necessary, but it has a better possibility of not resulting in a failure.
The datasource is defined in WEB-INF/kitchensink-quickstart-ds.xml. If it is not deployed, or detected in the deployment made by Eclipse, you will see the error. The message you see about missing dependents is due to the datasource not being found in the JNDI tree when deploying the JPA persistence unit.
You could retry deploying through Maven, since it packages up the datasource and makes the deployment as a packaged WAR. If that fails, you could open up the $JBOSS_HOME/standalone/deployments directory to examine the deployment for the -ds.xml file.
Vineet Reynolds
Suresh, running the example through Maven is not necessary, but it has a better possibility of not resulting in a failure.
The datasource is defined in WEB-INF/kitchensink-quickstart-ds.xml. If it is not deployed, or detected in the deployment made by Eclipse, you will see the error. The message you see about missing dependents is due to the datasource not being found in the JNDI tree when deploying the JPA persistence unit.
You could retry deploying through Maven, since it packages up the datasource and makes the deployment as a packaged WAR. If that fails, you could open up the $JBOSS_HOME/standalone/deployments directory to examine the deployment for the -ds.xml file.
5:49 a.m., Friday April 26
Moderate this comment by email
Email address: vineet.reynolds@gmail.com | IP address: 209.132.188.34
Reply to this email with “Delete”, “Approve”, or “Spam”, or moderate from the Disqus moderation panel.