I still consider the README.md not to be properly reworded.
What is it? - the first paragraph (_This quickstart shows...)
It describes migration from original Spring's petclinic, but it says something completely different than Spring Developer Guide's migration section. As described in the guide, you just have to align Hibernate version, you don't need to add jboss-deployment-structure.xml at all. I think this is so because the example doesn't use persistence.xml, so Hibernate module is not used by EAP6 automatically.
What is it? - the third paragraph (PetClinic features...)
I believe the default configuration is JPA + HSQLDB, see param spring.profiles.active in web.xml, it is set to `jpa`
Furthermore, simple comment change in data-access.properties is enough to switch underlying database engine (HSQLDB vs MySQL), but you need to rewrite (not just comment change) the aforementioned spring.profile.active param to switch between jdbc, jpa, spring-data-jpa profiles.
Another issue I just noticed
The class CallMonitorAspect doesn't exist, it is called CallMonitoringAspect.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
I still consider the README.md not to be properly reworded.
What is it? - the first paragraph (_This quickstart shows...)
It describes migration from original Spring's petclinic, but it says something completely different than Spring Developer Guide's migration section. As described in the guide, you just have to align Hibernate version, you don't need to add jboss-deployment-structure.xml at all. I think this is so because the example doesn't use persistence.xml, so Hibernate module is not used by EAP6 automatically.
What is it? - the third paragraph (PetClinic features...)
I believe the default configuration is JPA + HSQLDB, see param spring.profiles.active in web.xml, it is set to `jpa`
Furthermore, simple comment change in data-access.properties is enough to switch underlying database engine (HSQLDB vs MySQL), but you need to rewrite (not just comment change) the aforementioned spring.profile.active param to switch between jdbc, jpa, spring-data-jpa profiles.
Another issue I just noticed
The class CallMonitorAspect doesn't exist, it is called CallMonitoringAspect.