Thanks Gary. At least, there is the aforementioned ProtocolCommandListener which makes it easy to add the feature. Sure, it would be more efficient to just put those 10 lines of code required to log ProtocolCommandEvents directly in the [net] code, so one just needs to specify the DEBUG level in the logging configuration file
2012/8/15 Gary Gregory <[email protected]> > AFAIK, there is no logging in [net]. > > You can create a JIRA for requesting the feature. > > This will be followed by the usual debate as to which logging API to use ;) > > Gary > > On Wed, Aug 15, 2012 at 10:01 AM, Raffaele Sgarro > <[email protected]>wrote: > > > I was looking for a way to enable verbose logging for commons-net > > (specifically, I'm using the FTP library), but I can't find anything > > online, and a quick tour of the sources didn't help me. Can anybody tell > me > > if such an option exist? For example, with Apache HTTP client one can > > easily examine all the raw socket communication just by setting the log > > level to DEBUG and configuring an appender. > > > > It would be better if commons-net had this feature, instead of cluttering > > client code with endless series of System.out.println(replyText) > > > > > > -- > E-Mail: [email protected] | [email protected] > JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0 > Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory >
