[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[equinox-dev] dependent and registered buddy policies
- From: "Tom Huybrechts" <tom.huybrechts@xxxxxxxxx>
- Date: Sun, 23 Jul 2006 13:33:35 +0200
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=gPU0dwnPSuxcyN2f/5ZtQRiPosi6cKvxmZ+7TNRj3gCkgNOGUqjyU46XFb0hohjh6XL4ZyXVu1EcbJK2q26taHlVVkGdEPFRxP4FiYzGeYHVHuG9PP/jfLanM3QlY5KRf69tx6eRZJhwkO6hOqUHKaOTE5eHvhGzIaXBPn3QZx4=
I'm using a registered buddy policy to solve a deserialization issue.
I tried setting Eclipse-BuddyPolicy: registered in my org.jboss.client
plugin which will do the deserializing and Eclipse-RegisterBuddy:
org.jboss.client in the plugin that defines the serialized classes.
This did not work, and after diving into the source I found out why:
the RegisteredPolicy is a stricter version of DependentPolicy: it
delegates to plugins which are registered AND which have a direct
dependency on the other plugin.
From the RegisteredPolicy javadoc:
Registered policy is an implementation of a buddy policy. It is
responsible for looking up a class in the bundles (registrant) that
declare interest in the bundle that require the buddy loading. Note
that the registrants must have a direct dependency on the bundle
Why is the explicit dependency necessary ? And why is this not documented ?