Hey all,

A question on checkGreedyReferences() in the new osgicheck-maven-plugin, we got 
a lot of warnings about our static @Reference's needing to be greedy.

From the `ReferecePolicy.STATIC` java doc:

> If a target service is available to replace the bound service which became 
> unavailable, the component configuration must be reactivated and bound to the 
> replacement service.

Would this imply that regardless of the RELUCTANT/GREEDY setting, for a static 
@Reference I should see the new/updated service - and if so, should the warning 
only trigger for non static references?

Mark


---
"The ease with which a change can be implemented has no relevance at all to 
whether it is the right change for the (Java) Platform for all time." — 
Mark Reinhold.

**Mark Derricutt** | Senior Developer
**Phone**: +64 9 302 0515 Fax: +64 9 302 0518
**Mobile**: +64 21 562 533 Freephone: 0800 SMX SMX (769 769)
**Twitter**: @talios
**SMX Limited**: Level 10, 19 Victoria Street West, Auckland, New Zealand
**Web**: http://smxemail.com

![Cloud Email Hosting & Security](http://smxemail.com/images/smxsig.png)

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to