[
https://issues.jboss.org/browse/JBRULES-3305?page=com.atlassian.jira.plug...
]
Geoffrey De Smet commented on JBRULES-3305:
-------------------------------------------
Moved from Guvnor's jira: Guvnor itself doesn't have any hibernate specific
annotations. It does depend on hibernate-validator (but that's unrelated to hibernate
persistence and/or JPA) and even then it only uses the bean validation JSR annotations.
Drools does depend on hibernate-core, annotations and entitymanager, but it doesn't
use any hibernate specific annotations.
JBPM does use hibernate specific annotations:
{code}
Targets
String 'import org.hibernate'
Found usages (5 usages)
Production (5 usages)
jbpm-bam (4 usages)
org.jbpm.process.audit (4 usages)
HibernateUtil.java (2 usages)
(19: 1) import org.hibernate.SessionFactory;
(20: 1) import org.hibernate.cfg.Configuration;
ProcessInstanceDbLog.java (1 usage)
(21: 1) import org.hibernate.Session;
WorkingMemoryDbLogger.java (1 usage)
(28: 1) import org.hibernate.Session;
jbpm-persistence-jpa (1 usage)
org.jbpm.persistence.processinstance (1 usage)
ProcessInstanceInfo.java (1 usage)
(35: 1) import org.hibernate.annotations.CollectionOfElements;
{code}
What does the customer want?
Use any JPA Provider
--------------------
Key: JBRULES-3305
URL:
https://issues.jboss.org/browse/JBRULES-3305
Project: Drools
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 5.3.0.Final
Reporter: Jim Tyrrell
A potential customer has currently been using the BRMS/Govnor and would like the ability
to use any JPA provider. They noticed some Hibernate specific annotations and wonder why
that would be required/used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira