Re: Help with integrating maven2 plugin and apache

2008-02-13 Thread Radu Preotiuc-Pietro
Thanks Todd for sharing this on the list.

Radu

On Wed, 2008-02-13 at 13:15 -0500, Todd Nine wrote:
> Hi guys,
>   I wanted to thank everyone for their help.  I finally got it
> working.  Basically, I used the plugin and dependencies below only.
> Then I just added the jar that is generated by the plugin to the
> eclipse classpath manually.  Once I did that, everything worked!
> 
> 
> 
> 
> org.codehaus.mojo
> xmlbeans-maven-plugin
> 
> 
> 
> xmlbeans
> 
> 
> 
> true
> 
> src/main/xsd
> true
> 
> target/eclipse/xmlbeans-eclipse-runtime.jar
> 
> 1.5
> 
> 
> 
> 
> 
> 
> xmlbeans
> xmlbeans
> 2.3.0
> 
> 
> 
> stax
> stax
> 1.2.0
> 
> 
> 
> 
> 
> On Feb 11, 2008 2:44 PM, Todd Nine <[EMAIL PROTECTED]> wrote:
> Thanks for the feedback guys.  I haven't tried the plugin
> below, but wouldn't using the maven 2 plugin to generate a
> jar, then pointing Eclipse to it accomplish the same thing?
> This is what I have for my pom.  If I look at the class files
> that are created within the jar, they're the same ones that
> are getting copied with the plugin you suggested.  Any ideas
> why it works when you use the plugin, but why the jar that
> appears to have the same binaries doesn't? 
> 
> 
> 
> org.codehaus.mojo
> xmlbeans-maven-plugin
> 
> 
> 
> xmlbeans
> 
> 
> 
> true
> 
> 
> src/main/xsd
> true
> 
> 
> target/eclipse/xmlbeans-eclipse-runtime.jar
> 
> 
> 1.5
> 
> 
> 
> 
> Dependencies
> 
> 
> 
> xmlbeans
> xbean
> 2.2.0
> 
> 
> 
> stax
> stax
> 1.2.0
> 
> ...
> 
> 
> 
> 
> 
> On Feb 11, 2008 1:27 AM, David Jencks <[EMAIL PROTECTED]>
> wrote:
> I don't use eclipse.  Apparently the eclipse doesn't
> work well with maven plugins that generate binary code
> that eclipse is supposed to recognize but not compile
> itself.  In geronimo we've written a plugin that IIUC
> copies the generated code to a location that eclipse
> can find.  A typical use of the xmlbeans plugin looks
> like:
> 
> 
> 
> 
> 
> org.codehaus.mojo
> 
>  xmlbeans-maven-plugin
> 
> 
> 
> 
> 
>  org.apache.geronimo.plugins
> 
>  geronimo-maven-plugin
> 2.0.2
> 
> 
> 
> 
>  copy-xmlbeans-schemas
> 
> 
> 
> 
> 
> 
> 
> 
> The next release of this geronimo plugin (probably
> next wednesday) will be 
> 
> 
> 
>  org.apache.geronimo.buildsupport
> 
>  buildsupport-maven-plugin
> 2.1.0
> 
> 
> The trunk source code is
>  at 
> https://svn.apache.org/repos/asf/geronimo/server/trunk/buildsupport/buildsupport-maven-plugin.
>   I don't think it has changed over the last few releases.
> 
> 
> Hope this is relevant to the problems you are havi

Re: Help with integrating maven2 plugin and apache

2008-02-13 Thread Todd Nine
Hi guys,
  I wanted to thank everyone for their help.  I finally got it working.
Basically, I used the plugin and dependencies below only.  Then I just added
the jar that is generated by the plugin to the eclipse classpath manually.
Once I did that, everything worked!




org.codehaus.mojo
xmlbeans-maven-plugin



xmlbeans



true

src/main/xsd
true

target/eclipse/xmlbeans-eclipse-runtime.jar

1.5






xmlbeans
xmlbeans
2.3.0



stax
stax
1.2.0





On Feb 11, 2008 2:44 PM, Todd Nine <[EMAIL PROTECTED]> wrote:

> Thanks for the feedback guys.  I haven't tried the plugin below, but
> wouldn't using the maven 2 plugin to generate a jar, then pointing Eclipse
> to it accomplish the same thing?  This is what I have for my pom.  If I look
> at the class files that are created within the jar, they're the same ones
> that are getting copied with the plugin you suggested.  Any ideas why it
> works when you use the plugin, but why the jar that appears to have the same
> binaries doesn't?
>
> 
> org.codehaus.mojo
> xmlbeans-maven-plugin
> 
> 
> 
> xmlbeans
> 
> 
> 
> true
> 
> src/main/xsd
> true
> 
> target/eclipse/xmlbeans-eclipse-runtime.jar
> 
> 1.5
> 
> 
> 
>
> Dependencies
>
> 
> 
> xmlbeans
> xbean
> 2.2.0
> 
>
> 
> stax
> stax
> 1.2.0
> 
> ...
> 
>
>
>
> On Feb 11, 2008 1:27 AM, David Jencks <[EMAIL PROTECTED]> wrote:
>
> > I don't use eclipse.  Apparently the eclipse doesn't work well with
> > maven plugins that generate binary code that eclipse is supposed to
> > recognize but not compile itself.  In geronimo we've written a plugin that
> > IIUC copies the generated code to a location that eclipse can find.  A
> > typical use of the xmlbeans plugin looks like:
> > 
> > 
> > 
> > org.codehaus.mojo
> > xmlbeans-maven-plugin
> > 
> >
> > 
> > 
> > org.apache.geronimo.plugins
> > geronimo-maven-plugin
> > 2.0.2
> > 
> > 
> > 
> > copy-xmlbeans-schemas
> > 
> > 
> > 
> > 
> > 
> > 
> >
> > The next release of this geronimo plugin (probably next wednesday) will
> > be
> >
> > org.apache.geronimo.buildsupport
> > buildsupport-maven-plugin
> > 2.1.0
> >
> > The trunk source code is  at
> > https://svn.apache.org/repos/asf/geronimo/server/trunk/buildsupport/buildsupport-maven-plugin.
> >  I don't think it has changed over the last few releases.
> >
> > Hope this is relevant to the problems you are having.
> >
> > thanks
> > david jencks
> >
> > On Feb 10, 2008, at 6:21 PM, Todd Nine wrote:
> >
> > Bump,
> >   I've been struggling with this for 2 days.  Note that my title is
> > incorrect, is should say integrating maven 2 plugin and Eclipse.  I've tried
> > downgrading xmlbeans.xbean from 2.2.0 to 2.1.0, which didn't fix my
> > issue.  If I choose a version less than 2.1.0, the plugin completely
> > blows up due to deprecation problems.  Has anyone successfully used this
> > plugin with an Eclipse environment?  If so how did you do it?  This is
> > immensely frustrating, and I don't want to use JAXB, but I'm running out of
> > time to get XML Beans working.
> >
> >
> > Thanks,
> > Todd
> >
> > On Feb 8, 2008 1:03 PM, Todd Nine <[EMAIL PROTECTED]> wrote:
> >
> > > Hi All,
> > >   I'm using XML Beans version 2.2.0, and I'm trying to run my code
> > > through the Eclipse debugger.  Its failing, and I receive the following
> > > errors.  I've included my maven plugin 2 configuration, but basically I'm
> > > having the plugin create a jar of the classes that will be deployed, and
> > > including it into my classpath in Eclipse.  Any idea why I'm getting this
> > > error?  I'm using the same jdk for both maven, and eclipse, so I'm not 
> > > sure
> > > why I'm getting the class version issues.
> > >
> > > Thanks,
> > > Todd
> > >
> > > Mave

Re: Help with integrating maven2 plugin and apache

