jaikiran,
Our deployment scenario excludes Option #1, but Option #2 worked perfectlty!!!
Thank you!!!
I searched for hours for that information. Where is that located in the
documentation?
Again, thank you!!!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p
Looks like a deployment ordering issue. I can think of two options:
1) Create a folder named "deploy.last" in server/default/deploy folder and
place your EAR file in that deploy.last folder. That way, your EAR will be
deployed after everything else is deployed
OR
2) Create a jboss-app.xml (i
I changed the following line with no change in behavior:
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199312#4199312
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199312
___
Here is my persistence.xml file:
| http://java.sun.com/xml/ns/persistence";
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
| xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
| http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd";
version="1.0">
|
I tried placing the MBean definition in the default/conf/jboss-service.xml file
instead of a standalone cache-config.xml file in /default/deploy but got a
different error relating to TransactionManager being NULL at runtime.
View the original post :
http://www.jboss.com/index.html?module=bb&op=
Caused by: javax.management.InstanceNotFoundException:
jboss.cache:service=EJB3EntityCache is not registered.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199309#4199309
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=
