[
https://issues.apache.org/jira/browse/JCR-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12737023#action_12737023
]
Marcel Reutegger commented on JCR-2233:
---
So the only thing that might happen
[
https://issues.apache.org/jira/browse/JCR-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Guggisberg resolved JCR-2234.
Resolution: Fixed
fixed in svn r798958
changed behavior of javax.jcr.Value get* methods
[
https://issues.apache.org/jira/browse/JCR-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12737057#action_12737057
]
Timo Pick commented on JCR-2232:
the patch provided by sivakumar
Hi,
The DefaultAccessManager caches CompiledPermissions, and this cache
persists for the life of the session. Accessing Jackrabbit through
Sling, there's some additional session pooling so that sessions (and
therefore cached permissions) persist over requests.
This is causing an issue for us
[
https://issues.apache.org/jira/browse/JCR-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12737074#action_12737074
]
Bart van der Schans commented on JCR-2171:
--
Can this fix also be backported to the
Set binary property data using OutputStream
---
Key: JCR-2235
URL: https://issues.apache.org/jira/browse/JCR-2235
Project: Jackrabbit Content Repository
Issue Type: New Feature
Components:
[
https://issues.apache.org/jira/browse/JCR-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-2235:
--
Attachment: JCR-2235.patch
Set binary property data using OutputStream
[
https://issues.apache.org/jira/browse/JCR-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-2235:
--
Status: Patch Available (was: Open)
Set binary property data using OutputStream
hi arthur
Are there any plans to make that change?
not at the moment.
If I wanted to tackle that,
where would be a good place to start?
not sure what would be the best approach... nor am i totally
convinced that it should be changedthat's the 'eventually'
in the TODO comment ;)
Oh. I had read 'ev.' as 'evidently' :)
Absent changing that, then, is there any recommended mitigation
strategy; should we be killing all open and cached sessions whenever
there is a permissions change?
Thanks,
Arthur
Angela Schreiber wrote:
hi arthur
Are there any plans to make that
Arthur Taylor wrote:
Oh. I had read 'ev.' as 'evidently' :)
nice :)
Absent changing that, then, is there any recommended mitigation
strategy; should we be killing all open and cached sessions whenever
there is a permissions change?
permission changes are diffent thing... the compiled
Thanks for the reply,
permission changes are diffent thing... the compiled
permissions are intended to be notified and recalculated
whenever the permissions for any of the principals it
has been created for is modified. if that doesn't work
it's a bug.
Agreed. I think permissions changes for
[
https://issues.apache.org/jira/browse/JCR-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek resolved JCR-2232.
Resolution: Won't Fix
As noted in JCR-990 and
I just wanted to be sure that there wasn't a less expensive
approach first.
don't get me wrong:
i'm not saying that there isn't a less expensive
approach... when adding that TODO comment i simply
wasn't sure, if the Subject created upon login
should be changed in the first place.
in the
[
https://issues.apache.org/jira/browse/JCR-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12737137#action_12737137
]
Lars Trieloff commented on JCR-642:
---
Do you think it is necessary to break the NodeState or
[
https://issues.apache.org/jira/browse/JCR-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12737154#action_12737154
]
Alexander Klimetschek commented on JCR-642:
---
I think that limiting children to 100k
[
https://issues.apache.org/jira/browse/JCR-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12737163#action_12737163
]
Lars Trieloff commented on JCR-642:
---
I think that limiting children to 100k nodes is
[
https://issues.apache.org/jira/browse/JCR-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12737188#action_12737188
]
Timo Pick commented on JCR-2232:
Thanks for the quick answer. Is it really a viable solution
[
https://issues.apache.org/jira/browse/JCR-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12737234#action_12737234
]
Alexander Klimetschek commented on JCR-2232:
Is it really a viable solution to
Hello all,
We're considering implementing a JSR 283 CR in PHP 5 and releasing this
under the Apache license.
We're aware of early projects aimed at developing a JSR 170 CR. Are you
aware of any current efforts to do so? Would this be something the
Jackrabbit community would be interested in
20 matches
Mail list logo
