It seems like the HARDeployer has been removed all together, and that the Hibernate MBean can be deployed as any other service. I just packaged all the Hibernate classes and .hbm.xml files in one SAR, and renamed the hibernate-service.xml to jboss-service-xml.
I guess this is an improvement, and makes it simpler to deploy Hibernate applications on JBoss, but such changes (from RC2 to FINAL) should be documented in laymen's terms, not in some (to me) cryptic discussion among JBoss employees. That is documented prior to announcing the release.
Otherwise keep up the good work.
There should be no need to modify the har as documented in the release readme:
JBAS-2000, The HARDeployer as a separate full deployer was an unnecessary replication of behavior in the SARDeployer. The SARDeployer and deployer framework in general has been updated to support multiple extensions with ordering of the deployment order via the ExtendedSuffix attribute(see JBAS-2232). As such, a har deployment is just a sar deployment with a different suffix. Impact: None. A har deployment can use the legacy META-INF/hibernate-service.xml descriptor name, or the standard sar META-INF/jboss-service.xml descriptor name
I have a har using the of META-INF/hibernate-service.xml convention that deploys fine under 4.0.3. If you have an example that does not, create a bug report in jira with the example, http://jira.jboss.com/jira/browse/JBAS
I?m unable to consistently reproduce the bug, I have 2 applications using the old deployment method, one works, and the other does not. I can therefore not provide a good bug description, but I have posted what I have and maybe you can look into it. The new method works fine for me anyways.