2008-02-11 Thread Todd Nine
Thanks for the feedback guys.  I haven't tried the plugin below, but
wouldn't using the maven 2 plugin to generate a jar, then pointing Eclipse
to it accomplish the same thing?  This is what I have for my pom.  If I look
at the class files that are created within the jar, they're the same ones
that are getting copied with the plugin you suggested.  Any ideas why it
works when you use the plugin, but why the jar that appears to have the same
binaries doesn't?


org.codehaus.mojo
xmlbeans-maven-plugin



xmlbeans



true

src/main/xsd
true

target/eclipse/xmlbeans-eclipse-runtime.jar

1.5




Dependencies



xmlbeans
xbean
2.2.0



stax
stax
1.2.0

...



On Feb 11, 2008 1:27 AM, David Jencks <[EMAIL PROTECTED]> wrote:

> I don't use eclipse.  Apparently the eclipse doesn't work well with maven
> plugins that generate binary code that eclipse is supposed to recognize but
> not compile itself.  In geronimo we've written a plugin that IIUC copies the
> generated code to a location that eclipse can find.  A typical use of the
> xmlbeans plugin looks like:
> 
> 
> 
> org.codehaus.mojo
> xmlbeans-maven-plugin
> 
>
> 
> 
> org.apache.geronimo.plugins
> geronimo-maven-plugin
> 2.0.2
> 
> 
> 
> copy-xmlbeans-schemas
> 
> 
> 
> 
> 
> 
>
> The next release of this geronimo plugin (probably next wednesday) will
> be
>
> org.apache.geronimo.buildsupport
> buildsupport-maven-plugin
> 2.1.0
>
> The trunk source code is  at
> https://svn.apache.org/repos/asf/geronimo/server/trunk/buildsupport/buildsupport-maven-plugin.
>  I don't think it has changed over the last few releases.
>
> Hope this is relevant to the problems you are having.
>
> thanks
> david jencks
>
> On Feb 10, 2008, at 6:21 PM, Todd Nine wrote:
>
> Bump,
>   I've been struggling with this for 2 days.  Note that my title is
> incorrect, is should say integrating maven 2 plugin and Eclipse.  I've tried
> downgrading xmlbeans.xbean from 2.2.0 to 2.1.0, which didn't fix my
> issue.  If I choose a version less than 2.1.0, the plugin completely blows
> up due to deprecation problems.  Has anyone successfully used this plugin
> with an Eclipse environment?  If so how did you do it?  This is immensely
> frustrating, and I don't want to use JAXB, but I'm running out of time to
> get XML Beans working.
>
>
> Thanks,
> Todd
>
> On Feb 8, 2008 1:03 PM, Todd Nine <[EMAIL PROTECTED]> wrote:
>
> > Hi All,
> >   I'm using XML Beans version 2.2.0, and I'm trying to run my code
> > through the Eclipse debugger.  Its failing, and I receive the following
> > errors.  I've included my maven plugin 2 configuration, but basically I'm
> > having the plugin create a jar of the classes that will be deployed, and
> > including it into my classpath in Eclipse.  Any idea why I'm getting this
> > error?  I'm using the same jdk for both maven, and eclipse, so I'm not sure
> > why I'm getting the class version issues.
> >
> > Thanks,
> > Todd
> >
> > Maven plugin configuration:
> > 
> > org.codehaus.mojo
> > xmlbeans-maven-plugin
> > 
> > 
> > 
> > xmlbeans
> > 
> > 
> > 
> > true
> > 
> > src/main/xsd
> > true
> > target/eclipse/xmlbeans-
> > eclipse-runtime.jar
> > 
> >
> > Exception stacktrace:
> >
> > java.lang.ExceptionInInitializerError
> > at sun.misc.Unsafe.ensureClassInitialized(Native Method)
> > at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(
> > UnsafeFieldAccessorFactory.java:25)
> > at sun.reflect.ReflectionFactory.newFieldAccessor(
> > ReflectionFactory.java:122)
> > at java.lang.reflect.Field.acquireFieldAccessor(Field.java:917)
> > at java.lang.reflect.Field.getFieldAccessor(Field.java:898)
> > at java.lang.reflect.Field.get(Field.java:357)
> > at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(
> > XmlBeans.java:770)
> > at com.onwebconsulting.urchin.profiles.ProfilesDocument.(Unknown
> > Source)
> > at
> > com.onwebconsulting.urchin.pr

