[JBoss jBPM] - Re: dual jbpm context
by tbeernot
"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 session listener; that was added after I got knee deep in the servlet API and I keep forgetting it exists. Dumm me.
"kukeltje" wrote : Correct... but what I do not get is what you mean by 'with hibernate removed'. I have hibernate in both configs.
|
Well, in one of you previous posts you said this:
"kukeltje" 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 one configurations. As said; that didn't work. ThenI reread that part on the XML vs objects vs DB and finally saw the light; you either have a backing store (and can base on workflows stored in there), or you don't.
So thanks again!
Tom
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200813#4200813
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200813
17 years, 2 months
[JBoss jBPM] - Re: dual jbpm context
by kukeltje
"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 keep the processInstanceId and use that to cancel/remove the process. When the use clicks cancel it is (to me) obviously easier....
"tbeernot" wrote :
| And technically you do not have an "no-persistence" setup; you have two persisted configurations, but one DB happens to be in-memory. (I tried you setup with hybernate removed from the configuration, but that does not work).
|
Correct... but what I do not get is what you mean by 'with hibernate removed'. I have hibernate in both configs.
"tbeernot" wrote :
| I want all in-memory processes to be cleared when the session is destroyed (explicitely or due to time out).
|
See my first statement. You can also link it e.g. to seam conversation timeouts etc...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200798#4200798
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200798
17 years, 2 months
[JBoss jBPM] - Re: dual jbpm context
by tbeernot
"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 terminated? Or better; when the user simply cancels thus you never know it is terminated?
And technically you do not have an "no-persistence" setup; you have two persisted configurations, but one DB happens to be in-memory. (I tried you setup with hybernate removed from the configuration, but that does not work).
I want all in-memory processes to be cleared when the session is destroyed (explicitely or due to time out).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200790#4200790
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200790
17 years, 2 months