[JBoss Seam] - Re: jBPM integration question
by fady.matar
I guess I need to override the startup method. This is what I have done so far
| import static org.jboss.seam.InterceptionType.NEVER;
| import static org.jboss.seam.annotations.Install.BUILT_IN;
|
| import org.jboss.seam.ScopeType;
| import org.jboss.seam.annotations.Create;
| import org.jboss.seam.annotations.Install;
| import org.jboss.seam.annotations.Intercept;
| import org.jboss.seam.annotations.Logger;
| import org.jboss.seam.annotations.Name;
| import org.jboss.seam.annotations.Scope;
| import org.jboss.seam.annotations.Startup;
| import org.jboss.seam.jbpm.SeamVariableResolver;
| import org.jbpm.jpdl.el.impl.JbpmExpressionEvaluator;
| import org.jboss.seam.core.Jbpm;
| import org.jboss.seam.log.Log;
|
| @Scope(ScopeType.APPLICATION)
| @Startup(depends = { "org.jboss.seam.core.microcontainer",
| "org.jboss.seam.core.ejb" })
| @Name("org.jboss.seam.core.jbpm.init")
| @Install(value = false, precedence = BUILT_IN)
| public class JbpmInitializer extends Jbpm {
|
| @Logger
| Log log;
|
| @Create
| public void startup() throws Exception {
| log.trace("Starting jBPM");
| JbpmExpressionEvaluator.setVariableResolver(new SeamVariableResolver());
| this.invokeJbpmContext();
| }
|
| public void invokeJbpmContext() {
| //Invokation goes here
| }
| }
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035259#4035259
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035259
19 years
[JBoss jBPM] - strange problem with many-to-one mapping in jbpm 3.2
by camunda
Hi!
I have a very strange problem with the current jbpm 3.2. When I deploy a process a lot of columns which schould be filled are set to NULL in the database. Inspecting further I found, that ALL many-to-one mappings are set to NULL in the database, even if the association (the "Java-Pointer") was set correctly!
As a example take the start-state of a process-definition.
I started debugging in Hibernate (3.2.3 by the way) and found the following:
Hibernate males a check to set all transient attributes to null (makes sense):
| new ForeignKeys.Nullifier( entity, false, useIdentityColumn, source ).nullifyTransientReferences( values, types ); (AbstractSaveEventListener, 288)
|
If it checks the StartState, it finds the primary key ID=0, which leads hibernate to the assumption, this SuperSate is a transient object. So it is set to NULL!
This is a very strange behavior, because I think Hibernate should generate that key on its own!
I have no idea, why that happens in this new version of jbpm. Because I looked at the hibernate-mappings, and they haven't changed too much since 3.1.
By the way, I use mySQL 5...
ANY ideas to that issue? It took me already a lot of time to come to the point that I have no idea :-(
Thanks for every hint!!
Regards
Bernd
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035257#4035257
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035257
19 years