-
1. Re: javax.naming.NameNotFoundException: ConnectionFactory not bound
mmusaji Sep 20, 2010 10:55 AM (in response to gbhatia8)Without seeing the whole stacktrace but I guess something is wrong with your xxx-ds.xml file.
-
2. Re: javax.naming.NameNotFoundException: ConnectionFactory not bound(Resolved)
gbhatia8 Sep 22, 2010 7:49 AM (in response to mmusaji)There is no problem with -ds.xml file, the solution is Hot deployment in which I manually copied the file to deploy folder after starting the server. Can anybody suggest me how to automatically deploy the file(-service.xml(application specific)) during run time ?
-
3. Re: javax.naming.NameNotFoundException: ConnectionFactory not bound(Resolved)
peterj Sep 22, 2010 10:35 AM (in response to gbhatia8)I am going to make a guess that some mbean contained in your *-service.xml file depends on the datasource defined in your *-ds.xml. If that is the case, add a depends clause to your mbean that depends on the connection manager mbean created from the *-ds.xml file. Then you can include the *-service.xml file in the deploy directory at startup and the deployment will happen in the proper order.
-
4. Re: javax.naming.NameNotFoundException: ConnectionFactory not bound(Resolved)
gbhatia8 Sep 23, 2010 2:16 AM (in response to peterj)Thanks Peter, I have added connection factory dependency in my -service.xml file which is now maintaining the deployment order as per the requirement.