-
1. Re: JBoss 7 AS + JPA + missing [ jboss.naming.context.java.java:]
jaikiran Oct 10, 2011 10:30 AM (in response to dkumaran)How have you configured your datasource? What does it look like?
-
2. Re: JBoss 7 AS + JPA + missing [ jboss.naming.context.java.java:]
dkumaran Oct 10, 2011 10:48 AM (in response to jaikiran)i have configured the Datasource using the web-console... and it's in green enabled mode.
Is there anyway to check wheather the created datasource is available and how do i access it outside..
-
3. Re: JBoss 7 AS + JPA + missing [ jboss.naming.context.java.java:]
jaikiran Oct 10, 2011 10:52 AM (in response to dkumaran)What JNDI name did you configure it to? The standalone.xml would have the newly created datasource, so check that file. As for testing whether the datasource is functional, I think there is a test connection feature available in the admin console. I haven't checked recently, so can't say for sure.
-
4. Re: JBoss 7 AS + JPA + missing [ jboss.naming.context.java.java:]
dkumaran Oct 11, 2011 4:31 AM (in response to jaikiran)i can see the datasource name created in the standalone.xml as follows.
<datasource jndi-name="DKDS" pool-name="DKDS_Pool" enabled="true">
<connection-url>
jdbc:jtds:sqlserver://localhost:1433/test
</connection-url>
<driver>
sqljdbc4.jar
</driver>
<security>
<user-name>
qhg_engr_user
</user-name>
<password>
*08oate
</password>
</security>
</datasource>
-
5. Re: JBoss 7 AS + JPA + missing [ jboss.naming.context.java.java:]
jaikiran Oct 11, 2011 4:43 AM (in response to dkumaran)I forgot to ask it earlier. What does your persistence.xml look like. It should use java:/DKDS (the front slash is necessary) as the jndi name of the datasource
-
6. Re: JBoss 7 AS + JPA + missing [ jboss.naming.context.java.java:]
dkumaran Oct 11, 2011 6:09 AM (in response to jaikiran)yes that was the problem,,, awesome and thanks for the information... i was trying to access the JNDI as java:DKDS just modified to java:/DKDS and it started working....
once again thanks for the information i was strucked with this issue for the past two days..... and finally got resolved....