On Wed, 26 Mar 2008, Hendrik wrote:
Eric Bodden wrote:
> 2. Can we take out the woven code from the rt.jar? (I personally think
> it's not possible due to the complexity of the involved tasks)
You you wish to identify the classes that were actually changed and
only extract those?
Y
Eric Bodden wrote:
1. Does AspectJ provide a native/straightforward solution for weaving
into rt.jar or is it some kind of a workaround?
It's a workaround.
2. Can we take out the woven code from the rt.jar? (I personally think
it's not possible due to the complexity of the involve
> 1. Does AspectJ provide a native/straightforward solution for weaving
> into rt.jar or is it some kind of a workaround?
It's a workaround.
> 2. Can we take out the woven code from the rt.jar? (I personally think
> it's not possible due to the complexity of the involved tasks)
You you wish
Hi,
Thanks for the reply Eric.
At the moment I am just concerned with static weaving, e.g. inserting a
new constructor to classes. So I think rt.jar weaving should work for
me, but need to clarify some things first:
1. Does AspectJ provide a native/straightforward solution for weaving
into rt
Hello, Hendrik.
There may be "hacks" to get around this, but to my best knowledge,
ajc's load time weaver does share those limitations. I have heard of
people though who successfully wove into rt.jar statically. Whether
this works or not probably depends on what your aspect does, though.
Eric
On
Hi,
I just found out recently that in Java, a custom class loader cannot
load core Java classes, i.e. classes located in java.* -- an exception
will be thrown if we attempt to do this.
So, I was wondering whether the same limitation also applies to AspectJ?
For example, can inter-type declar
