You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@empire-db.apache.org by "Francis De Brabandere (Commented) (JIRA)" <em...@incubator.apache.org> on 2012/03/11 10:56:00 UTC
[jira] [Commented] (EMPIREDB-102) ArrayOutOfBoundsException with
Oracle Driver and unspecified dbSchema parameter
[ https://issues.apache.org/jira/browse/EMPIREDB-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227024#comment-13227024 ]
Francis De Brabandere commented on EMPIREDB-102:
------------------------------------------------
Can we not show a better exception that hints to what is going wrong instead of this ugly ArrayIndexOutOfBoundsException???
> ArrayOutOfBoundsException with Oracle Driver and unspecified dbSchema parameter
> -------------------------------------------------------------------------------
>
> Key: EMPIREDB-102
> URL: https://issues.apache.org/jira/browse/EMPIREDB-102
> Project: Empire-DB
> Issue Type: Improvement
> Components: CodeGenerator
> Affects Versions: empire-db-2.0.7-incubating
> Environment: Oracle Driver
> Reporter: Daniel Weidele
> Assignee: Rainer Döbele
> Priority: Minor
>
> Steps:
> Use Oracle Driver v14 and do not specify "dbSchema" in XML-configuration.
> Actual Behaviour:
> ArrayOutOfBoundsException
> Expected:
> - No ArrayOutOfBoundsException
> - Create a check that prevents the execution in case of 'dbSchema' is missing (but necessary).
> Stack trace looks as follows:
> java.lang.ArrayIndexOutOfBoundsException: 8
> at org.apache.empire.db.codegen.CodeGenParser.populateTable(CodeGenParser.java:199)
> at org.apache.empire.db.codegen.CodeGenParser.populateDatabase(CodeGenParser.java:163)
> at org.apache.empire.db.codegen.CodeGenParser.loadDbModel(CodeGenParser.java:92)
> at org.apache.empire.db.maven.CodeGenMojo.execute(CodeGenMojo.java:141)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:592)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira