-1 for having the security-manager optional.
the security section has been completely reworked
and the security-manager is a key functionality.
up to know the access-manager was the only mandatory
element in the security section. with the new security
code it could even be the other way round: t
[
https://issues.apache.org/jira/browse/JCR-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boni Gopalan updated JCR-1762:
--
Attachment: JCR-1762-patch.zip
Files Changed :
src/main/java/org/apache/jackrabbit/ocm/manag
Improvement to MultiValueCollectionConverterImpl to Map collections with
element class Object.class
---
Key: JCR-1762
URL: https://issues.apache.org/jira/browse/JCR-17
[
https://issues.apache.org/jira/browse/JCR-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634268#action_12634268
]
Oliver Lietz commented on JCR-1721:
---
Not sure what you mean. The digester is using Collecti
+1
regards,
david
Hi,
On Wed, Sep 24, 2008 at 8:52 PM, Thomas Müller <[EMAIL PROTECTED]> wrote:
> In that case the SecurityManager setting should be truly optional: no
> warning should be logged if it is missing.
Why is that?
We can (and should) deprecate old configurations like ones with no
SecurityManager or no
On Wed, Sep 24, 2008 at 3:06 PM, Angela Schreiber <[EMAIL PROTECTED]> wrote:
>
>> [JCR-1300] Improve performance for large binary properties
>> [JCR-1319] NullPointerException when accessing the SimpleWebdav ...
>> [JCR-1392] Exception not thrown where it appears it should have been
>> [JCR-1401] R
+1 for being backwards compatible in a minor 1.x release
In that case the SecurityManager setting should be truly optional: no
warning should be logged if it is missing.
+1
Thanks and Regards
Felix
Angela Schreiber schrieb:
> hi
>
> i'd like to release a couple of jcr-server bug fixes
> in the 1.4 branch.
>
> please find below the list of issues that should
> from my point of view go into that release:
>
> [JCR-1300] Improve performance for large binary proper
On Wed, Sep 24, 2008 at 2:25 PM, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> The question is, should the 1.5 upgrade changes in configuration files
> or not? I would rather opt for a smoother upgrade with more backwards
> compatibility, but I acknowledge that there are good reasons why we
> might wa
[
https://issues.apache.org/jira/browse/JCR-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1736:
---
Fix Version/s: (was: core 1.4.6)
1.4.1
If we do included this in 1.4, that would
[
https://issues.apache.org/jira/browse/JCR-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-1630.
Resolution: Fixed
Resolving as Fixed. As the final piece I added an "About Apache Jackrabbit"
page t
[
https://issues.apache.org/jira/browse/JCR-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-1678:
Fix Version/s: (was: 1.5)
jcr-server 1.4.1
> NullPointerException in constructor of JcrDavExce
[
https://issues.apache.org/jira/browse/JCR-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-1392:
Fix Version/s: (was: 1.5)
jcr-server 1.4.1
> [PATCH] Exception not thrown where it appears it
[
https://issues.apache.org/jira/browse/JCR-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-1679:
Fix Version/s: (was: 1.5)
jcr-server 1.4.1
> Simple Webdav: dir with same name as repository h
[
https://issues.apache.org/jira/browse/JCR-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-1300:
Fix Version/s: (was: 1.5)
jcr-server 1.4.1
> spi2dav Improve performance for large binary prop
[
https://issues.apache.org/jira/browse/JCR-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-1345:
Fix Version/s: (was: 1.4.1)
jcr-server 1.4.1
> ClassCastException when updating properties usi
[
https://issues.apache.org/jira/browse/JCR-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-1319:
Fix Version/s: (was: 1.5)
jcr-server 1.4.1
> NullPointerException when accessing the SimpleWeb
[
https://issues.apache.org/jira/browse/JCR-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-1401:
Fix Version/s: (was: 1.5)
(was: 1.4.1)
jcr-server 1.4.1
> Removing-node
[
https://issues.apache.org/jira/browse/JCR-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634142#action_12634142
]
Jukka Zitting commented on JCR-1756:
With the OCM components now included in the main Jac
[
https://issues.apache.org/jira/browse/JCR-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634140#action_12634140
]
Micah Whitacre commented on JCR-1753:
-
My use case is described in the mailing list link
[JCR-1300] Improve performance for large binary properties
[JCR-1319] NullPointerException when accessing the SimpleWebdav ...
[JCR-1392] Exception not thrown where it appears it should have been
[JCR-1401] Removing-nodes with unexpected nodetype
[JCR-1679] Dir with same name as repository has i
[
https://issues.apache.org/jira/browse/JCR-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-1353:
Component/s: (was: jackrabbit-jcr-server)
jackrabbit-webapp
> Installation For people new to tom
Hi i have created a simple application for adding some content and then
trying to search for the same.
Somewhere it is failing and it does not actually give an error. I dont even
know if the add is working properly
I have attached the files. you just need to run the "TestJackRabbit.java"
and check
Hi,
On Wed, Sep 24, 2008 at 2:06 PM, Thomas Mueller (JIRA) <[EMAIL PROTECTED]>
wrote:
> Compatibility: Jackrabbit 1.5 will not work with 1.4 repository.xml files
> because of
> JCR-1472 (SecurityManager). If we want to make the repository.xml backward
> compatible,
> we should have a look at th
[
https://issues.apache.org/jira/browse/JCR-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634118#action_12634118
]
Thomas Mueller commented on JCR-1462:
-
> how much we are actually gaining by enabling DTD
[
https://issues.apache.org/jira/browse/JCR-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634115#action_12634115
]
Jakub Wozniakowski commented on JCR-1755:
-
Extremely quick reaction and fix. Thank yo
[
https://issues.apache.org/jira/browse/JCR-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634099#action_12634099
]
Jukka Zitting commented on JCR-1724:
Committed the component and the modifications in rev
[
https://issues.apache.org/jira/browse/JCR-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-1737.
Resolution: Fixed
Fix Version/s: 1.5
Assignee: Jukka Zitting
Fixed in revision 698489
[
https://issues.apache.org/jira/browse/JCR-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-1756.
Resolution: Fixed
Patch applied in revision 698480. Resolving as Fixed.
> Include OCM in the main Ja
[
https://issues.apache.org/jira/browse/JCR-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-1631.
Resolution: Fixed
Patch applied in revision 698478. Resolving as Fixed.
> Replace commons-logging de
[
https://issues.apache.org/jira/browse/JCR-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634075#action_12634075
]
Jukka Zitting commented on JCR-1462:
> Is this option implementation independent?
No, i
[
https://issues.apache.org/jira/browse/JCR-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634072#action_12634072
]
Marcel Reutegger commented on JCR-1462:
---
Is this option implementation independent?
>
[
https://issues.apache.org/jira/browse/JCR-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1462:
---
Attachment: JCR-1462-dynamic.patch
Attached a proposed patch (JCR-1462-dynamic.patch) that enables vali
[
https://issues.apache.org/jira/browse/JCR-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634068#action_12634068
]
Christophe Lombart commented on JCR-1761:
-
See discussion :
http://jackrabbit.markm
hi
i'd like to release a couple of jcr-server bug fixes
in the 1.4 branch.
please find below the list of issues that should
from my point of view go into that release:
[JCR-1300] Improve performance for large binary properties
[JCR-1319] NullPointerException when accessing the SimpleWebdav ...
[
https://issues.apache.org/jira/browse/JCR-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634063#action_12634063
]
Jukka Zitting commented on JCR-1462:
How about if we set the http://apache.org/xml/featur
[
https://issues.apache.org/jira/browse/JCR-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634062#action_12634062
]
Stefan Guggisberg commented on JCR-664:
---
+1 for 'Won't Fix'
> Property.setValue(Node) e
OCM:Add the ability to specify name of a Collection Element through XML Mapping
files.
--
Key: JCR-1761
URL: https://issues.apache.org/jira/browse/JCR-1761
Project: J
[
https://issues.apache.org/jira/browse/JCR-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634052#action_12634052
]
Alexander Klimetschek commented on JCR-1462:
What about a two-pass parsing: in th
[
https://issues.apache.org/jira/browse/JCR-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1631:
---
Component/s: (was: jackrabbit-text-extractors)
jackrabbit-webapp
j
[
https://issues.apache.org/jira/browse/JCR-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved JCR-664.
--
Resolution: Won't Fix
+1, see also my previous comment.
> Property.setValue(Node) explicitly chec
[
https://issues.apache.org/jira/browse/JCR-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634048#action_12634048
]
Marcel Reutegger commented on JCR-1462:
---
I think we should remove the DTD validation ag
[
https://issues.apache.org/jira/browse/JCR-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634047#action_12634047
]
Jukka Zitting commented on JCR-1538:
> "failed to add property " + name + " to " + this
[
https://issues.apache.org/jira/browse/JCR-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634045#action_12634045
]
Marcel Reutegger commented on JCR-1631:
---
+1
> Replace commons-logging dependency with
[
https://issues.apache.org/jira/browse/JCR-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634044#action_12634044
]
Marcel Reutegger commented on JCR-1753:
---
I have the same concerns regarding the visibil
On Wed, Sep 24, 2008 at 3:44 AM, xing007008 <[EMAIL PROTECTED]> wrote:
> I don't know how to register Repository.
Where do you want to register the Repository? If you want to register
it with JNDI, see my previous answer to your mail where I pointed to
some Jackrabbit code that does JNDI handling.
47 matches
Mail list logo
