[JBoss jBPM] - Re: API questions: how to...
by kukeltje
2a: By using the component that is used in the console as wel, or develop your own component
anonymous wrote : But.. there is a more simple way ? like the getBytes("processoimage.jsp" ... directly from standard jpdl api? No
anonymous wrote : Will be implements in a future release? It is not on the list, but that does not mean it will not happen.
anonymous wrote : If it is possible to define this additional properties... how can I get it from jpdl api?
You can by turning of schemavalidation (removing the declaration) or adding it to elements that support anyType (see the xsd for that)
You can then load the processdefinition.xml file the same way you load the image and make a dom out of it. After that you can retrieve the elements
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175414#4175414
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175414
17 years, 7 months
[JBoss jBPM] - Error while adding variables to execution context
by mlsreekanth
Hello All,
I have been successfully using jbpm-jpdl-3.2.GA till now. Few days back, database server was down suddenly because of data storage issue. After that, i am seeing very peculiar errors from JBPM as follows,
Caused by: org.hibernate.TransientObjectException: org.jbpm.context.exe.TokenVariableMap
at org.hibernate.engine.ForeignKeys.getEntityIdentifierIfNotUnsaved(ForeignKeys.java:216)
at org.hibernate.type.EntityType.getIdentifier(EntityType.java:108)
at org.hibernate.type.ManyToOneType.isDirty(ManyToOneType.java:221)
at org.hibernate.type.TypeFactory.findDirty(TypeFactory.java:476)
at org.hibernate.persister.entity.AbstractEntityPersister.findDirty(AbstractEntityPersister.java:2900)
at org.hibernate.event.def.DefaultFlushEntityEventListener.dirtyCheck(DefaultFlushEntityEventListener.java:474)
at org.hibernate.event.def.DefaultFlushEntityEventListener.isUpdateNecessary(DefaultFlushEntityEventListener.java:197)
at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:120)
at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:195)
at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76)
at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26)
at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:993)
at org.jbpm.persistence.db.DbPersistenceService.flushSession(DbPersistenceService.java:272)
at org.jbpm.persistence.db.DbPersistenceService.close(DbPersistenceService.java:232)
>From the above stack-trace i understand that JBPM runtime information such as token, context instance etc,,, are in-correct.
How can i correct the database? Could you please shed some light?
I am literally dying here as production server is down because of this issue.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175393#4175393
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175393
17 years, 7 months