The blueprint url naming context does not depend on ProxyManager so should not
be registered after it has become available.
---------------------------------------------------------------------------------------------------------------------------
Key: ARIES-520
URL: https://issues.apache.org/jira/browse/ARIES-520
Project: Aries
Issue Type: Bug
Components: JNDI
Affects Versions: 0.3
Reporter: Alasdair Nottingham
Assignee: Alasdair Nottingham
Fix For: 0.3
The blueprint url naming context is only registered when the ProxyManager
exists, but since the ProxyManager is not needed by it we can register it
earlier.
Since blueprint also depends on ProxyManager before registering the blueprint
context the url scheme still wont work, but you'll get a nicer error message
than you get when no url object factory is registered.
Also update the error message when the blueprint container service cannot be
found.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