Re: Help with integrating maven2 plugin and apache

2008-02-10 Thread David Jencks
I don't use eclipse.  Apparently the eclipse doesn't work well with  
maven plugins that generate binary code that eclipse is supposed to  
recognize but not compile itself.  In geronimo we've written a plugin  
that IIUC copies the generated code to a location that eclipse can  
find.  A typical use of the xmlbeans plugin looks like:





org.codehaus.mojo
xmlbeans-maven-plugin




org.apache.geronimo.plugins
geronimo-maven-plugin
2.0.2



copy-xmlbeans-schemas







The next release of this geronimo plugin (probably next wednesday)  
will be


org.apache.geronimo.buildsupport
buildsupport-maven-plugin
2.1.0

The trunk source code is  at https://svn.apache.org/repos/asf/ 
geronimo/server/trunk/buildsupport/buildsupport-maven-plugin.  I  
don't think it has changed over the last few releases.


Hope this is relevant to the problems you are having.

thanks
david jencks

On Feb 10, 2008, at 6:21 PM, Todd Nine wrote:


Bump,
  I've been struggling with this for 2 days.  Note that my title is  
incorrect, is should say integrating maven 2 plugin and Eclipse.   
I've tried downgrading xmlbeans.xbean from 2.2.0 to 2.1.0, which  
didn't fix my issue.  If I choose a version less than 2.1.0, the  
plugin completely blows up due to deprecation problems.  Has anyone  
successfully used this plugin with an Eclipse environment?  If so  
how did you do it?  This is immensely frustrating, and I don't want  
to use JAXB, but I'm running out of time to get XML Beans working.



Thanks,
Todd

On Feb 8, 2008 1:03 PM, Todd Nine <[EMAIL PROTECTED]> wrote:
Hi All,
  I'm using XML Beans version 2.2.0, and I'm trying to run my code  
through the Eclipse debugger.  Its failing, and I receive the  
following errors.  I've included my maven plugin 2 configuration,  
but basically I'm having the plugin create a jar of the classes  
that will be deployed, and including it into my classpath in  
Eclipse.  Any idea why I'm getting this error?  I'm using the same  
jdk for both maven, and eclipse, so I'm not sure why I'm getting  
the class version issues.


Thanks,
Todd

Maven plugin configuration:

org.codehaus.mojo
xmlbeans-maven-plugin



xmlbeans



true

src/main/xsd
true
target/eclipse/xmlbeans-eclipse- 
runtime.jar



Exception stacktrace:

java.lang.ExceptionInInitializerError
at sun.misc.Unsafe.ensureClassInitialized(Native Method)
at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor 
(UnsafeFieldAccessorFactory.java:25)
at sun.reflect.ReflectionFactory.newFieldAccessor 
(ReflectionFactory.java:122)

at java.lang.reflect.Field.acquireFieldAccessor(Field.java:917)
at java.lang.reflect.Field.getFieldAccessor(Field.java:898)
at java.lang.reflect.Field.get(Field.java:357)
at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader 
(XmlBeans.java:770)
at com.onwebconsulting.urchin.profiles.ProfilesDocument. 
(Unknown Source)
at com.onwebconsulting.urchin.profiles.ProfilesDocument 
$Factory.parse(Unknown Source)
at com.bnp.insightCommon.dao.rest.UrchinDaoImpl.getProfiles 
(UrchinDaoImpl.java:81)
at com.bnp.insightCommon.dao.UrchinDaoTest.getProfiles 
(UrchinDaoTest.java:54)
at com.bnp.insightCommon.dao.UrchinDaoTest.testGetProfiles 
(UrchinDaoTest.java:41)

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 junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at org.springframework.test.ConditionalTestCase.runBare 
(ConditionalTestCase.java:69)

at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at  
org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run 
(JUnit3TestReference.java:130)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run 
(TestExecution.java:38)
at  
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner

Re: Help with integrating maven2 plugin and apache

2008-02-10 Thread Jacob Danner
Hi Todd,
I'm not an eclipse user (IntelliJ IDEA), but I'll give it a try. Which
maven plugin are you using, which version of eclipse?
Have you queried the maven or eclipse projects for similar issues?
-jacobd

On Feb 10, 2008 6:21 PM, Todd Nine <[EMAIL PROTECTED]> wrote:
> Bump,
>   I've been struggling with this for 2 days.  Note that my title is
> incorrect, is should say integrating maven 2 plugin and Eclipse.  I've tried
> downgrading xmlbeans.xbean from 2.2.0 to 2.1.0, which didn't fix my issue.
> If I choose a version less than 2.1.0, the plugin completely blows up due to
> deprecation problems.  Has anyone successfully used this plugin with an
> Eclipse environment?  If so how did you do it?  This is immensely
> frustrating, and I don't want to use JAXB, but I'm running out of time to
> get XML Beans working.
>
>
> Thanks,
> Todd
>
>
>
> On Feb 8, 2008 1:03 PM, Todd Nine <[EMAIL PROTECTED]> wrote:
> > Hi All,
> >   I'm using XML Beans version 2.2.0, and I'm trying to run my code through
> the Eclipse debugger.  Its failing, and I receive the following errors.
> I've included my maven plugin 2 configuration, but basically I'm having the
> plugin create a jar of the classes that will be deployed, and including it
> into my classpath in Eclipse.  Any idea why I'm getting this error?  I'm
> using the same jdk for both maven, and eclipse, so I'm not sure why I'm
> getting the class version issues.
> >
> > Thanks,
> > Todd
> >
> > Maven plugin configuration:
> > 
> > org.codehaus.mojo
> > xmlbeans-maven-plugin
> > 
> > 
> > 
> > xmlbeans
> > 
> > 
> > 
> > true
> > 
> > src/main/xsd
> > true
> >
> target/eclipse/xmlbeans-eclipse-runtime.jar
> > 
> >
> > Exception stacktrace:
> >
> > java.lang.ExceptionInInitializerError
> > at sun.misc.Unsafe.ensureClassInitialized(Native Method)
> > at
> sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:25)
> > at
> sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:122)
> > at java.lang.reflect.Field.acquireFieldAccessor(Field.java:917)
> > at java.lang.reflect.Field.getFieldAccessor(Field.java:898)
> > at java.lang.reflect.Field.get(Field.java:357)
> > at
> org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:770)
> > at
> com.onwebconsulting.urchin.profiles.ProfilesDocument.(Unknown
> Source)
> > at
> com.onwebconsulting.urchin.profiles.ProfilesDocument$Factory.parse(Unknown
> Source)
> > at
> com.bnp.insightCommon.dao.rest.UrchinDaoImpl.getProfiles(UrchinDaoImpl.java:81)
> > at
> com.bnp.insightCommon.dao.UrchinDaoTest.getProfiles(UrchinDaoTest.java:54)
> > at
> com.bnp.insightCommon.dao.UrchinDaoTest.testGetProfiles(UrchinDaoTest.java:41)
> > 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 junit.framework.TestCase.runTest(TestCase.java:154)
> > at junit.framework.TestCase.runBare(TestCase.java:127)
> > at
> org.springframework.test.ConditionalTestCase.runBare(ConditionalTestCase.java:69)
> > at junit.framework.TestResult$1.protect(TestResult.java:106)
> > at junit.framework.TestResult.runProtected(TestResult.java:124)
> > at junit.framework.TestResult.run(TestResult.java:109)
> > at junit.framework.TestCase.run(TestCase.java:118)
> > at junit.framework.TestSuite.runTest(TestSuite.java:208)
> > at junit.framework.TestSuite.run(TestSuite.java:203)
> > at
> org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
> > at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> > at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
> > at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
> > at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> > at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
> > Caused by: java.lang.RuntimeException: Could not instantiate
> SchemaTypeSystemImpl (java.lang.reflect.InvocationTargetException): is the
> version of xbean.jar correct?
> > at
> schemaorg_apache_xmlbeans.system.sD0FCECC1CA81F97745FE1F9A4449F63C.TypeSystemHolder.loadTypeSystem(Unknown
> Source)
> > at
> schemaorg_apache_xmlbeans.system.sD0FCECC1CA81F97745FE1F9A4449F63C.TypeSystemHolder.(Unknown
> Source)
> > ... 31 more
> >

