generic fix for Oracle.
I'm actually surprised that it is picking these up - I would have expected it
to use the more optimized OracleMetaDataDialect which filters these BIN$ tables
out automatically and does not fail on index info.
You can try that by setting a property to:
hibernatetool.meta
That worked for me. Thank you very much for the prompt help. BTW, the full file
name is seam-gen.reveng.xml.
Also, is this a generic fix for using seam-gen with Oracle DB? OR it's just a
fix for my specific situation?
View the original post :
http://www.jboss.com/index.html?module=bb&op=view
hmm...
add the following line to the reveng.xml file in your resources directory
(assuming you use the latest release)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032808#4032808
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posti
I didn't get the complete log when redirecting the output to a log file.
Anyway, here is the last past of the output missing from my last post. As you
can see, the build failed without creating the source files.
| [hibernate] An exception occurred while running exporter #2:hbm2java
(Generate
yes Oracle drivers have problems with index; so we just report it as an warning.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032793#4032793
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032793
Ok, it looks like lower/upper case does matter for seam-gen. I used "WAS" as
the schema name, which matches exactly what I see in Oracle Enterprise Manager,
however, I got the following exceptions. Any idea?
| Buildfile: C:\jboss-seam-1.2.1.GA\seam-gen\build.xml
|
| validate-workspace:
hmm...the new tools should actually not care if your schema is lower or upper
case ;(
In any case that is probably the problem.
Use WAS as your schema name. I can also be empty but then it will process the
whole database and not just your schema (read: slower!)
View the original post :
http:/
