Hi,
On Thu, Apr 24, 2008 at 8:41 PM, Thomas Mueller
<[EMAIL PROTECTED]> wrote:
> > The best solution IMHO is not to allow SNS in the first place.
>
> Yes, unfortunately it's not the default behavior. And making it the
> default would break XML import.
Sure, but if you're (or your application
Hi,
> The best solution IMHO is not to allow SNS in the first place.
Yes, unfortunately it's not the default behavior. And making it the
default would break XML import.
> Another solution would be a custom getOrAddNode() method, like the one
> I've implemented
try {
retur
Hi,
Let's keep JCR-1552 focused on the setProperty semantics. The addNode
method is a whole different issue so I'm taking it back to the mailing
list.
On Thu, Apr 24, 2008 at 5:19 PM, Thomas Mueller (JIRA) <[EMAIL PROTECTED]>
wrote:
> When concurrently updating or adding nodes (so far I was talk
[
https://issues.apache.org/jira/browse/JCR-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592076#action_12592076
]
Thomas Mueller commented on JCR-1552:
-
Jackrabbit should either always or never throw an
[
https://issues.apache.org/jira/browse/JCR-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592052#action_12592052
]
Stefan Guggisberg commented on JCR-1552:
> > this special case can be compared with
[
https://issues.apache.org/jira/browse/JCR-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592051#action_12592051
]
Jukka Zitting commented on JCR-1552:
Stefan:
> this particular issue is about the special
[
https://issues.apache.org/jira/browse/JCR-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592044#action_12592044
]
[EMAIL PROTECTED] edited comment on JCR-1552 at 4/24/08 5:58 AM:
--
tested the release as follows:
* downloaded src, checked md5
* ran: mvn install, successful
+1 Release this package as jackrabbit-core 1.4.3
--
regards, toby
On 4/24/08, Thomas Mueller <[EMAIL PROTECTED]> wrote:
> Hi,
>
> +1 Release this package as jackrabbit-core 1.4.3
>
> I agree, it's not a
[
https://issues.apache.org/jira/browse/JCR-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592044#action_12592044
]
Stefan Guggisberg commented on JCR-1552:
> AFAIK that's outside the scope of this iss
[
https://issues.apache.org/jira/browse/JCR-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592043#action_12592043
]
Stefan Guggisberg commented on JCR-1552:
> Jukka Zitting commented on JCR-1552:
> -
[
https://issues.apache.org/jira/browse/JCR-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592040#action_12592040
]
Thomas Mueller commented on JCR-1380:
-
Revision 651247: improved test case
> CachingHier
Hi,
+1 Release this package as jackrabbit-core 1.4.3
I agree, it's not a problem. Anyway those are generated files. Good to
know it is fixed in future releases.
Regards,
Thomas
On Thu, Apr 24, 2008 at 1:59 PM, Jukka Zitting <[EMAIL PROTECTED]> wrote:
> Hi,
>
>
> On Thu, Apr 24, 2008 at 2:45
[
https://issues.apache.org/jira/browse/JCR-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592000#action_12592000
]
Alexander Klimetschek commented on JCR-1552:
Ok, then I would favor to
a) make i
Hi,
On Thu, Apr 24, 2008 at 2:45 PM, Thomas Mueller
<[EMAIL PROTECTED]> wrote:
> I just noticed that the file
>
> http://people.apache.org/~jukka/jackrabbit/jackrabbit-core-1.4.3/repository/org/apache/jackrabbit/jackrabbit-core/1.4.3/jackrabbit-core-1.4.3-sources.jar
> contains generated Java
[
https://issues.apache.org/jira/browse/JCR-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591991#action_12591991
]
Jukka Zitting commented on JCR-1552:
> That being said: your interpretation makes this fe
Hi,
I just noticed that the file
http://people.apache.org/~jukka/jackrabbit/jackrabbit-core-1.4.3/repository/org/apache/jackrabbit/jackrabbit-core/1.4.3/jackrabbit-core-1.4.3-sources.jar
contains generated Java files in the root folder instead of the
respective package name folder (for example: AS
[
https://issues.apache.org/jira/browse/JCR-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591974#action_12591974
]
Michael Dürig commented on JCR-1550:
+1
> Remove ItemInfo.getName() since it is redundan
[
https://issues.apache.org/jira/browse/JCR-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591972#action_12591972
]
Michael Dürig commented on JCR-1405:
I'm in favour of the patch as it is. That is, add ge
[
https://issues.apache.org/jira/browse/JCR-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-1550:
Attachment: JCR-1550.diff
proposed patch for the trunk
> Remove ItemInfo.getName() since it is redundant
> -
[
https://issues.apache.org/jira/browse/JCR-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sven Rieckhoff updated JCR-1554:
Attachment: jackrabbit-tx-bug.zip
As announced a simple java application demonstrating the bug...
>
StaleItemStateException with distributed transactions
-
Key: JCR-1554
URL: https://issues.apache.org/jira/browse/JCR-1554
Project: Jackrabbit
Issue Type: Bug
Components: transacti
[
https://issues.apache.org/jira/browse/JCR-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591964#action_12591964
]
angela commented on JCR-1550:
-
you are right... since it seems not to be used currently with jcr2
[
https://issues.apache.org/jira/browse/JCR-1349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591961#action_12591961
]
Dirk Feufel commented on JCR-1349:
--
Same problem with WebSphere and datasources. In addition
> Yes, that is correct -- this is not about JCR compliance, but about what we
> expect *Jackrabbit* to do.
ah i see... ok, my expectation would be that jackrabbit does not throw ;)
regards,
david
--
Visit: http://dev.day.com/ - Day JCR Cup 08 - Win a MacBook Pro
David Nuescheler wrote:
I indeed get the expected exception, but not for
n1.getProp
n2.getProp
n1.setProp
n1.save
n2.setProp
n2.save
...which I hoped for.
i think it would be totally legitimate for a content repository to either
throw or not... personally, i would not support
> I indeed get the expected exception, but not for
>
> n1.getProp
> n2.getProp
>
> n1.setProp
> n1.save
>
> n2.setProp
> n2.save
>
> ...which I hoped for.
i think it would be totally legitimate for a content repository to either
throw or not... personally, i would not support a test
26 matches
Mail list logo
