* sight *

It is really disappointing:

svn update

[lots of output]


grep -r printStackTrace ..... | awk .... | wc -l
   44

Now every time I have to merge my changes, because Vaadin guys are using SVN instead of Mercurial (or any other DVCS) and does not wants spend 1 hour to remove these
nasty-nasty-nasty
printStackTrace statements. :frowning:

Hi,

I second this. One should not use printStackTrace. A sorrow logger or - even better - a log facade such as slf4j should be used!

Greetings
Peer

Hi,

I agree with both of you that printStackTrace really should not be used and improvement of the logging in Vaadin is included in the plans for Vaadin7. Exactly how it will be done is not clear at this point in time but using something like slf4j does not sound like a bad idea.

Yeah, I just recently killed that “not bad idea” from EJP project which I forked (an ORM, that is very small, but just works without any XML/annotations with a plain POJOs). I think for now, a standard Java logger is just as fine for Vaadin and probably will be just fine for a quite a while. :slight_smile:

Seriously, I think you, guys, can try to understand us, who really cursing life on production because of this. I really would like to look at your Liferay’s logs! :slight_smile: Still got a space on a server?.. Please kill just one little hour of working time and carefully remove all that nasty things, replaced with a standard logger and spit to the log
only in case of debug mode
, which is already defined in Vaadin web.xml, right? :slight_smile: There only 44 places where to replace, where only like 5 are the most nasty. For me it would take just ~30 minutes to implement. Why wait till Vaadin 7, which will much later from now?

Then you, guys, can think about rocket-science, while all the rest of the world just as fine and then replace this with something you think is better (although I still doubt the World needs something else than just a standard Java logger).

Thanks for understanding!

Hi Bo!

I’m happy to tell you that I just pushed a server-side logging solution (using java.util.logging) to our SVN. It’ll be included in Vaadin 6.5.0.

See
#5715
for more information.

HTH,
/Jonatan

Yeeehaaaa!! :grin:
Many thanks, Jonatan!

Also I am
very
happy Vaadin is not using anything like log4j or any other strange logger. For Vaadin standard Java logger is more than enough.