[
https://issues.apache.org/jira/browse/ARIES-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Ross closed ARIES-1354.
----------------------------
Resolution: Duplicate
Assignee: John Ross
Alexandre, I think this is the same thing as in ARIES-1360? Please reopen if
not. For the sake of clarity, I'll summarize some of the discussion from there.
>From the description, it sounds like you are registering the content handler
>service in the root region. So when you install a subsystem requiring that
>content handler into the root subsystem, it works because the parent
>subsystem's context is used to do the service lookup. When you then add
>another subsystem in between the root subsystem and the one requiring the
>service, that new subsystem becomes the parent and needs to import the content
>handler from the root subsystem. Alternatively, you could register the service
>within the new subsystem (or by using that subsystem's bundle context
>directly) rather than at (or in additional to) the root level. The subsystem
>containing the content to be processed by the content handler should not
>require the import.
> Subsystem ContentHandler instances are not called in a child subsystem
> ----------------------------------------------------------------------
>
> Key: ARIES-1354
> URL: https://issues.apache.org/jira/browse/ARIES-1354
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
> Affects Versions: subsystem-2.0.2
> Reporter: Alexandre Roman
> Assignee: John Ross
>
> I have a subsystem embedding a custom resource. This resource is handled by a
> custom ContentHandler implementation.
> This resource is correctly handled if I install this subsystem as a child of
> the root subsystem (my ContentHandler is called).
> However, if the same subsystem is embedded in a bigger subsystem, the
> resource is not handled, while the subsystem is successfully installed and
> started.
> No errors found in logs (DEBUG level).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
