That is really pity, but nevertheless thx for your help. The implementation is 
the only problem. I already found out that you added code for `WeavingHooks` in 
the framework code ;) So if I have the implementation the rest will be easy 
hopefully ^^

-Christian

----- Original Message -----
From: [email protected]
To: [email protected]
Date: 09.07.2012 18:07:29
Subject: Re: AOP in Apache Felix


> On 7/9/12 11:56 , [email protected] wrote:
>> Hi Richard,
>> 
>> I already had a look to the `WeaverHook` interface, but I did not find any 
>> good example how to implement it. Do you have any sources?
> 
> Not really. Just google it. The spec has an example in it. If you are 
> looking for help with doing the byte code manipulation, then you're on 
> your own there...
> 
> Implementing the hook is fairly straightforward, though. Just implement 
> a weaving hook and register it as a service and then it will be called 
> by the framework to give you a chance to manipulate the class bytes.
> 
> -> richard
> 
>> 
>> Greetings.
>> Christian
>> 
>> ----- Original Message -----
>> From: [email protected]
>> To: [email protected]
>> Date: 09.07.2012 16:12:13
>> Subject: Re: AOP in Apache Felix
>> 
>> 
>>> On 7/9/12 9:20 AM, [email protected] wrote:
>>>> Hi guys,
>>>> 
>>>> Currently I'm trying to add AOP support to my Felix OSGi environment. 
>>>> After some research I came up with following possibilities:
>>>> 
>>>> * using dynamic proxies (Spring AOP or DependencyManager)
>>>> * Equinox Weaving (but does not work in Apache Felix)
>>>> 
>>>> All the above solutions doesnt suit my use case. I need aspects which 
>>>> weaves in terms of special annotations. I do not want to know the service 
>>>> interfaces which could be implemented by a proxy like the 
>>>> DependencyManager is doing. Is there any possibility to add "real" AOP 
>>>> support to my project?
>>>> 
>>>> Underlying development will be done by Bnd(tools), maybe it could be 
>>>> relevant :)
>>> Check the weaving hook section in the R4.3 or R5 OSGi core spec.
>>> 
>>> -> richard
>>> 
>>>> Greetings.
>>>> Christian
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [email protected]
>>>> For additional commands, e-mail: [email protected]
>>>> 
>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to