Norbet Reilly a écrit :
I understand where you are coming from and I have seen the debugging
output you mention (but didn't know how to quickly track down the
particular logger).
Yeah. It's easier when you actually have wrote the code :)
We have a proxy GUI which needs to display this information in a
window (and operates at the higher level of the provider), so having a
toString() is a much better solution for us. Also this particular case
it at odds with all the other *Impl.toString() methods (see also
http://issues.apache.org/jira/browse/DIRSERVER-585 which has a simple
bug).
Sure. That's also a valid concern. The point is that we have had two
different codecs and we decided to discord one of them. So we had to use
TwixTransformer to switch from one format to another. Too bad : twix has
toString() method for every kind of LdapMessage, but this is not the
case for the other encoder.
Merging both codec and both data structure (with toString() methods) is
already in our roadmap : https://issues.apache.org/jira/browse/DIRSERVER-176
At any rate, I'm sure this isn't the most important stuff you guys are
doing for RC1 and I have my own patches to use.
What you can do is to "import" the toString() method in
org.apache.directory.shared.ldap.codec.search.SearchRequest to have a
working trace. Be carefull that you may have to modify it a bit to work
in SearchMessageImpl.
I think we will improve debugging messages in RC2 or RC3. The pb is RC1.
It's a tought and bumpy road we are cruising actually;
