[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2515?page=c... ] Christian Bauer commented on HHH-2515: -------------------------------------- And add a note in the JBoss AS documentation saying "Note that the previously supported JBoss-specific HAR deployment has been superseded by the standardized EJB 3.0/Java Persistence deployment model. If you require automatic detection of Hibernate mapping metadata, be it in annotations or in XML mapping files, deploy Hibernate as a standard Java Persistence provider with Hibernate EntityManager." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2515?page=c... ] Steve Ebersole commented on HHH-2515: ------------------------------------- Hold on! Why are we removing documentation about HAR deployments? They work fine and trust me, there will be people not wanting to use JPA; so what should they do for auto-doscovery inside JBossAS? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2515?page=c... ] Christian Bauer commented on HHH-2515: -------------------------------------- How it is currently presented indicates to users that this is the _primary_ and (if the users are gullible) _only_ way to use Hibernate on JBoss AS. We just had a support case about it. The small advantage of auto-discovery does not justify this, especially not since we have a standardized deployment model and implementation that is supposed to work on every Appserver. Similar, the explanation for users who don't want to use JPA for this is "use persistence.xml with the SessionFactory/Session API". This is much easier to handle than a completely separate deployment strategy that only works on JBoss AS. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2515?page=c... ] Steve Ebersole commented on HHH-2515: ------------------------------------- Well, then that is hardly "remove all documentation"... Move, unify, yes... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2515?page=c... ] Christian Bauer commented on HHH-2515: -------------------------------------- So, Anthony and Joshua, please move the HAR section to a wiki page and mark it deprecated with a warning and a link to these methods: - pure JMX deployment of HibernateService, binding of SF to JNDI, lookup of SF, working with getCurrentSession() in plain JTA and EJBs/CMT - JPA deployment with META-INF/persistence.xml, binding the SF to JNDI, etc. Main difference: the first option requires JTA, the second doesn't and even gives you automatic discovery of mappings. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira