geronimo-xbean-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <j...@apache.org>
Subject [jira] Closed: (XBEAN-53) "java.lang.ArrayIndexOutOfBoundsException: 0" thrown from XBeanMojo
Date Mon, 18 Sep 2006 20:57:23 GMT
     [ http://issues.apache.org/jira/browse/XBEAN-53?page=all ]

Hiram Chirino closed XBEAN-53.
------------------------------

    Resolution: Fixed

Fixed in trunk revision 447551

> "java.lang.ArrayIndexOutOfBoundsException: 0" thrown from XBeanMojo
> -------------------------------------------------------------------
>
>                 Key: XBEAN-53
>                 URL: http://issues.apache.org/jira/browse/XBEAN-53
>             Project: XBean
>          Issue Type: Bug
>          Components: spring
>    Affects Versions: 2.6
>            Reporter: Hiram Chirino
>         Assigned To: Hiram Chirino
>             Fix For: 2.7
>
>
> I noticed this happened when I was trying to apply a patch to ActiveMQ.  The patch left
a .java file empty.  And this is why XBean is barfing.  We should protect against such cases
and instead issue a warnning message.
> Full Error:
> java.lang.ArrayIndexOutOfBoundsException: 0
>         at org.apache.xbean.spring.generator.QdoxMappingLoader.loadElements(QdoxMappingLoader.java:147)
>         at org.apache.xbean.spring.generator.QdoxMappingLoader.loadNamespaces(QdoxMappingLoader.java:107)
>         at org.apache.xbean.spring.generator.QdoxMappingLoader.loadNamespaces(QdoxMappingLoader.java:101)
>         at org.apache.xbean.maven.XBeanMojo.execute(XBeanMojo.java:153)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
>         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:585)
>         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 contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message