Spring ROO database reverse engineering with renamed context file
My requirement is quite simple. I recently created a jsf-primefaces-spring-roo-eclipselink multi module archetype and distributed it across my team here. With Spring ROO enabled, it makes our life easier to do all database reverse engineering and all is happy and well. When I created the archetype, I used an applicationContext.xml file in the model tier to do ROO DB reverse engineering. I then tried to change the name of the context file to applicationContext-model.xml because I used another context in the web tier. Now after renaming this context file, when I do a 'database reverse engineer --schema ', I get 'unable-to-obtain-connection' when I tab for autocomplete in the roo shell. Also when I enter my schema name manually after --schema, I get this error: File 'C:\TestWorkspace\TT\TT-model\src\main\resources\META-INF\spring\applicationContext.xml' does not exist Obviously ROO doesn't seem so happy with the context file rename. May I know how I could tell ROO to take the new context file name to do the database reverse engineering? Thanks for your help. Regards Basith
Since Roo wants a context file in the path 'src\main\resources\META-INF\spring\applicationContext.xml', I usually change the name of the other context files if I need to avoid collisions. For instance, try to rename the application context file that you have in the web tier.
How can we rename GWT nocache.js?
Why is a simple Weld SE 1.1, JUnit, Maven unittest no longer working
Deploying snapshots always fails but deploying releases works fine
Which settings are needed to make use of EL 3 in a JavaEE environment?
How to read values from .properties using maven plugin
Unable to install Ubik load pack using Maven
IntelliJ Maven Module Cannot resolve dependencies
Adding JPA support to an existing Maven project in IntelliJ
Specify which jar wins when conflicts in Maven Shade
JGitFlow maven plugin release-start from custom branch
Problems uploading jar artifact to hosted maven repository in nexus OSS 3.0.0-03
Auto deploy a Liferay portlet
log4j2 writing in file when testing, not when deploying
Exclude maven dependency by adding it as test scope?
Call source from exec-maven-plugin
Maven command : add classpath directory for Java runtime [closed]