I'm using Roo 1.1.3.RELEASE [rev 4404ffb] on Ubuntu with Java 1.6.0_21_x64 connecting to an Oracle DB.
Trying to run database reverse engineer --schema ... --testAutomatically yields the following output:
roo> database reverse engineer --schema <schema> --testAutomatically
Created SRC_MAIN_RESOURCES/dbre.xml
Undo manage SRC_MAIN_RESOURCES/META-INF/persistence.xml
Undo manage ROOT/pom.xml
Undo create SRC_MAIN_RESOURCES/dbre.xml
Member holding type details required
roo> Created SRC_MAIN_JAVA/ar/GomezFact_Roo_Entity.aj
Created SRC_MAIN_JAVA/ar/GomezFactPK_Roo_Identifier.aj
Deleted SRC_MAIN_JAVA/ar/GomezFact_Roo_Entity.aj
Deleted SRC_MAIN_JAVA/ar/GomezFactPK_Roo_Identifier.aj
Not sure what the problem here is. Running the introspect yields what looks to be pretty standard, though I'm a total newbie when it comes to Roo. Help please?
roo> database introspect --schema <schema>
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!--WARNING: DO NOT EDIT THIS FILE. THIS FILE IS MANAGED BY SPRING ROO.--><!DOCTYPE database SYSTEM "http://db.apache.org/torque/dtd/database_3_3.dtd">
Restarting STS and re-running the same command but without "--testAutomatically" yields the below error:
roo> database reverse engineer --schema NEW_ODS
Created SRC_MAIN_RESOURCES/dbre.xml
Created SRC_MAIN_JAVA/ar/GomezFactPK.java
Created SRC_MAIN_JAVA/ar/GomezFact.java
Created SRC_MAIN_JAVA/ar/GomezIspDim.java
Created SRC_MAIN_JAVA/ar/GomezVariableDim.java
Undo create SRC_MAIN_JAVA/ar/GomezVariableDim.java
Undo create SRC_MAIN_JAVA/ar/GomezIspDim.java
Undo create SRC_MAIN_JAVA/ar/GomezFact.java
Undo create SRC_MAIN_JAVA/ar/GomezFactPK.java
Undo manage SRC_MAIN_RESOURCES/META-INF/persistence.xml
Undo manage ROOT/pom.xml
Undo create SRC_MAIN_RESOURCES/dbre.xml
Type for table 'GOMEZ_VARIABLE_DIM' could not be found but was referenced by table 'GOMEZ_FACT'
roo> Created SRC_MAIN_JAVA/ar/GomezFact_Roo_Entity.aj
Created SRC_MAIN_JAVA/ar/GomezFactPK_Roo_Identifier.aj
Deleted SRC_MAIN_JAVA/ar/GomezFact_Roo_Entity.aj
Deleted SRC_MAIN_JAVA/ar/GomezFactPK_Roo_Identifier.aj
Last edited by bzimmerman; Apr 24th, 2011 at 12:29 PM.
Reason: Different roo command
I can't reproduce the error however I don't have your schema DDL in a standalone Roo shell, I just allowed Roo to create the entities directly from the dbre.xml file using 1.1.3.RELEASE and 1.1.4.BUILD-SNAPSHOT.
I had to create the tests using test intregration --entity com.foo.empty.GomezFact etc. Still no errors.
If you want to attach your Oracle schema DDL can use the same steps in STS to attempt to re-create the issue.
Please log a Jira ticket for this an attach the schema there.
Thanks
Alan Stewart
Spring Roo Committer
twitter @alankstewart
I followed the commands you executed in script.log attached to the JIRA case and was able to get things started. I'm confused, though, about some of the commands and what purpose they serve. Could you please enlighten this newbie?
This last one I gather does something with the JDBC driver JAR for Oracle, though I had been able to execute an introspect prior to running this command.