-----Original Message-----
From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
To: "[email protected]" <[email protected]>
Sent: 12/7/2007 3:05 PM
Subject: General Digest, Vol 42, Issue 4
Send General mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://xqzone.com/mailman/listinfo/general
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of General digest..."
Today's Topics:
1. RE: Re: XCC logging and filehandlers (Fagan, Mike)
2. limiting documents to search (Paul M)
3. Re: limiting documents to search (Michael Blakeley)
----------------------------------------------------------------------
Message: 1
Date: Thu, 6 Dec 2007 15:48:22 -0500
From: "Fagan, Mike" <[EMAIL PROTECTED]>
Subject: RE: [MarkLogic Dev General] Re: XCC logging and filehandlers
To: "General Mark Logic Developer Discussion"
<[email protected]>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
I am having a similar problem when initializing XCC ContentSource. Its
high-jacking my logger for my app and the weblogic server. Is there an
easy way to disable the XCC logger from redirecting my server and
application log messages?
Regards,
Mike Fagan
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ron
Hitchens
Sent: Wednesday, November 14, 2007 4:50 PM
To: General Mark Logic Developer Discussion
Subject: Re: [MarkLogic Dev General] Re: XCC logging and filehandlers
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
> [email protected]
> http://xqzone.com/mailman/listinfo/general
---
Ron Hitchens [EMAIL PROTECTED] 650-655-2351
------------------------------
Message: 2
Date: Fri, 7 Dec 2007 05:04:44 +0800 (CST)
From: Paul M <[EMAIL PROTECTED]>
Subject: [MarkLogic Dev General] limiting documents to search
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
This goes back to limiting searches.
I have the following:
Two documents
doc1prod.xml has the following: role/permission => proddocs, read
doc2test.xml has the following role/permission =>testdocs, readfull path of
doc1prod.xml => prod/doc1.xml
doc2test.xml => test/doc2.xml
User: superuser
has roles proddocs and testdocs assigned
Now I do a cts:search(fn:doc() ...
Both documents doc1 and doc2 will be returned.
However, if I construct query similar to the following:
cts:search(fn:doc(),
cts:and-query((query),
cts:directory-query(("/prod/"), "1") ) ) )
I should only get doc1prod.xml. But what is the performance hit in general.
i.e. +5% +10% +20% when limiting by directory? Would searching within a
collection be -noticeable faster than searching by specifying directory? (I am
trying to avoid collection, more permissions and roles would be required.)
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://xqzone.marklogic.com/pipermail/general/attachments/20071207/4f0b1c0d/attachment-0001.html
------------------------------
Message: 3
Date: Thu, 06 Dec 2007 13:21:29 -0800
From: Michael Blakeley <[EMAIL PROTECTED]>
Subject: Re: [MarkLogic Dev General] limiting documents to search
To: General Mark Logic Developer Discussion
<[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="utf-8"
Paul,
Directories and collections are both indexed in much the same way, and
perform similarly.
-- Mike
Paul M wrote:
> This goes back to limiting searches.
>
> I have the following:
> Two documents
> doc1prod.xml has the following: role/permission => proddocs, read
> doc2test.xml has the following role/permission =>testdocs, readfull path of
> doc1prod.xml => prod/doc1.xml
> doc2test.xml => test/doc2.xml
>
> User: superuser
> has roles proddocs and testdocs assigned
>
> Now I do a cts:search(fn:doc() ...
> Both documents doc1 and doc2 will be returned.
>
> However, if I construct query similar to the following:
> cts:search(fn:doc(),
> cts:and-query((query),
> cts:directory-query(("/prod/"), "1") ) ) )
> I should only get doc1prod.xml. But what is the performance hit in general.
> i.e. +5% +10% +20% when limiting by directory? Would searching within a
> collection be -noticeable faster than searching by specifying directory? (I
> am trying to avoid collection, more permissions and roles would be required.)
>
>
>
>
>
>
>
>
>
>
> ____________________________________________________________________________________
> Be a better friend, newshound, and
> know-it-all with Yahoo! Mobile. Try it now.
> http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> General mailing list
> [email protected]
> http://xqzone.com/mailman/listinfo/general
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4532 bytes
Desc: S/MIME Cryptographic Signature
Url :
http://xqzone.marklogic.com/pipermail/general/attachments/20071206/87d90855/smime-0001.bin
------------------------------
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general
End of General Digest, Vol 42, Issue 4
**************************************
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general
