firas mualla yahoo.com> writes:
>
> I have a large J2EE web application . From
> performance(speed & memory space) point of view
> what is the best scenario to use ?
> 1)Use one logger for each class ( this is a common
> practice but
> doon't you think that it is heap-consu
I have a large J2EE web application . From
performance(speed & memory space) point of view
what is the best scenario to use ?
1)Use one logger for each class ( this is a common
practice but
doon't you think that it is heap-consuming ).
2)Use one logger instance at
