Matt,
'this issue' is to vague to give any serious response. Just like 'I can't do
anything using the old processes'. Besides that, we have no clue what your apps
do.
So sorry, but I think we cannot be of any help unless you post more but
relevant info.
View the original post :
http://www.j
you can remove process instances that have ended, that should cleanup a lot.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4055977#4055977
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4055977
__
I think you should look to the file where queries are defined :
org/jbpm/db/hibernate.queries.hbm.xml
And you can customize hibernate mapping file, see the persistence chapter :
http://docs.jboss.com/jbpm/v3/userguide/persistence.html
View the original post :
http://www.jboss.com/index.html?mod
Ok, it seems there are no takers. I don't understand the lack of interest -
maybe that's because I'm missing some really important point. Let me define
where I'm coming from:
I'm going to run on average N*10 workflows per day. That amounts to about
10*N*10 variable instances and goodly q
Hi there,
Thanks for clearing my doubt. The information prove to be handy.
Good Day.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980879#3980879
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980879
jBPM uses Hibernate as an object/relational persistence engine. With this
abstraction layer, the java objects can be persisted in any relational database
that is supported by hibernate. Have a look at http://www.hibernate.org/80.html
to see which databases are supported. For further reading on h
