Maciej,
As food for thought back in the Hibernate days of the codeline we had a
similar problem with MEX entity and there was simply an attribute of the
DAO unmapped and as such nothing was flushed to DB - so maybe some
mistype in an annotation or something.
Matt
Maciej Szefler wrote:
For all those of you who are at peace with JPA, take a look at
ActivityRecoverTest.testInvokeSuccess on trunk.. If you have any idea why
the following occurs, please let me know:
Caused by: org.apache.ode.bpel.iapi.BpelEngineException: InternalError: No
instance for partner mex
[EMAIL PROTECTED]
at
org.apache.ode.bpel.engine.BpelProcess.executeContinueInstancePartnerRoleResponseReceived
(BpelProcess.java:387)
at
org.apache.ode.bpel.engine.PartnerLinkPartnerRoleImpl$UnreliableInvoker$1.run
(PartnerLinkPartnerRoleImpl.java:374)
at org.apache.ode.bpel.engine.Contexts$1.call(Contexts.java:80)
at org.apache.ode.bpel.engine.Contexts$1.call(Contexts.java:1)
at org.apache.ode.bpel.engine.Contexts.execTransaction(Contexts.java
:100)http://www.nytimes.com/2006/04/16/fashion/weddings/16vows.html?ex=1145764800&en=8d8388dc36b1fe6d&ei=5070&emc=eta1
By all accounts the MEX DAO object was populated with a ProcessInstance, yet
when it is reloaded, this field (along with some others) is mysteriously
blank. Its driving me bananas.
-mbs
