incubator-empire-db-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francis De Brabandere <franci...@gmail.com>
Subject Re: [jira] Created: (EMPIREDB-102) ArrayOutOfBoundsException with Oracle Driver and unspecified dbSchema parameter
Date Wed, 16 Feb 2011 11:09:48 GMT
I looked a bit at the code but as I don't have access to an oracle
system it's not really clear what fails because of what... . Could
somebody look at this?

Cheers,
Francis

On Fri, Feb 11, 2011 at 9:44 AM, Daniel Weidele (JIRA)
<empire-db-dev@incubator.apache.org> wrote:
> 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: Bug
>          Components: CodeGenerator
>    Affects Versions: empire-db-2.0.7-incubating
>         Environment: Oracle Driver
>            Reporter: Daniel Weidele
>            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.
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>



-- 
http://www.somatik.be
Microsoft gives you windows, Linux gives you the whole house.

Mime
View raw message