ICapability extends IApplication and CapabilityInstance extends ApplicationInstance
ICapability extends IApplication and CapabilityInstance extends ApplicationInstance
AbstractInstance manages dependencies on IApplication(s)

instead of on ICapability.

TODO: Update BindingManagement to manage depenedncies as expected.
BindingManagement resolves and unresolves dependencies in all applications (capabilities included).

Now applications may depend on other applications, despite the fact of being capabilities or not.
Delay call to onDependenciesResolved.
Merge branch 'feature/depending-on-apps' into feature/capabilities-are-apps
Refactor CapabilityInstance. Move service related methods to protected ones.
Move services from CapabilityInstance to ApplicationInstance.

ApplicationInstance(s) are holding services and responsible for providing the service proxy used in injection.

TODO: Missing a way to trigger service init in ApplicationInstance.
ApplicationInstances init/cancel services when resolved/unresolved.

BindingManagement triggers service initialization when the ApplicationInstance is resoldev.
It triggers service cancelation when ApplicationInstance gets unresolved.

CapabilityInstances follow the same behaviour.
Services in CapabilityInstances are no longer initialized when the instance is bound, but when it gets resolved.
Services in CapabilityInstances are no longer cancelled when the instance is unbound, but when it gets unresolved.
Avoid creating services and proxy for applications without interfaces extending IApplication.

Notice that methods declared in the application, but not explicitely defined in a separate interface extending IApplication, will not be exposed as services.
Therefore, applications directly implementing IApplication but no other interface will have no services.
BindingManagement reacts to resource creation/removal calling IResourceManagementListener methods.

- IResourceManagemeentListener methods updated, new parameter ICapability added.
- ResourceMonitoringFilter getParameters has been updated to prepare parameters for IResourceManagemeentListener methods.
- BindingManagement registers IResourceManagemeentListener methods with ResourceMonitoringFilter.
- BindingManagement IResourceManagemeentListener implementation updated.
Implement lookup by ICapabiity in the tree.
Remove IInternalResourceManagementListener.

Methods there are no longer required.
They are now replaced by IResourceManagementListener methods.
Test BindingManagement reacts to services coming and going.

resourceAdded method is executed when a service annotated with AddsResource is executed.
resourceRemoved method is executed when a service annotated with RemovesResource is executed.
Merge branch 'master' into feature/binding-management-notified-when-resource-is-added-removed
Merge pull request #27 from logoff/master

Bug fix: BundleTree notifications and filters
Merge branch 'master' into feature/binding-management-notified-when-resource-is-added-removed
Fix merge with master.
Merge pull request #28 from isartcanyameres/feature/binding-management-notified-when-resource-is-added-removed

Feature/binding management notified when resource is added removed
Add a Collection of Endpoint's and toString method.