Can you please provide a JUnit test demonstrating the error in JIRA?
Regards,
Koen
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=390#390
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=390
Sorry I should have said, it's in the
\build\classes.jbpm\org\jbpm\graph\def\ProcessDefinition.hbm.xml
Change the nodes list: -
list name=nodes cascade=all where=SUPERSTATE_ is null.
Mark
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3933055#3933055
Reply
Their is also a BUG here!!!
If there are more than 24 states e.g.
start
super1
state1
state2
super2
state3
state4
super3
state5
state6
state7
state8
state9
state10
state11
state12
state13
state14
state15
state16
state17
state19
state20
state21
state22
state23
super4
state24
Well I've got a fix for this, can this be added as an issue?
The issue is that the ProcessDefinition.hbm.xml has: -
list-index column=NODECOLLECTIONINDEX_ /
one-to-many class=org.jbpm.graph.def.Node /
This means that super states nodes and normal nodes that both have an
mjm_uk wrote : Well I've got a fix for this, can this be added as an issue?
|
| To resolve this issue I have added
|
| where=SUPERSTATE_ is null to the list criteria.
|
| This is probably not the best way to go (I don't really know hibernate, but
a filter looked like it might be
I'm having the same issue...
Process Definition =
?xml version=1.0 encoding=UTF-8?
process-definition name=test
start-state name=start
/start-state
end-state name=end1/end-state
super-state name=super1
