-
1. Re: Jbpm6 - extend task
swiderski.maciej Oct 20, 2014 1:35 AM (in response to zmor)1 of 1 people found this helpfulin general for that you should you process and task variables. If you need more advanced storage for process variables so they can be easily queried you can used so called variable persistence strategies so you store certain variables in different storage - for example put them into the search index or separate data base. See this article for details about variable persistence strategies.
HTH
-
2. Re: Jbpm6 - extend task
zmor Oct 20, 2014 9:35 AM (in response to swiderski.maciej)Thanks for the reply.
I read your blog already and i read this article too.
I was trying to persist my entity variable but with no luck. Then i saw code of marhsal method of JPAPlaceholderResolverStrategy class and i realize that this method doesn't persist object in database.
After a little digging i found JPAReadAndWriteStrategy class, which is described in JBPM6 developer guide book. Marshal method of this class persists objects in database.
Anyway, is there any API method to search tasks by various fields from variable which is persisted as entity? Or should i write my own search engine?
-
3. Re: Jbpm6 - extend task
swiderski.maciej Oct 21, 2014 3:50 AM (in response to zmor)1 of 1 people found this helpfulyou're right that version 6.0.1 did not persist the entity as part of the marshaller strategy although it was fixed and now it does so. So you can upgrade to 6.1 or just make a copy of that fixed version into your application to make use of it.
There is no direct way to query variables outside of jbpm tables so once they are stored in other location you need to provide your own way of searching that.
HTH
-
4. Re: Jbpm6 - extend task
zmor Oct 22, 2014 3:11 AM (in response to swiderski.maciej)Thanks for the answers.
Now it's more clear for me.
Regards,
KM