[MarkLogic Dev General] Re: XCC logging and filehandlers

[Ron Hitchens]

Patrick,

    Can you provide the actual code you're using to do
this logger configuration.  If you're setting a Logger
instance with ContentSourceImpl.setDefaultLogger, then
I don't see how this could happen because the reference
is just stored and not modified at all.

    If you can provide the specifics of want you're doing
I may be able to see what's happening.

On Nov 14, 2007, at 11:17 AM, Patrick Force wrote:

> Hi Ron,
>
> Thanks for your help, but I actually found all of the properties  
> modification instructions already and still can't seem to solve one  
> part of what XCC appears to be overriding in logging.  Here's what  
> I've done and the issue that still exists:
>
> (1) created my own custom com.marklogic.xcc package with an empy  
> xcc.logging.properties file within (so no default properties will  
> be overwritten I think) -- this successfully reset the console  
> output format
> (2) I create a logger in a class and a log file handler to it
> (3) Set the XCC ContentSource
> (4) After setting the XCC ContentSource, it appears that my log  
> file handler is getting dropped and log output is no longer going  
> to the file
>
> Thanks,
> Patrick
>
> _______________________________________________
> General mailing list
> General at developer.marklogic.com
> http://xqzone.com/mailman/listinfo/general

---
Ron Hitchens {ron.hitchens at marklogic.com}  650-655-2351




-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2435 bytes
Desc: not available
Url : http://xqzone.marklogic.com/pipermail/general/attachments/20071114/f2548e85/smime.bin