[jboss-jira] [JBoss JIRA] (AS7-1656) Binder services should not be ON_DEMAND

[Paul Ferraro (Issue Comment Edited) (JIRA)]

    [ https://issues.jboss.org/browse/AS7-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654729#comment-12654729 ] 

Paul Ferraro edited comment on AS7-1656 at 1/9/12 4:30 PM:
-----------------------------------------------------------

This is not really an issue anymore.  Cache instances are now bound to jndi, as well as cache containers.  A cache can be configured to start eagerly, in which case, it's jndi binding is also eager.
                
      was (Author: pferraro):
    This is really an issue anymore.  Cache instances are now bound to jndi, as well as cache containers.  A cache can be configured to start eagerly, in which case, it's jndi binding is also eager.
                  
> Binder services should not be ON_DEMAND
> ---------------------------------------
>
>                 Key: AS7-1656
>                 URL: https://issues.jboss.org/browse/AS7-1656
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 7.0.1.Final
>            Reporter: Stuart Douglas
>            Assignee: Paul Ferraro
>             Fix For: 7.1.0.Final
>
>
> IF a binder service is registered as ON_DEMAND then the item will not be available for lookup in JNDI until something as expressed a dependency on it. This means that it will work for resource injection, however will fail for manual JNDI lookups. 
> If lazy startup is required the binder service should use a ManagedReferenceFactory that starts the lazy service and blocks until the lazy service is available. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira