You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2009/06/08 17:22:07 UTC

[jira] Resolved: (FELIX-906) Felix needs an RFC 126 EventHook

     [ https://issues.apache.org/jira/browse/FELIX-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard S. Hall resolved FELIX-906.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: felix-2.0.0
         Assignee: Richard S. Hall

Patches have been applied. Please close if satisfied, thanks.

> Felix needs an RFC 126 EventHook
> --------------------------------
>
>                 Key: FELIX-906
>                 URL: https://issues.apache.org/jira/browse/FELIX-906
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework, Specification compliance
>            Reporter: David Bosschaert
>            Assignee: Richard S. Hall
>             Fix For: felix-2.0.0
>
>
> RFC 126 defines an EventHook that Felix needs to implement.
> For more information see: http://www.osgi.org/download/osgi-4.2-early-draft2.pdf
> Note that in this document the hook is called 'PublishHook'. It has since been renamed to EventHook.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Re: [jira] Resolved: (FELIX-906) Felix needs an RFC 126 EventHook

Posted by João Ferreira <jt...@gmail.com>.
I was talking about build deps since bnd maven plugin does the bundle 
deps for me :)
I guess i will use the framework.

João Ferreira

Richard S. Hall wrote:
> On 6/8/09 2:09 PM, João Ferreira wrote:
>> Hello
>>
>> This feature from 4.2 is very nice for a work im doing where i 
>> altered the framework to filter returns from getService().
>> I was trying to try it but the EventHook is only is the framework 
>> module. Should it be in the core module?
>> I know there are different views about the usage of the core module, 
>> but i think its better to my project include a dependency on the core 
>> module rather than the framework module.
>> There are any problems if i use the framework as dependency?
>
> Depends on what you mean. If you are purely talking about in your 
> build dependencies, then it doesn't make a difference. The framework 
> will continue to include the service hook api because it needs it. I 
> should be switching to the new OSGi R4.2 class files soon, but Felix 
> will not release these JAR files in the future, so you cannot depend 
> on them from Felix, but we will likely do what we need to do to get 
> the official OSGi JARs into a maven repo someplace. So, for build 
> dependencies you will have some options.
>
> On the other hand, if you are talking about your bundle dependencies. 
> You should only be using Import-Package and then the question is moot.
>
> -> richard
>
>>
>> João Ferrreira
>>
>> Richard S. Hall (JIRA) wrote:
>>>      [ 
>>> https://issues.apache.org/jira/browse/FELIX-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel 
>>> ]
>>>
>>> Richard S. Hall resolved FELIX-906.
>>> -----------------------------------
>>>
>>>        Resolution: Fixed
>>>     Fix Version/s: felix-2.0.0
>>>          Assignee: Richard S. Hall
>>>
>>> Patches have been applied. Please close if satisfied, thanks.
>>>
>>>> Felix needs an RFC 126 EventHook
>>>> --------------------------------
>>>>
>>>>                 Key: FELIX-906
>>>>                 URL: https://issues.apache.org/jira/browse/FELIX-906
>>>>             Project: Felix
>>>>          Issue Type: Bug
>>>>          Components: Framework, Specification compliance
>>>>            Reporter: David Bosschaert
>>>>            Assignee: Richard S. Hall
>>>>             Fix For: felix-2.0.0
>>>>
>>>>
>>>> RFC 126 defines an EventHook that Felix needs to implement.
>>>> For more information see: 
>>>> http://www.osgi.org/download/osgi-4.2-early-draft2.pdf
>>>> Note that in this document the hook is called 'PublishHook'. It has 
>>>> since been renamed to EventHook.
>>>
>>


Re: [jira] Resolved: (FELIX-906) Felix needs an RFC 126 EventHook

Posted by "Richard S. Hall" <he...@ungoverned.org>.
On 6/8/09 2:09 PM, João Ferreira wrote:
> Hello
>
> This feature from 4.2 is very nice for a work im doing where i altered 
> the framework to filter returns from getService().
> I was trying to try it but the EventHook is only is the framework 
> module. Should it be in the core module?
> I know there are different views about the usage of the core module, 
> but i think its better to my project include a dependency on the core 
> module rather than the framework module.
> There are any problems if i use the framework as dependency?

Depends on what you mean. If you are purely talking about in your build 
dependencies, then it doesn't make a difference. The framework will 
continue to include the service hook api because it needs it. I should 
be switching to the new OSGi R4.2 class files soon, but Felix will not 
release these JAR files in the future, so you cannot depend on them from 
Felix, but we will likely do what we need to do to get the official OSGi 
JARs into a maven repo someplace. So, for build dependencies you will 
have some options.

On the other hand, if you are talking about your bundle dependencies. 
You should only be using Import-Package and then the question is moot.

-> richard

>
> João Ferrreira
>
> Richard S. Hall (JIRA) wrote:
>>      [ 
>> https://issues.apache.org/jira/browse/FELIX-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel 
>> ]
>>
>> Richard S. Hall resolved FELIX-906.
>> -----------------------------------
>>
>>        Resolution: Fixed
>>     Fix Version/s: felix-2.0.0
>>          Assignee: Richard S. Hall
>>
>> Patches have been applied. Please close if satisfied, thanks.
>>
>>> Felix needs an RFC 126 EventHook
>>> --------------------------------
>>>
>>>                 Key: FELIX-906
>>>                 URL: https://issues.apache.org/jira/browse/FELIX-906
>>>             Project: Felix
>>>          Issue Type: Bug
>>>          Components: Framework, Specification compliance
>>>            Reporter: David Bosschaert
>>>            Assignee: Richard S. Hall
>>>             Fix For: felix-2.0.0
>>>
>>>
>>> RFC 126 defines an EventHook that Felix needs to implement.
>>> For more information see: 
>>> http://www.osgi.org/download/osgi-4.2-early-draft2.pdf
>>> Note that in this document the hook is called 'PublishHook'. It has 
>>> since been renamed to EventHook.
>>
>

Re: [jira] Resolved: (FELIX-906) Felix needs an RFC 126 EventHook

Posted by João Ferreira <jt...@gmail.com>.
Hello

This feature from 4.2 is very nice for a work im doing where i altered 
the framework to filter returns from getService().
I was trying to try it but the EventHook is only is the framework 
module. Should it be in the core module?
I know there are different views about the usage of the core module, but 
i think its better to my project include a dependency on the core module 
rather than the framework module.
There are any problems if i use the framework as dependency?

João Ferrreira

Richard S. Hall (JIRA) wrote:
>      [ https://issues.apache.org/jira/browse/FELIX-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Richard S. Hall resolved FELIX-906.
> -----------------------------------
>
>        Resolution: Fixed
>     Fix Version/s: felix-2.0.0
>          Assignee: Richard S. Hall
>
> Patches have been applied. Please close if satisfied, thanks.
>
>   
>> Felix needs an RFC 126 EventHook
>> --------------------------------
>>
>>                 Key: FELIX-906
>>                 URL: https://issues.apache.org/jira/browse/FELIX-906
>>             Project: Felix
>>          Issue Type: Bug
>>          Components: Framework, Specification compliance
>>            Reporter: David Bosschaert
>>            Assignee: Richard S. Hall
>>             Fix For: felix-2.0.0
>>
>>
>> RFC 126 defines an EventHook that Felix needs to implement.
>> For more information see: http://www.osgi.org/download/osgi-4.2-early-draft2.pdf
>> Note that in this document the hook is called 'PublishHook'. It has since been renamed to EventHook.
>>     
>
>