[ https://issues.jboss.org/browse/AS7-1656?page=com.atlassian.jira.plugin.s... ] Paul Ferraro commented on AS7-1656: ----------------------------------- I'm not sure this is really a problem. There are several mechanisms to demand the jndi binding, @Resource injection, <resource-ref>, etc. What I'd hate to lose is the coupling of the jndi resource to the application lifecycle. One solution would be to introduce an additional start-mode for infinispan caches that distinguishes between LAZY and ON_DEMAND. LAZY could install the binder service using ACTIVE mode, where the cache container gets started lazily, while ON_DEMAND would preserve the current behavior. This way, if some application needs to perform a jndi lookup without a mechanism for demanding the binding to start, there is a configuration option that supports this without having to resort to eagerly starting a cache. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1656?page=com.atlassian.jira.plugin.s... ] James Perkins commented on AS7-1656: ------------------------------------ It came up on an IRC pm I was having. Here is what we have: Infinispan config: http://pastebin.com/k1EKmNwn Stack trace: http://pastebin.com/HFmdNyc4 Talked about it yesterday with Stuart and he saw something about it loading ON_DEMAND. We thought that could be the problem as maybe JNDI binding hadn't been started yet. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1656?page=com.atlassian.jira.plugin.s... ] Jason Greene updated AS7-1656: ------------------------------ Fix Version/s: 7.1.0.Beta1 (was: 7.0.2.Final) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1656?page=com.atlassian.jira.plugin.s... ] Jason Greene updated AS7-1656: ------------------------------ Moving all non-critical issues to the CR. If you finish it before we release beta please correct the fix-for version. Thanks -- 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

[ https://issues.jboss.org/browse/AS7-1656?page=com.atlassian.jira.plugin.s... ] 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. -- 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