Werner,
Thanks for your help. The problem was I did not know how to configure
commons logging. Castor devs might want to make this more clear in their
documentation.

Thanks again.


-----Original Message-----
From: Werner Guttmann [mailto:[email protected]] 
Sent: Wednesday, June 03, 2009 11:50 PM
To: [email protected]
Subject: Re: [castor-user] Debug Messages

Dan,

let me try a bit more precise. Castor has been around for more than 10
years, and parts of its code base is .. well, old. There might still be
areas where a sysout is used or similar.

For other parts of Castor we have switched to using commons-logging to
interface to any logging package available. Internally, we are using
log4j (during e.g. test execution, but of course commons-logging knows
thow to interface with Java logging.

Dan Moore (danielmo) wrote:
> Actually, I misinterpreted this.

> We're using java logging to capture all
> stdout output, which is why changing the logging settings changes
castor
> output. 
I am sure that Java logging (similar to log4j) allows you to selectively
disable all output for Castor, i.e. all org.castor* and
org.exolab.castor* packages. In other words, this is a problem of
configuring the logging system you are using. Does this make sense ?

> Is there a way to suppress Castor output itself?
> 
> All that I have found has been this line:
> #
> org.exolab.castor.debug=false
> in castor.core.properties, but as you can see, they're all set to
false.
> Is there any other place this could be affecting debug output?
For the old code, this is the property to use to disable output.

> Thanks,
> Dan Moore
> 
> -----Original Message-----
> From: Dan Moore (danielmo) 
> Sent: Friday, May 29, 2009 11:17 AM
> To: [email protected]
> Subject: RE: [castor-user] Debug Messages
> 
> Sorry I wasn't clear,
> I'm using castor as a Maven dependency (castor-core-1.3.jar). I'm not
> using log4j, but just java logging.
> 
> That was the issue though, the logging.properties pointed me in the
> right direction.
> Thanks for your help, as the reference to logging got me there.
> Cheers,
> Dan Moore
> 
> -----Original Message-----
> From: Werner Guttmann [mailto:[email protected]] 
> Sent: Friday, May 29, 2009 10:41 AM
> To: [email protected]
> Subject: Re: [castor-user] Debug Messages
> 
> Hi,
> 
> are you using a logging package such as log4j ? If so, please set
yopur
> log level to e.g. warning.
> 
> Werner
> 
> Dan Moore (danielmo) wrote:
>> List,
>> I'm having issues trying to hide debug messages that are being
printed
>> in Castor. All the .properties files are turned off, but the messages
>> are still spewing out when parsing XML files. Here is a trace of some
> of
>> the messages.
>>
>> Is there another way to configure this or something else I can do
>> besides manually removing and rebuilding the source?
>>
>>
>> May 29, 2009 10:07:25 AM
>> org.exolab.castor.xml.util.resolvers.AbstractResolverPackageCommand
>> resolveFINE: Now in resolve method:
>> org.exolab.castor.xml.util.resolvers.ByPackageMapping resolving:
>> com.cisco.test.tea.core.testbed
>> May 29, 2009 10:07:25 AM
>>
>
org.exolab.castor.xml.util.XMLClassDescriptorResolverImpl$DescriptorCach
>> eImpl addAllDescriptorsFINE: Called addAllDescriptors with null or
> empty
>> descriptor map
>> May 29, 2009 10:07:25 AM
>>
>
org.exolab.castor.xml.util.XMLClassDescriptorResolverImpl$DescriptorCach
>> eImpl getDescriptorFINE: Get descriptor for:
>> com.cisco.test.tea.core.testbed.Driver found: null
>> May 29, 2009 10:07:25 AM
>> org.exolab.castor.xml.util.resolvers.AbstractResolverClassCommand
>> resolveFINE: Now in method:
>> org.exolab.castor.xml.util.resolvers.ByDescriptorClass resolving:
>> com.cisco.test.tea.core.testbed.Driver
>> May 29, 2009 10:07:25 AM
>> org.exolab.castor.xml.util.resolvers.ResolveHelpers loadClassFINE:
>> Ignored problem at loading class:
>> com.cisco.test.tea.core.testbed.DriverDescriptor through class
loader:
>> sun.misc.launcher$appclassloa...@1ba34f2, exception:
>> java.lang.ClassNotFoundException:
>> com.cisco.test.tea.core.testbed.DriverDescriptor
>> May 29, 2009 10:07:25 AM
>> org.exolab.castor.xml.util.resolvers.ResolveHelpers loadClassFINE:
>> Ignored problem at loading class:
>> com.cisco.test.tea.core.testbed.descriptors.DriverDescriptor through
>> class loader: sun.misc.launcher$appclassloa...@1ba34f2, exception:
>> java.lang.ClassNotFoundException:
>> com.cisco.test.tea.core.testbed.descriptors.DriverDescriptor
>> May 29, 2009 10:07:25 AM
>>
>
org.exolab.castor.xml.util.XMLClassDescriptorResolverImpl$DescriptorCach
>> eImpl addAllDescriptorsFINE: Called addAllDescriptors with null or
> empty
>> descriptor map
>> May 29, 2009 10:07:25 AM
>>
>
org.exolab.castor.xml.util.XMLClassDescriptorResolverImpl$DescriptorCach
>> eImpl getDescriptorFINE: Get descriptor for:
>> com.cisco.test.tea.core.testbed.Driver found: null
>> May 29, 2009 10:07:25 AM
>> org.exolab.castor.xml.util.resolvers.AbstractResolverClassCommand
>> resolveFINE: Now in method:
>> org.exolab.castor.xml.util.resolvers.ByIntrospection resolving:
>> com.cisco.test.tea.core.testbed.Driver
>> May 29, 2009 10:07:25 AM
>> org.exolab.castor.xml.util.resolvers.ResolveHelpers loadClassFINE:
>> Ignored problem at loading class:
> com.cisco.test.tea.core.testbed.Driver
>> through class loader: sun.misc.launcher$appclassloa...@1ba34f2,
>> exception: java.lang.ClassNotFoundException:
>> com.cisco.test.tea.core.testbed.Driver
>> May 29, 2009 10:07:25 AM
>>
>
org.exolab.castor.xml.util.XMLClassDescriptorResolverImpl$DescriptorCach
>> eImpl addAllDescriptorsFINE: Called addAllDescriptors with null or
> empty
>> descriptor map
>> May 29, 2009 10:07:25 AM
>>
>
org.exolab.castor.xml.util.XMLClassDescriptorResolverImpl$DescriptorCach
>> eImpl getDescriptorFINE: Get descriptor for:
>> com.cisco.test.tea.core.testbed.Driver found: null
>> May 29, 2009 10:07:25 AM
>>
>
org.exolab.castor.xml.util.XMLClassDescriptorResolverImpl$DescriptorCach
>> eImpl addDescriptorFINE: Adding class name to missing classes:
>> com.cisco.test.tea.core.testbed.Driver
>> May 29, 2009 10:07:25 AM org.exolab.castor.xml.UnmarshalHandler
>> endElementFINEST: #endElement: driver
>> May 29, 2009 10:07:25 AM org.exolab.castor.xml.UnmarshalHandler
>> charactersFINEST: #characters:
>>
>>
>> Thanks,
>> Dan Moore
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>     http://xircles.codehaus.org/manage_email
>>
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>     http://xircles.codehaus.org/manage_email
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>     http://xircles.codehaus.org/manage_email
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
> 
>     http://xircles.codehaus.org/manage_email
> 
> 

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to