Dit gaat makkelijker of niet?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4201007#4201007
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4201007
___
jboss-user mailing list
kukeltje wrote : Dit gaat makkelijker of niet?
Ligt eraan, als je zonder persistence gaat roepen, ga ik nog dingen
verwijderen ;-)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4201050#4201050
Reply to the post :
anonymous wrote : Well, in one of you previous posts you said this:
|
| anonymous wrote :
| | One pointing to a hibernate config with persistance and one without?
| |
|
| Without persistence, for me that means no persistence and not
in-memory db, so I took hibernate out of the
kukeltje wrote : That is what you get when non native english speakers start
writing short statements. Persistence to me is 'surving restarts'
|
|
And to make matters worse: the short statements are interpreted by other non
native english speakers. Ain't communication great? :-)
But in
That is another option I use the 'mem' option with an in-memory database
and when starting the app, I deploy the process to there. I also remove process
instances from the in-memory database when they end... works great
View the original post :
kukeltje wrote : That is another option I use the 'mem' option with an
in-memory database and when starting the app, I deploy the process to there. I
also remove process instances from the in-memory database when they end...
works great
Doesn't this cause cleanup issues? When sessions are
tbeernot wrote :
| Doesn't this cause cleanup issues? When sessions are terminated? Or better;
when the user simply cancels thus you never know it is terminated?
|
No, use an HttpSessionListener, declare it in the web.xml and implement the
sessionDestroyed method. In the session you can
kukeltje wrote : No, use an HttpSessionListener, declare it in the web.xml
and implement the sessionDestroyed method. In the session you can keep the
processInstanceId and use that to cancel/remove the process. When the use
clicks cancel it is (to me) obviously easier
|
Ah, yes, the
kukeltje wrote : put 2 jbpm-context in one config file and put a name
attribute on each them
I dunno; what to do with lines like this:
JbpmConfiguration.getInstance().createSchema();
It should be done like:
JbpmConfiguration.getInstance().createJbpmContext(mem).createSchema();
But that is
tbeernot wrote :
| JbpmConfiguration.getInstance().createSchema();
|
Ah, oeps:
JbpmConfiguration.getInstance().createSchema(mem);
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4200558#4200558
Reply to the post :
Ah... I finally get it.
If I want long running workflows, I use the JbpmContext and go off and persist
it. Then I need to hold the id in session.
If I only want to do stuff in memory, I cannot use the JbmpContext at all,
notably not for findLatestProcessDefinition, since there is no store. I
put 2 jbpm-context in one config file and put a name attribute on each them
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4200045#4200045
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4200045
2. Or do I have to configure hibernate to use hsqldb in memory mode?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4199740#4199740
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4199740
1. Having two JbpmConfigurations runs into some dead ends.
When trying to parse a ProcessDefinition from String using the static
parseXmlString, underwater JbpmConfiguration.getInstance() is called.
JbpmConfiguration.getInstance(String) line: 278
JbpmConfiguration.getInstance() line: 257
tbeernot wrote : When trying to parse a ProcessDefinition from String using
the static parseXmlString, underwater JbpmConfiguration.getInstance() is
called.
|
The problem basically is with the static
ProcessDefinition.createNewProcessDefinition; it accesses a static inner class
Configs:
huh? can't you use to different named context in one config? One pointing to a
hibernate config with persistance and one without?
USe
http://docs.jboss.org/jbpm/v3/javadoc/org/jbpm/JbpmConfiguration.html#createJbpmContext(java.lang.String)
then
View the original post :
kukeltje wrote : huh? can't you use to different named context in one config?
One pointing to a hibernate config with persistance and one without?
|
| USe
http://docs.jboss.org/jbpm/v3/javadoc/org/jbpm/JbpmConfiguration.html#createJbpmContext(java.lang.String)
then
I'm using two configs
17 matches
Mail list logo
