mputz, I tried it just now - but unsuccessfully. I use Firebird as JBPM DB, and
as far as I can see - the JobExecutor holds opened transaction from its start
to infinite...
The only one solution I can find is
https://jira.jboss.org/jira/browse/JBSEAM-3837
- because
anonymous wrote : can't the job executor work with seam transactions?
Just recently, I made a similar test and added the JobExecutorServlet to the
dvdstore demo and experienced no issues when a timer fired. This was with Seam
2.0.2, and no other changes to the jBPM configs were necessary.
sorry, it accepts context param's as far as i know. But why do you want *no*
transaction around yor jobs? weird, never heard anybody want that.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4196512#4196512
Reply to the post :
kukeltje wrote : sorry, it accepts context param's as far as i know. But why
do you want *no* transaction around yor jobs? weird, never heard anybody want
that.
For Seam/jBPM integration and using of Seam managed JBpmContext, it's required
to disable transaction management in JBPM and use
Yes, but that is the other way around as you described it initially this
makes sense, although can't the job executor work with seam transactions?
There was something in the Jira, but I think it was fixed
View the original post :
mputz wrote :
| Just recently, I made a similar test and added the JobExecutorServlet to
the dvdstore demo and experienced no issues when a timer fired. This was with
Seam 2.0.2, and no other changes to the jBPM configs were necessary.
Thanks!
View the original post :
The jobexecutor is configured via the jbpm config file as is in the docs
The title of your post does not match the question
jbpm.configuration.resource parameter is used (as you could see in the source)
as init parameters for either the filter or servlets and configured in the
web.xml.
kukeltje wrote :
| The title of your post does not match the question
|
Sorry for my poor English, my native language is Java :)
kukeltje wrote : jbpm.configuration.resource parameter is used (as you could
see in the source) as init parameters for either the filter or servlets and
