I'm learning jBPM and I am intrigued by the <hql> element because it allows me direct access to the hibernate session and jbpm data model. But wouldn't this lock me into the current release of jBPM? i.e. in a later release the developers decide to change a column name or even eliminate a whole table then I can't upgrade without changing my code.
Maybe most people consider themselves locked into a particular release anyway but I wonder if anyone else has any thoughts.
I'm on 4.3 currently.
The HSQL-activity can of course be used to access the jbpm data model directly but the intented use rather is accessing your own entities which you might define in addition to the jbpm data model. In this use case your are not tied to one release.