No more nasty @Persister annotations on your entities, they now look like plain
old ones.
When using JPA and as long as you use a TransactionManager (ie JTA support),
the configuration is very simple
http://java.sun.com/xml/ns/persistence";
xmlns:xsi="http://www.w3.org/2001/XMLSchem
And I've added a small page on how to set up JBoss TransactionManager in
standalone
http://community.jboss.org/wiki/HowtouseJBossJTAstandaloneTransactionManager
On 18 mars 2011, at 16:39, Emmanuel Bernard wrote:
> No more nasty @Persister annotations on your entities, they now look like
> plai
I will be changing Hibernate Core JIRA project to use the participant-based
notification scheme. Should I change over any other projects while I am in
there?
What is participant-based notification? Basically, any participant (reporter,
assignee and all commenters) is automatically notified on
Is anyone using or aware of uses of the JACC stuff in org.hibernate.secure?
I'd like to remove it.
---
Steve Ebersole
http://hibernate.org
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-
I wanted to give everyone a heads up about the changes to the stuff in
org.hibernate.testing (there is still a question about whether Eclipse is able
to handle the hibernate-testing as a separate module setup).
Internally, the main piece is a custom JUnit4 runner implementation,
org.hibernate.t
