[wildfly-dev] JNDI and java:comp, slimming the server, and componentless naming contexts

[Jason Greene]

+ 1

On Feb 4, 2014, at 7:57 AM, Stuart Douglas <stuart.w.douglas at gmail.com> wrote:

> Sounds good to me.
> 
> Stuart
> 
> 
> On Tue, Feb 4, 2014 at 3:39 PM, David M. Lloyd <david.lloyd at redhat.com> wrote:
> I think we need to look into a small redesign of how we handle
> java:comp, java:module, and java:app.  The reasoning comes in three parts:
> 
> * Various specs require that certain names be bound globally across all
> of java:comp.
> * Various other specs implicitly expect to be able to query these
> globally bound names even if there is no actual component context.
> * Duplicating these bindings uses more resources than are necessary.
> 
> Therefore I think we need to make a small change - we should have a
> "global" version of the three context-specific namespaces that act as a
> sort of fallback if there's no (component|module|app)-specific name
> bound at a location.  This allows us to do a few things:
> 
> * Satisfy the spec issues
> * Reduce resource overhead
> * Allow globally-configured things in the management config to bind to
> component/module/app-specific namespaces
> 
> Thoughts?
> --
> - DML
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
> 
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev

--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat