It appears that this problem is fixed in CR1. In addition, instead of declaring a xxx.har/META-INF/hibernate-service.xml file, you need to declare a xxx.har/META-INF/*-hibernate.xml file (see http://wiki.jboss.org/wiki/JBossHibernate3).
But there is a problem. For some reason, HAR files are being deployed before *-ds.xml files. Which makes it rather inconvenient because, of course, the data source used by the HAR does not exist yet. Even adding another depends clause to the *-hibernate.xml does not help: <hibernate-configuration xmlns="urn:jboss:hibernate-deployer:1.0"> | <session-factory ...> | ... | <depends>jboss.jca:name=xxx,service=ManagedConnectionPool</depends> | </session-factory> | </hibernate-configuration> Of course, if I wait until the *-ds.xml file is deployed, and then deploy the har file, JBossAS is happy, and everything works. So my question is - did I screw up the depends clause, or is this a bug? And the second question is why aren't HAR files automatically deployed after *-ds.xml files? Should I open a new JIRA or reopen JBAS-5232? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162158#4162158 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162158 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
