Best Practice to get SessionFactory

[toriton]

Hi all , i have a question on how to get SessionFactory directly from JBPM.
In the documentation
http://docs.jboss.org/jbpm/v3/userguide/persistence.html#thehibernatesessionfactory
(par 7.7) In the documentation there is a suggestion to use the JBPM SessionFactory ,for own persistence classes.
But my question is: which the best practice is to retrieve the SessionFactory?

I use this code:

JbpmConfiguration.getInstance().getCurrentJbpmContext().getSessionFactory();

in a DAO class, but i seen around that the method
getCurrentJbpmContext() will be deprecated, but in my version 3.3.1 is not. So there is another way to interact with shared sessionfactory? or according to my version (3.3.1 GA), this is the only way?
The DAO class are deployed as Jar with entity classes under the path jbpm-service.sar , and work perfectly at this moment :).


T.

[boercher]

Looking at the current jBPM3 code

JbpmContext.getCurrentJbpmContext().getSessionFactory()

seems to be the standard way to access the SessionFactory. In my ActionHandlers I'm rather using the current Session directly via

executionContext.getJbpmContext().getSession()

Volker

[toriton]

thank for yout reply :)

I do the same in an ActionHandler.

[toriton]

Hi all again :),
i found another way to get SessionFactory, and i want know if this is a most clear solution.

I use this code in a DAO class.

JtaDbPersistenceServiceFactory jtaDBFactory = (JtaDbPersistenceServiceFactory)JbpmConfiguration.getInstance().getServiceFactory("persistence");

It is correct?.
It's work fine :) and save correctly.
Thanks for any reply.

[toriton]

Sorry bad cut :)

this is how the SessionFactory is returned :

JtaDbPersistenceServiceFactory jtaDBFactory = (JtaDbPersistenceServiceFactory)JbpmConfiguration.getInstance().getServiceFactory("persistence");
return (SessionFactory) jtaDBFactory.getSessionFactory();

[kukeltje]

this way you are dependent on what is explicitly configured (not using interfaces but and explicit implementation) imo that is not the best way (no examples show this, but do show what Volker advised)

[toriton]

Is true, Kuke thanks for your reply. I missed that thing.. usually i use always Interfaces.. my bad to think about this as a solution :).