JPMS is something to work _around_, not _with_ IMO.
Gary
On Thu, Nov 2, 2023, 12:25 AM Christian Grobmeier wrote:
>
>
> On Thu, Nov 2, 2023, at 02:12, Ralph Goers wrote:
> > Christian, I was at least 3 years ahead of you on this one.This is
>
> Sorry I was not active for a while. Good you were
On Thu, Nov 2, 2023, at 08:53, Ralph Goers wrote:
>> On Nov 1, 2023, at 9:24 PM, Christian Grobmeier wrote:
>>
>>
>>
>> On Thu, Nov 2, 2023, at 02:12, Ralph Goers wrote:
>>> Christian, I was at least 3 years ahead of you on this one.This is
>>
>> Sorry I was not active for a while. Good
> On Nov 1, 2023, at 9:24 PM, Christian Grobmeier wrote:
>
>
>
> On Thu, Nov 2, 2023, at 02:12, Ralph Goers wrote:
>> Christian, I was at least 3 years ahead of you on this one.This is
>
> Sorry I was not active for a while. Good you were here.
>
>> precisely why in 3.x we extracted a
On Thu, Nov 2, 2023, at 02:12, Ralph Goers wrote:
> Christian, I was at least 3 years ahead of you on this one.This is
Sorry I was not active for a while. Good you were here.
> precisely why in 3.x we extracted a LOT of stuff from log4j-core into
> their own modules.
Why not 2.x?
> To
Christian, I was at least 3 years ahead of you on this one.This is precisely
why in 3.x we extracted a LOT of stuff from log4j-core into their own modules.
To be honest the main driver was JPMS - our goal for 3.x Is for log4j-core to
only have a hard dependency on java.base and as few optional
> On Nov 1, 2023, at 2:22 PM, Christian Grobmeier wrote:
>
> We should not underestimate the impact log4shell had. Jndi was at the epi
> center. Us, providing a giant jar including so much stuff with potential
> security holes don’t do us a favor.
This is exactly why in 3.x, the main branch,
As some might know, I am writing a book and the publisher gathers a lot of
feedback. Also I talk to many people in my classrooms and also to many pros at
my clients side.
What I hear is usually:
- is log4j really secure?
- can’t I disable certain features?
- are you sure you get jndi right this
I don’t see any reason why we shouldn’t publish the JNDI support in its own
module as we’re planning in main already. Whether we eventually split out
anything from the main repo is another story, but in 3.x, JNDI, like most of
the optional features, will require downloading additional
If you want separate logging config files in an EJB environment using JNDI is
pretty much required. The same would be true for any properties needed in the
configuration.
In any case, despite Piotr saying this is a majority vote, it is not. I will
veto any attempt to remove JNDI components
On Wed, Nov 1, 2023, at 00:01, Ralph Goers wrote:
> There is a difference between a JEE application that only uses servlets
> vs one that uses EJBs. At a former employer we often used JBoss to run
> servlets even though we had no EJBs. In an environment with EJBs I am
> not sure how you can
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
There is a difference between a JEE application that only uses servlets vs one
that uses EJBs. At a former employer we often used JBoss to run servlets even
though we had no EJBs. In an environment with EJBs I am not sure how you can
distinguish the various components from each other without
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
Piotr, I think it is important to differentiate what is a requirement and
what is just another way of achieving something. My employer has several
Tomcat- and JBoss-based JEE applications (using Log4j) and we don't have a
single JNDI usage I know of.
I would like to hear "the functional need"
Hi Christian,
On Tue, 31 Oct 2023 at 21:57, Christian Grobmeier wrote:
> I am surprised we still have JNDI in the code at all, but this made me
> curious:
> why do JEE users need JNDI features for logging? Why can't they just use the
> normal log mechanism?
JNDI is basically a bean
15 matches
Mail list logo