Re: Help with integrating maven2 plugin and apache

2008-02-10 Thread Todd Nine
Bump,
  I've been struggling with this for 2 days.  Note that my title is
incorrect, is should say integrating maven 2 plugin and Eclipse.  I've tried
downgrading xmlbeans.xbean from 2.2.0 to 2.1.0, which didn't fix my issue.
If I choose a version less than 2.1.0, the plugin completely blows up due to
deprecation problems.  Has anyone successfully used this plugin with an
Eclipse environment?  If so how did you do it?  This is immensely
frustrating, and I don't want to use JAXB, but I'm running out of time to
get XML Beans working.


Thanks,
Todd

On Feb 8, 2008 1:03 PM, Todd Nine <[EMAIL PROTECTED]> wrote:

> Hi All,
>   I'm using XML Beans version 2.2.0, and I'm trying to run my code through
> the Eclipse debugger.  Its failing, and I receive the following errors.
> I've included my maven plugin 2 configuration, but basically I'm having the
> plugin create a jar of the classes that will be deployed, and including it
> into my classpath in Eclipse.  Any idea why I'm getting this error?  I'm
> using the same jdk for both maven, and eclipse, so I'm not sure why I'm
> getting the class version issues.
>
> Thanks,
> Todd
>
> Maven plugin configuration:
> 
> org.codehaus.mojo
> xmlbeans-maven-plugin
> 
> 
> 
> xmlbeans
> 
> 
> 
> true
> 
> src/main/xsd
> true
> target/eclipse/xmlbeans-eclipse-runtime.jar
> 
> 
>
> Exception stacktrace:
>
> java.lang.ExceptionInInitializerError
> at sun.misc.Unsafe.ensureClassInitialized(Native Method)
> at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(
> UnsafeFieldAccessorFactory.java:25)
> at sun.reflect.ReflectionFactory.newFieldAccessor(
> ReflectionFactory.java:122)
> at java.lang.reflect.Field.acquireFieldAccessor(Field.java:917)
> at java.lang.reflect.Field.getFieldAccessor(Field.java:898)
> at java.lang.reflect.Field.get(Field.java:357)
> at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java
> :770)
> at com.onwebconsulting.urchin.profiles.ProfilesDocument.(Unknown
> Source)
> at 
> com.onwebconsulting.urchin.profiles.ProfilesDocument$Factory.parse(Unknown
> Source)
> at com.bnp.insightCommon.dao.rest.UrchinDaoImpl.getProfiles(
> UrchinDaoImpl.java:81)
> at com.bnp.insightCommon.dao.UrchinDaoTest.getProfiles(
> UrchinDaoTest.java:54)
> at com.bnp.insightCommon.dao.UrchinDaoTest.testGetProfiles(
> UrchinDaoTest.java:41)
> 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 junit.framework.TestCase.runTest(TestCase.java:154)
> at junit.framework.TestCase.runBare(TestCase.java:127)
> at org.springframework.test.ConditionalTestCase.runBare(
> ConditionalTestCase.java:69)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:118)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at
> org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(
> JUnit3TestReference.java:130)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(
> TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(
> RemoteTestRunner.java:460)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(
> RemoteTestRunner.java:673)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(
> RemoteTestRunner.java:386)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(
> RemoteTestRunner.java:196)
> Caused by: java.lang.RuntimeException: Could not instantiate
> SchemaTypeSystemImpl (java.lang.reflect.InvocationTargetException): is the
> version of xbean.jar correct?
> at
> schemaorg_apache_xmlbeans.system.sD0FCECC1CA81F97745FE1F9A4449F63C.TypeSystemHolder.loadTypeSystem(Unknown
> Source)
> at
> schemaorg_apache_xmlbeans.system.sD0FCECC1CA81F97745FE1F9A4449F63C.TypeSystemHolder.(Unknown
> Source)
> ... 31 more
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(
> NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
> DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Construct

Help with integrating maven2 plugin and apache

2008-02-08 Thread Todd Nine
Hi All,
  I'm using XML Beans version 2.2.0, and I'm trying to run my code through
the Eclipse debugger.  Its failing, and I receive the following errors.
I've included my maven plugin 2 configuration, but basically I'm having the
plugin create a jar of the classes that will be deployed, and including it
into my classpath in Eclipse.  Any idea why I'm getting this error?  I'm
using the same jdk for both maven, and eclipse, so I'm not sure why I'm
getting the class version issues.

Thanks,
Todd

Maven plugin configuration:

org.codehaus.mojo
xmlbeans-maven-plugin



xmlbeans



true

src/main/xsd
true
target/eclipse/xmlbeans-eclipse-runtime.jar



Exception stacktrace:

java.lang.ExceptionInInitializerError
at sun.misc.Unsafe.ensureClassInitialized(Native Method)
at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(
UnsafeFieldAccessorFactory.java:25)
at sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java
:122)
at java.lang.reflect.Field.acquireFieldAccessor(Field.java:917)
at java.lang.reflect.Field.getFieldAccessor(Field.java:898)
at java.lang.reflect.Field.get(Field.java:357)
at org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java
:770)
at com.onwebconsulting.urchin.profiles.ProfilesDocument.(Unknown
Source)
at 
com.onwebconsulting.urchin.profiles.ProfilesDocument$Factory.parse(Unknown
Source)
at com.bnp.insightCommon.dao.rest.UrchinDaoImpl.getProfiles(
UrchinDaoImpl.java:81)
at com.bnp.insightCommon.dao.UrchinDaoTest.getProfiles(
UrchinDaoTest.java:54)
at com.bnp.insightCommon.dao.UrchinDaoTest.testGetProfiles(
UrchinDaoTest.java:41)
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 junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at org.springframework.test.ConditionalTestCase.runBare(
ConditionalTestCase.java:69)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(
JUnit3TestReference.java:130)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(
TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(
RemoteTestRunner.java:460)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(
RemoteTestRunner.java:673)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(
RemoteTestRunner.java:386)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(
RemoteTestRunner.java:196)
Caused by: java.lang.RuntimeException: Could not instantiate
SchemaTypeSystemImpl (java.lang.reflect.InvocationTargetException): is the
version of xbean.jar correct?
at
schemaorg_apache_xmlbeans.system.sD0FCECC1CA81F97745FE1F9A4449F63C.TypeSystemHolder.loadTypeSystem(Unknown
Source)
at
schemaorg_apache_xmlbeans.system.sD0FCECC1CA81F97745FE1F9A4449F63C.TypeSystemHolder.(Unknown
Source)
... 31 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(
NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
... 33 more
Caused by: org.apache.xmlbeans.SchemaTypeLoaderException: XML-BEANS compiled
schema: Incompatible minor version - expecting up to 23, got 24
(schemaorg_apache_xmlbeans.system.sD0FCECC1CA81F97745FE1F9A4449F63C.index) -
code 3
at org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl$XsbReader
.(SchemaTypeSystemImpl.java:1522)
at org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.initFromHeader(
SchemaTypeSystemImpl.java:260)
at org.apache.xmlbeans.impl.schema.SchemaTypeSystemImpl.(
SchemaTypeSystemImpl.java:183)
... 37 more