[EJB 3.0] - Re: Same datasource in multiple ear applications
by connerjohn
"bill.burke(a)jboss.com" wrote : This is what has to be unique:
|
|
| | <property name="jboss.entity.manager.factory.jndi.name" value="java:/itsEntityManagerFactory"/>
| |
|
| The unit name does not have to be unique between EARs.
|
| Why is this happening? the jboss.entity.manager.factory.jndi.name binds to global JNDI.
|
|
Ok - so after thinking about this for a while and walking the Seam examples and my applications, I believe I see what you are talking about. I need to set the jndi name for each persistent unit (the property you highlighted) to be unique across the ear applications.
To reiterate for myself, the reason is that the jndi name needs to be unique across the application server instance. I am getting the exception because both applications are trying to bind to the same jndi name. And that is why one "failed" to deploy; yet the application still worked (it found the other one that was previously deployed).
I will try that out tomorrow. I'm sure it's a cut/paste issue. I followed the Seam examples and then copied my skeleton to new applications without realizing this property also needs to be changed. And since I don't have enough experience with an application server, I'm not sure I every would have figured this out.
Thanks for looking at this,
-- jc
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968271#3968271
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968271
20 years
[JBoss jBPM] - Timer persisted but not fired
by ngeadah
Hi All!
I'm facing a frustrating timer problem. My process enters the "waitForAR" state correctly and a timer entry is correctly persisted in JBPM_TIMER, with a correct due date. My problem is the timer is never "fired" and the transition thus never followed...
The empty action (with a space between the open and close tag) is a suggestion I already received but it did not work.
I'm not sure what I could be missing. Perhaps a scheduler is not there monitoring the process. Is there an easy way to tell?
| <?xml version="1.0" encoding="UTF-8"?>
|
| <process-definition name="myprocess">
| <start-state name="start">
| <transition name="" to="isARAvailable"></transition>
| </start-state>
| <end-state name="end"></end-state>
|
| <state name="waitForAR">
| <timer name="waitingForAR" duedate="30 seconds" transition="waitingForARInLoop">
| <action> </action>
| </timer>
| <transition name="waitingForARInLoop" to="isARAvailable"/>
| </state>
|
| <decision name="isARAvailable" expression="#{ARChecker.isARAvailable}">
| <transition name="false" to="waitForAR"></transition>
| <transition name="true" to="writeToAR"></transition>
| </decision>
|
| <task-node name="writeToAR">
| <transition name="writeToAR" to="end">
| <action expression="#{ARReturnService.writeToAR}"/>
| </transition>
| </task-node>
| </process-definition>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968268#3968268
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968268
20 years