jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From anton_slutsky <aslut...@applevac.com>
Subject Re: NodeTypeRegistry.checkForReferencesInContent()
Date Wed, 07 Feb 2007 17:36:52 GMT

Alrighty.  Reworked the patch slightly and attached it with a whole lot of
comments to JCR-322.  Tried to move the thread to the dev forum, but it
barked at me and told me that I ask the impossible.  Oh well ....


Jukka Zitting wrote:
> 
> Hi,
> 
> On 2/7/07, anton_slutsky <aslutsky@applevac.com> wrote:
>> I agree, examining each node manually would be safer, but, like you said,
>> it
>> probably wont scale performancewise.
> 
> Perhaps we could extend the persistence manager interface to support
> something like this...
> 
>> Concurrency is an issue.  I was thinking on setting a semaphore or a
>> mutex
>> flag on the RepositoryImpl instance, but I was sure if it's possible to
>> have
>> two RepositoryImpl instances working on the same physical repository. 
>> From
>> what I've read so far, it doesnt appear that such a behavior is
>> supported.
>> If this can be confirmed to be a fact, the mutex solution should really
>> do
>> the trick.
> 
> Confirmed, your approach sounds good.
> 
>> Please pardon the ignorance, but what is an improvement request, and
>> where
>> can I file one? :-)
> 
> The Jackrabbit issue tracker is at
> http://issues.apache.org/jira/browse/JCR. You can file a new issue
> (improvement requests are one type of issues) once you've registered
> an account. See also http://issues.apache.org/jira/browse/JCR-322 for
> the full feature request related to this. If you want you can also
> attach your patch there.
> 
> BR,
> 
> Jukka Zitting
> 
> 

-- 
View this message in context: http://www.nabble.com/NodeTypeRegistry.checkForReferencesInContent%28%29-tf2882955.html#a8850220
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.


Mime
View raw message