Bug 220248 - BCException caused by spring-aspect.jar (@Configurable)
Summary: BCException caused by spring-aspect.jar (@Configurable)
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: DEVELOPMENT   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 1.6.0   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-25 13:32 EST by Hermann Voßeler CLA
Modified: 2008-04-25 11:13 EDT (History)
3 users (show)

See Also:

Attachments
Testcase triggering the error (10.33 KB, application/octet-stream)
2008-02-25 13:48 EST, Hermann Vosseler CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Hermann Voßeler CLA 2008-02-25 13:32:15 EST 
Use of the @Configurable annotation and weaving with spring-aspect.jar
causes:

org.aspectj.weaver.BCException
at org.aspectj.weaver.AjAttribute.read(AjAttribute.java:127)
at org.aspectj.weaver.bcel.BcelAttributes.readAjAttributes(BcelAttributes.java:66)
at org.aspectj.weaver.bcel.BcelObjectType.ensureAspectJAttributesUnpacked(BcelObjectType.java:312)
at org.aspectj.weaver.bcel.BcelObjectType.<init>(BcelObjectType.java:142)
at org.aspectj.weaver.bcel.BcelWorld.buildBcelDelegate(BcelWorld.java:360)
at org.aspectj.weaver. ... n thrown: malformed org.aspectj.weaver.PointcutDeclaration attribute java.io.EOFException
when batch building BuildConfig[/home/hiv/defect1] #Files=1



Using ECLIPSE Version: 3.3.1.1  Build id: M20071023-1652
AJDT Version: 1.5.2.200802061816 (with AspectJ version: 1.6.0.20080206212408)

with Ubuntu Gutsy on i386

The Spring-Aspects are from Spring-Version: 2.0.1


The same worked without problems with AJDT 1.5.0.200706070619
Comment 1 Hermann Vosseler CLA 2008-02-25 13:48:47 EST 
Created attachment 90668 [details]
Testcase triggering the error

...you need additionaly the @Configurable from spring(2.0.1)
Comment 2 Andrew Clement CLA 2008-02-25 15:37:42 EST 
I *think* this is fixed in the latest AJ dev builds (which haven't been packaged inside AJDT yet) - are you able to try it out with the latest AJ?

I plan to do a new AJDT later today with the 1.6.0m2 driver in.
Comment 3 Andrew Clement CLA 2008-04-23 20:24:36 EDT 
are you still seeing this problem?
Comment 4 Hermann Voßeler CLA 2008-04-24 16:19:06 EDT 
As far as I can tell this problem is gone now.
Switched the affected project last weak to work with the AJDT currently on the update site. Worked well, including incremental compliation. Thanks very much!
Comment 5 Andrew Clement CLA 2008-04-25 11:13:02 EDT 
thanks for letting me know.