But JCL isn't a logging implementation...

Originally Posted by
jbetancourt
I vote for removing JCL use in Spring. Perhaps Spring should eat its own dog food and have the logging implementation injected into it.

JCL is an abstraction layer, not an implementation. The sole purpose of JCL is to decouple your app from any specific logging implementation. So by using JCL, Spring is already eating its own dog food. Or would you have Spring reinvent the wheel by providing its own logging abstraction layer?
Andrew
Andrew Swan
"Now is the EJB of our discontent made glorious Spring"