|
Re: Logging: msg#00032network.samba.java
On Tue, 15 Nov 2005 12:50:07 +0300 Maxim Gordienko <mgordienko@xxxxxxxxx> wrote: > Hello, Mike! > Excuse me for my insolent opinion, but current logging is not fine. > Transport1 floods log with messages with no way to silence it, > System.out.println is used. That's because there are some System.out.println's left over from some debugging in the last release. We'll take them out in the next release. > Besides, using custom LogStream force developer to decide log or not > some event, instead of delegating this decision to log system. Well I don't know why you would care about logging inside jCIFS but this isn't really true. See the jcifs.util.loglevel property. Mike |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | jcifs + weblogic has java.net.ConnectException: Connection timed out: connect: 00032, Zhang, Victor |
|---|---|
| Next by Date: | Re: Connection timeout, then the transport stays "in error": 00032, Michael B Allen |
| Previous by Thread: | Re: Loggingi: 00032, Maxim Gordienko |
| Next by Thread: | Re: Logging: 00032, Maxim Gordienko |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |