[JBoss Seam] - Re: Multiple DataModels in an SFSB
by lightbulb432
I'm getting a problem where the DataModelSelection that isn't being selected (because there's 2 in the SFSB) is still being outjected, albeit with all properties empty...I do a null check on whether a particular component is not empty in conversation scope for application functionality, so this is a problem. (By the way, is that not a good way of doing things?)
Where in my debugger should I put a breakpoint to see when a component gets outjected into any scope (in particular, the conversation scope)? I think it's a simple case of having a ${mycomponent.myproperty} somewhere in one of the pages, so the component is getting outjected...
A related question is if I put a ${mycomponent.myproperty} within Facelets template text in a page to output the value if that property exists (or remain empty otherwise), I get an empty mycomponent outjected (is that expected behavior)? I thought things only get outjected when you specify explicitly that you outject them (e.g. in an @Out of a session bean). But a simple property access...?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013706#4013706
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013706
19Â years, 2Â months
[JBoss jBPM] - Re: Concurrent task acquisition (how?)
by Johan.Parent
In the meanwhile I've implemented this approach. And it solves the problem.
But I can't catch the exception very early on. So my process produces ugly stack traces upon unsuccesful commits.
I'm not sure whether replace the DbPersistenceService(Factory) (through the service definition in the jbpm.cfg.xml) would be adviseable. I risk bring a bunch of other things. Is there a better way?
Best regards,
Johan
| [oe2] AbstractFlushingEventListener : Could not synchronize database state with session
| org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.graph.exe.Token#7110]
| at org.hibernate.persister.entity.AbstractEntityPersister.check(AbstractEntityPersister.java:1635)
| at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2208)
| at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2118)
| at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2374)
| at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:84)
| at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:243)
| at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:227)
| at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:141)
| at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:296)
| at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
| at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:980)
| at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:353)
| at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106)
| at org.jbpm.persistence.db.DbPersistenceService.close(DbPersistenceService.java:162)
| at org.jbpm.svc.Services.close(Services.java:211)
| at org.jbpm.JbpmContext.close(JbpmContext.java:139)
| at JBpmTest.JBpmOeTest.closeContext(JBpmOeTest.java:331)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013703#4013703
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013703
19Â years, 2Â months