You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "James Strachan (JIRA)" <ji...@apache.org> on 2007/09/03 17:49:22 UTC
[jira] Commented: (CAMEL-134) add better logging - thats easy to
use - to trace the 'magic' in Camel such as auto-discovery of components &
type conversions
[ https://issues.apache.org/activemq/browse/CAMEL-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40057 ]
James Strachan commented on CAMEL-134:
--------------------------------------
I've added some debug logging to DefaultCamelContext and DefaultComponentResolver to provide debug logging of how components are resolved and to show which component creates endpoint URIs.
I wonder how this could be improved? I wonder if we should invent some logging names for the discovery of components / endpoints / type converters so its easy to watch the 'magic' via log4j config files?
> add better logging - thats easy to use - to trace the 'magic' in Camel such as auto-discovery of components & type conversions
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-134
> URL: https://issues.apache.org/activemq/browse/CAMEL-134
> Project: Apache Camel
> Issue Type: Improvement
> Reporter: James Strachan
> Assignee: James Strachan
> Fix For: 1.2.0
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.