You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Jeff Faath (JIRA)" <ju...@ws.apache.org> on 2009/05/21 19:51:45 UTC
[jira] Closed: (JUDDI-177) Adding debug level logging
[ https://issues.apache.org/jira/browse/JUDDI-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Faath closed JUDDI-177.
----------------------------
Resolution: Fixed
Each query inherits EntityQuery and flows through the "getQueryResult" method. This method has a debug line that prints the query out nicely.
> Adding debug level logging
> --------------------------
>
> Key: JUDDI-177
> URL: https://issues.apache.org/jira/browse/JUDDI-177
> Project: jUDDI
> Issue Type: Task
> Affects Versions: 3.0alpha
> Reporter: Kurt T Stam
> Assignee: Jeff Faath
> Fix For: 3.0beta
>
>
> Jeff, in lots of classes the logger is not even used. Can you make a pass and add some DEBUG level logging? Especially the Finder classes have very little logging. The same actually holds for javadoc.
> Look for TODO- JUDDI-177 in the code for some code review comments.
> This org.apache.juddi.query package has no unittests. I think this code is in dire need of tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.