openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey" <plins...@bea.com>
Subject RE: add-was-interfaces
Date Tue, 07 Nov 2006 03:21:58 GMT
Looks like it only happens on a non-clean run. Makes sense, since
presumably on the second run, it tries to instantiate the then-processed
plugin, at which time the exception occurs.

Interesting. It could be that you're using serp in a way that requires
the classes to be loadable. 

(Can't investigate further... dinner is calling...)

-Patrick

-- 
Patrick Linskey
BEA Systems, Inc. 

_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it. 

> -----Original Message-----
> From: Michael Dick [mailto:michael.d.dick@gmail.com] 
> Sent: Monday, November 06, 2006 7:14 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: add-was-interfaces
> 
> Hi Patrick,
> 
> I just ran svn update and mvn clean package and I didn't get 
> the error and I
> didn't put any WebSphere jars on the classpath (ran it at home to make
> sure). Are you using the newer version of Serp by any chance? 
>  I tried the
> -X and -e flags with maven and I didn't see the same problem, 
> I'm not sure
> what else I could be doing different.
> 
> As far as I know the WebSphere interfaces aren't published 
> (as class files)
> anywhere so we can't compile against them. To get around the 
> problem I used
> Serp to add the interface to the class. At the time I didn't 
> see any errors
> from Serp, but if that's no longer the case we'll have to come up with
> something else.
> 
> One alternative is to create a stub class similar to what we do for
> sun.misc.Perf in openjpa-lib, assuming that doesn't violate a license
> agreement.
> 
> On 11/6/06, Patrick Linskey <plinskey@bea.com> wrote:
> >
> > Hi,
> >
> > I get the following stack trace when running 'mvn package'. It looks
> > like I don't have some required IBM classes in my classpath.
> > Surprisingly, this exception does not cause the build to fail, but
> > presumably, the output bytes are not the same as if this had run
> > successfully.
> >
> > Does anyone have any suggestions for either getting the 
> classes into the
> > classpath or moving the exception to runtime, so that there aren't
> > build-time dependency issues resulting in different jars 
> from the same
> > sources?
> >
> > Thanks,
> >
> > -Patrick
> >
> >
> > Partial stack trace:
> >
> > [INFO] [antrun:run {execution: add-was-interfaces}]
> > [INFO] Executing tasks
> >      [java] java.lang.IllegalArgumentException:
> > java.lang.NoClassDefFoundError:
> > com/ibm/websphere/jtaextensions/SynchronizationCallback
> >      [java]     at
> > 
> org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.
> java:180)
> >      [java]     at 
> org.apache.tools.ant.taskdefs.Java.run(Java.java:710)
> >      [java]     at
> > org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:178)
> >
> >      [java]     at
> > org.apache.tools.ant.taskdefs.Java.execute(Java.java:84)
> >      [java]     at
> > org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
> >      [java]     at org.apache.tools.ant.Task.perform(Task.java:364)
> >      [java]     at 
> org.apache.tools.ant.Target.execute(Target.java:341)
> >      [java]     at
> > 
> org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(Ab
> stractAntM
> > ojo.java:108)
> >      [java]     at
> > 
> org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83)
> >      [java]     at
> > 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(Defau
> ltPluginMa
> > nager.java:412)
> >      [java]     at
> > 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoa
> ls(Default
> > LifecycleExecutor.java:534)
> >      .....
> >
> >      [java] Caused by: java.lang.IllegalArgumentException:
> > java.lang.NoClassDefFoundError:
> > com/ibm/websphere/jtaextensions/SynchronizationCallback
> >      [java]     at serp.util.Strings.toClass(Strings.java:211)
> >      [java]     at serp.util.Strings.toClass(Strings.java:140)
> >      [java]     at serp.bytecode.BCClass.getType(BCClass.java:565)
> >      [java]     at serp.bytecode.BCClass.write(BCClass.java:202)
> >      [java]     at
> > 
> org.apache.openjpa.ee.WASManagedRuntime.main(WASManagedRuntime
> .java:412)
> >      [java]     at 
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> > Method)
> >
> > --
> > Patrick Linskey
> > BEA Systems, Inc.
> >
> > 
> ______________________________________________________________
> _________
> > Notice:  This email message, together with any attachments, 
> may contain
> > information  of  BEA Systems,  Inc.,  its subsidiaries  and 
>  affiliated
> > entities,  that may be confidential,  proprietary,  
> copyrighted  and/or
> > legally privileged, and is intended solely for the use of 
> the individual
> > or entity named in this message. If you are not the 
> intended recipient,
> > and have received this message in error, please immediately 
> return this
> > by email and then delete it.
> >
> 
> -- 
> -Michael Dick
> 

Mime
View raw message