jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Angela Schreiber <anch...@adobe.com>
Subject Re: Some more benchmarks
Date Tue, 02 Apr 2013 11:41:49 GMT
oh... already fixed it before lunch and committed modifications
before re-checking mails (using OAK-690 and an appropriate comment).

thanks anyway... test passed and i assume it's fine. the internal method 
AuthorizableImpl#getTree will now return the Tree associated
with the authorizable as long it has not been disconneted and
throw IllegalStateException otherwise to avoid odd behavior.


On 4/2/13 12:46 PM, Michael Dürig wrote:
> On 28.3.13 15:19, Angela Schreiber wrote:
>> hi michael
>>> With the resolution of OAK-690, I made tree instances stable across save
>>> and refresh operations.
>> does that mean that the AuthorizableImpl could hold a Tree instance
>> instead of re-accessing it over and over again using a lookup by id?
>> if that was the case, could you please create an issue asking for
>> that refactoring such that we don't forget it? the fix should be
>> fairly trivial as the Tree gets passed to the constructor for
>> validation but is currently not kept as field.
> https://issues.apache.org/jira/browse/OAK-733
> Michael
>> regards
>> angela

View raw message