[aspects] Can't weave a simple aspect to Eclipse 3.4

Hi,

While trying to weave a simple aspect in Eclipse 3.4.1 with Equinox Aspects
M3 I'm getting an error (attached). The config.ini I'm using is:

osgi.bundles=org.eclipse.equinox.common <at> 2\:start,org.eclipse.update.configur
ator <at> 3\:start,org.eclipse.core.runtime <at> start,org.eclipse.equinox.weaving.asp
ectj <at> 1\:start,org.eclipse.equinox.weaving.caching@:start, aosgi.test
osgi.bundles.defaultStartLevel=4
osgi.framework=org.eclipse.osgi
osgi.configuration.cascaded=false
osgi.splashPath = platform:/base/plugins/org.eclipse.platform

# AOSGi
osgi.framework.extensions=org.eclipse.equinox.weaving.hook
org.aspectj.weaver.loadtime.configuration=META-INF/aop.xml;org/aspectj/aop.x
ml;META-INF/aop-ajc.xml
#aj.weaving.verbose=true
org.aspectj.weaver.showWeaveInfo=true
org.aspectj.osgi.verbose=true

Basically, this config.ini was used with Eclipse 3.3 (except for
modifications in osgi.bundles and in osgi.framework.extensions).

Please help,
Oren

!SESSION 2008-11-03 10:30:27.139 -----------------------------------------------

aspects

Re: [aspects] Can't weave a simple aspect to Eclipse 3.4

Hi Oren!

I am observing an endless recursion within the stack trace. Looks pretty 
much like a bug in the new supplementer mechanisms implementation. Would 
be great if you could create a new bug for this and maybe attach a small 
example to reproduce the problem? That would be great.

Cheers,
-Martin

> While trying to weave a simple aspect in Eclipse 3.4.1 with Equinox Aspects
> M3 I'm getting an error (attached). The config.ini I'm using is:
> 
> osgi.bundles=org.eclipse.equinox.common <at> 2\:start,org.eclipse.update.configur
> ator <at> 3\:start,org.eclipse.core.runtime <at> start,org.eclipse.equinox.weaving.asp
> ectj <at> 1\:start,org.eclipse.equinox.weaving.caching@:start, aosgi.test
> osgi.bundles.defaultStartLevel=4
> osgi.framework=org.eclipse.osgi
> osgi.configuration.cascaded=false
> osgi.splashPath = platform:/base/plugins/org.eclipse.platform
> 
> # AOSGi
> osgi.framework.extensions=org.eclipse.equinox.weaving.hook
> org.aspectj.weaver.loadtime.configuration=META-INF/aop.xml;org/aspectj/aop.x
> ml;META-INF/aop-ajc.xml
> #aj.weaving.verbose=true
> org.aspectj.weaver.showWeaveInfo=true
> org.aspectj.osgi.verbose=true
> 
> Basically, this config.ini was used with Eclipse 3.3 (except for
> modifications in osgi.bundles and in osgi.framework.extensions).
> 
> Please help,
> Oren
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@...
> https://dev.eclipse.org/mailman/listinfo/equinox-dev

RE: [aspects] Can't weave a simple aspect to Eclipse 3.4

Ok no problem. BTW it works with M2.
Oren

-----Original Message-----
From: equinox-dev-bounces@...
[mailto:equinox-dev-bounces@...] On Behalf Of Martin Lippert
Sent: Monday, November 03, 2008 12:34 PM
To: Equinox development mailing list
Subject: Re: [equinox-dev] [aspects] Can't weave a simple aspect to Eclipse
3.4

Hi Oren!

I am observing an endless recursion within the stack trace. Looks pretty 
much like a bug in the new supplementer mechanisms implementation. Would 
be great if you could create a new bug for this and maybe attach a small 
example to reproduce the problem? That would be great.

Cheers,
-Martin

> While trying to weave a simple aspect in Eclipse 3.4.1 with Equinox
Aspects
> M3 I'm getting an error (attached). The config.ini I'm using is:
> 
>
osgi.bundles=org.eclipse.equinox.common <at> 2\:start,org.eclipse.update.configur
>
ator <at> 3\:start,org.eclipse.core.runtime <at> start,org.eclipse.equinox.weaving.asp
> ectj <at> 1\:start,org.eclipse.equinox.weaving.caching@:start, aosgi.test
> osgi.bundles.defaultStartLevel=4
> osgi.framework=org.eclipse.osgi
> osgi.configuration.cascaded=false
> osgi.splashPath = platform:/base/plugins/org.eclipse.platform
> 
> # AOSGi
> osgi.framework.extensions=org.eclipse.equinox.weaving.hook
>
org.aspectj.weaver.loadtime.configuration=META-INF/aop.xml;org/aspectj/aop.x
> ml;META-INF/aop-ajc.xml
> #aj.weaving.verbose=true
> org.aspectj.weaver.showWeaveInfo=true
> org.aspectj.osgi.verbose=true
> 
> Basically, this config.ini was used with Eclipse 3.3 (except for
> modifications in osgi.bundles and in osgi.framework.extensions).
> 
> Please help,
> Oren
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@...
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@...
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Re: [aspects] Can't weave a simple aspect to Eclipse 3.4

Hi Oren!

> Ok no problem. BTW it works with M2.

Great, thanks. Seems to be related to the changed supplementer mechanism 
and that change was introduced by M3. Will try to fix that as soon as 
possible. Looking forward to your test scenario.

Sorry for causing you trouble with M3.

Cheers,
-Martin

> Oren
> 
> -----Original Message-----
> From: equinox-dev-bounces@...
> [mailto:equinox-dev-bounces@...] On Behalf Of Martin Lippert
> Sent: Monday, November 03, 2008 12:34 PM
> To: Equinox development mailing list
> Subject: Re: [equinox-dev] [aspects] Can't weave a simple aspect to Eclipse
> 3.4
> 
> Hi Oren!
> 
> I am observing an endless recursion within the stack trace. Looks pretty 
> much like a bug in the new supplementer mechanisms implementation. Would 
> be great if you could create a new bug for this and maybe attach a small 
> example to reproduce the problem? That would be great.
> 
> Cheers,
> -Martin
> 
> 
> 
> 
> 
>> While trying to weave a simple aspect in Eclipse 3.4.1 with Equinox
> Aspects
>> M3 I'm getting an error (attached). The config.ini I'm using is:
>>
>>
> osgi.bundles=org.eclipse.equinox.common <at> 2\:start,org.eclipse.update.configur
> ator <at> 3\:start,org.eclipse.core.runtime <at> start,org.eclipse.equinox.weaving.asp
>> ectj <at> 1\:start,org.eclipse.equinox.weaving.caching@:start, aosgi.test
>> osgi.bundles.defaultStartLevel=4
>> osgi.framework=org.eclipse.osgi
>> osgi.configuration.cascaded=false
>> osgi.splashPath = platform:/base/plugins/org.eclipse.platform
>>
>> # AOSGi
>> osgi.framework.extensions=org.eclipse.equinox.weaving.hook
>>
> org.aspectj.weaver.loadtime.configuration=META-INF/aop.xml;org/aspectj/aop.x
>> ml;META-INF/aop-ajc.xml
>> #aj.weaving.verbose=true
>> org.aspectj.weaver.showWeaveInfo=true
>> org.aspectj.osgi.verbose=true
>>
>> Basically, this config.ini was used with Eclipse 3.3 (except for
>> modifications in osgi.bundles and in osgi.framework.extensions).
>>
>> Please help,
>> Oren
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> equinox-dev mailing list
>> equinox-dev@...
>> https://dev.eclipse.org/mailman/listinfo/equinox-dev
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@...
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
> 
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@...
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
> 
> 

quick way to find who is exporting a package

Re: quick way to find who is exporting a package

ClassLoader incompatibilities due to EquinoxFWClassLoader

In our tests for dm Server we are firing up an Equinox instance many times in the same VM and after the first
invocation (which loads Equinox types with the app ClassLoader), our tests fail because Equinox types
are loaded with an EquinoxFWClassLoader. This behaviour cannot easily be stopped because the
FrameworkProperties.inUse() method always returns true.

The issue for us in using EquinoxFWClassLoader is that we get test failures due to class
incompatibilities. In our case, we load StateObjectFactory in the first test run, and for that run the
instance of State that the Equinox types see is the same as those seen by StateObjectFactory. For
subsequent runs, Equinox types are loaded from the EFWCL and are not compatible with the types that dm
Server has previously loaded.

The simplest solution for us is to be able to clear the FrameworkProperties. A better solution for us is to
prevent the use of EFWCL.

Rob

--

-- 
Rob Harrop
SpringSource 

Registered in England & Wales - Registration Number 5187766
Registered Office: A2 Yeoman Gate, Yeoman Way, Worthing, West Sussex, BN13 3QZ, UK

This e-mail and any attachments transmitted with it are strictly confidential and intended solely for the
person or entity to whom they are addressed. Unauthorised use, copying, disclosure or distribution is
prohibited. If you receive this e-mail in error please notify the sender immediately and then delete it
along with any attachments. E-mails should be checked by the recipient to ensure that there are no viruses
and Interface21 does not accept any responsibility if this is not done. Any views or opinions presented
are solely those of the author and do not necessarily represent those of Interface21.

Re: ClassLoader incompatibilities due to EquinoxFWClassLoader

Equinox tagged for next I-Build