RE: [Springframework-developer] re: java.lang.IncompatibleClassChangeError

[Bronwen C. <bro...@ya...>]

Hi
I'm lost :-( sorry to trouble you I have changed all the jars, deleted =
the
classes directory, rebuilt the project same result. I am using intelliJ
idea, all the jars I use are in one directory, I have checked idea's =
path
settings and they are all pointing to the same jars in the directory to
where I am expecting them to point to, I have nothing in my jdk/lib/ext

These are the jars I am using:

aopalliance.jar  // from build 1.0.2
commons-beanutils.jar // from build 1.0.2
commons-collections.jar // from build 1.0.2
commons-fileupload.jar // from build 1.0.2
commons-lang.jar   // from build 1.0.2
commons-logging.jar  // from build 1.0.2
dom4j.jar   // from build 1.0.2
dom.jar
jakarta-oro-2.0.7.jar  // from build 1.0.2
jakarta-regexp-1.3.jar  // ran tests with and without to check same =
result
jaxen.jar  // not from spring
jaxp-api.jar  // not from spring
jstl.jar  // not from spring
log4j-1.2.8.jar
sax.jar
saxpath.jar
spring.jar  // 1.0.2 version
standard.jar
xalan.jar
xercesImpl.jar

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf =
Of
j=FCrgen h=F6ller [werk3AT]
Sent: 25 May 2004 09:40
To: spr...@li...
Subject: Re: [Springframework-developer] re:
java.lang.IncompatibleClassChangeError

Have you got old spring jars in your class path? That sort of error can =
just
happen when you've built against classes that are not the same during
runtime.
=20
DO_NOT_PROXY and co in AbstractAutoProxyCreator have changed from =
"protected
final" to "protected static final" (an oversight that's been corrected). =
But
as long as everything is built against the current version, that =
shouldn't
matter.
=20
That just made me aware that we actually require rebuilding your apps
against new Spring jars. That's not a big problem, I guess, but it means
that new Spring jars are in general not a drop-in replacement for =
runtime
environments.
=20
In other words, current Spring releases are source compatible but not
necessarily binary compatible. So to be on the safe side, rebuild your =
app
against the Spring jars that you intend to use, and everything should =
work.
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von
Bronwen Cassidy
Gesendet: Di 25.05.2004 11:07
An: spr...@li...
Betreff: [Springframework-developer] re:
java.lang.IncompatibleClassChangeError



Hi Just tried the CVS version for spring (pre 1.0.2) I have been using
1.0.1, when running my AOP tests I get the following stack trace, the =
same
happens in weblogic:

=20

java.lang.IncompatibleClassChangeError

            at
org.springframework.aop.framework.autoproxy.AbstractAdvisorAutoProxyCreat=
or.
getInterceptorsAndAdvisorsForBean(AbstractAdvisorAutoProxyCreator.java:66=
)

            at
org.springframework.aop.framework.autoproxy.AbstractAutoProxyCreator.post=
Pro
cessAfterInitialization(AbstractAutoProxyCreator.java:209)

            at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFact=
ory
.applyBeanPostProcessorsAfterInitialization(AbstractAutowireCapableBeanFa=
cto
ry.java:150)

            at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFact=
ory
.createBean(AbstractAutowireCapableBeanFactory.java:234)

            at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFact=
ory
.createBean(AbstractAutowireCapableBeanFactory.java:172)

            at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(Abs=
tra
ctBeanFactory.java:159)

            at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preI=
nst
antiateSingletons(DefaultListableBeanFactory.java:178)

            at
org.springframework.context.support.AbstractApplicationContext.refresh(Ab=
str
actApplicationContext.java:269)

            at
org.springframework.context.support.ClassPathXmlApplicationContext.<init>=
(Cl
assPathXmlApplicationContext.java:58)

=20

this is when upgrading spring.jar and aopalliance.jar. I cannot figure =
out
what has gone wrong, if I replace spring.jar with the 1.0.1 version,
everything runs with no problems, help :-)

=20

This happens in AbstractAdvisorAutoproxyCreator here:

=20

List advices =3D findEligibleAdvisors(bean.getClass());

f (advices.isEmpty()) {

                        return DO_NOT_PROXY;

            }=20

=20

The return DO_NOT_PROXY ends up with the error, the debugger goes no
further??

=20

Thanx in advance

Bronwen



-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. =

Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id149&alloc_id=8166&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer