Hi On Tue, Oct 31, 2023, at 23:23, Matt Sicker wrote: > I’m not sure how much people use this deployment model anymore, but > JNDI was and still is at the core of JavaEE (now JakartaEE) dependency > injection APIs. While CDI is the current way of using dependency > injection there, CDI is compatible with JNDI and the other JavaEE tech > that came in between (the resource loader API thing). Typically, a > JavaEE application server (think like JBoss/Wildfly, WebSphere, > Weblogic, etc.) would be configured with shared resources like database > and JMS connection pools, and those would be obtainable via JNDI. A > single application server could host multiple servlets or more advanced > packaging formats. All this JNDI usage, however, relies on the Java > provider, not the LDAP or DNS or similar providers, so it works without > networking being involved. > > Do note, though, that there are ways to use this same tech without > JNDI, but that typically involves being part of some JavaEE lifecycle, > using CDI for dependency injection, etc.
Yes, I am aware of that, being a JNDI user myself back in the days. My question is not general about JNDI, but why is it necessary in the context of Logging? Piotr already mentioned JMS connections, so is this the only thing or am I missing something else?
