[jboss-user] [JBoss jBPM] - Re: Problem with a decision node in a fork, join construct.

kukeltje do-not-reply at jboss.com
Wed Dec 17 16:40:38 EST 2008

Yes, the lock can be on the processdefinition. If it complaints and you have a reference to the xsd, remove that....  validating against the xsd does not work then. (also a jira issue might be created then for the xsd to be updated)

@Martin.. Yes, I'd like to but I get 403's when committing. Someone has to fix that and I don't know who (already informed Tom)

The generator type was just to see if postgress would work then and kind of confirm it has a releation to generated-id's (via sequences) or auto-increment one. It was never meant to be changed indefinately

On a sidenote, If I add the flush back in the code, my H2 oracle compatible db does not lead to any errors as without it I get a SOE

The strange thing is that UPGRADE and FORCE (the default if nothing is provided) are kind of similar for hibernate. FORCE also working for not versioned objects... strange. Maybe one of the JBoss Hibernate experts could have a look. 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197225#4197225

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197225

More information about the jboss-user mailing list