You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Alasdair Nottingham (JIRA)" <ji...@apache.org> on 2010/12/21 10:48:00 UTC
[jira] Created: (ARIES-520) The blueprint url naming context does
not depend on ProxyManager so should not be registered after it has become
available.
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.
[jira] Resolved: (ARIES-520) The blueprint url naming context does
not depend on ProxyManager so should not be registered after it has become
available.
Posted by "Alasdair Nottingham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alasdair Nottingham resolved ARIES-520.
---------------------------------------
Resolution: Fixed
> 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.
[jira] Work started: (ARIES-520) The blueprint url naming context
does not depend on ProxyManager so should not be registered after it has
become available.
Posted by "Alasdair Nottingham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on ARIES-520 started by Alasdair Nottingham.
> 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.