[jira] [Created] (JCR-3169) Exception when shutting down Jackrabbit using a NOT embedded Derby database

Exception when shutting down Jackrabbit using a NOT embedded Derby database --- Key: JCR-3169 URL: https://issues.apache.org/jira/browse/JCR-3169 Project: Jackrabbit Content Repos

[jira] [Commented] (JCR-3169) Exception when shutting down Jackrabbit using a NOT embedded Derby database

[ https://issues.apache.org/jira/browse/JCR-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162686#comment-13162686 ] Sascha Theves commented on JCR-3169: That is because the DerbyPersistenceManager closes

[jira] [Resolved] (JCR-3167) Make Jackrabbit compile on Java 7

[ https://issues.apache.org/jira/browse/JCR-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting resolved JCR-3167. Resolution: Fixed Fix Version/s: 2.3.5 Assignee: Jukka Zitting Fixed in revision 1209

[jira] [Commented] (JCR-3169) Exception when shutting down Jackrabbit using a NOT embedded Derby database

[ https://issues.apache.org/jira/browse/JCR-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162695#comment-13162695 ] Sascha Theves commented on JCR-3169: One more information: I am using one single DataSou

[jira] [Commented] (JCR-3169) Exception when shutting down Jackrabbit using a NOT embedded Derby database

[ https://issues.apache.org/jira/browse/JCR-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162697#comment-13162697 ] Sascha Theves commented on JCR-3169: The DerbyFileSystems seems to have the same problem

[jira] [Updated] (JCR-3169) Exception when shutting down Jackrabbit using a NOT embedded Derby database

[ https://issues.apache.org/jira/browse/JCR-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Theves updated JCR-3169: --- Priority: Major (was: Minor) > Exception when shutting down Jackrabbit using a NOT embedded Derby

[jira] [Commented] (JCR-3169) Exception when shutting down Jackrabbit using a NOT embedded Derby database

[ https://issues.apache.org/jira/browse/JCR-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162701#comment-13162701 ] Sascha Theves commented on JCR-3169: Following the example from http://wiki.apache.org/j

Fwd: [Jackrabbit Wiki] Update of "Jsop" by JulianReschke

FYI: Original Message Subject: [Jackrabbit Wiki] Update of "Jsop" by JulianReschke Date: Mon, 05 Dec 2011 11:22:43 - From: Apache Wiki Reply-To: dev@jackrabbit.apache.org To: Apache Wiki Dear Wiki user, You have su

[jira] [Created] (JCR-3170) Precompile JavaCC parsers in jackrabbit-spi-commons

Precompile JavaCC parsers in jackrabbit-spi-commons --- Key: JCR-3170 URL: https://issues.apache.org/jira/browse/JCR-3170 Project: Jackrabbit Content Repository Issue Type: Improvement

JSOP extension points, was: JSOP

On 2011-11-29 17:37, Thomas Mueller wrote: Hi, What is not on this wiki page yet - because it's not defined yet - is: "commit metadata". Commit metadata is needed when you want to: * get multiple commits (diffs) in one block * send multiple commits (diffs) in one block As an example, see Micro

Re: JSOP extension points, was: JSOP

On 5.12.11 13:35, Julian Reschke wrote: This highlights a general problem with the compact syntax; it lacks an extension point. Unless I'm missing something, a today's JSOP parsers will be unable to parse future messages that contain an extension defined like the above, as they won't know how

Re: JSOP extension points, was: JSOP

Hi, >Unless I'm missing something, a today's JSOP parsers will be unable to >parse future messages that contain an extension defined like the above, >as they won't know how to skip over it. What we currently don't have, and probably should add, is a way to negotiate the format / protocol version

Re: JSOP extension points, was: JSOP

On 05.12.11 15:02, "Thomas Mueller" wrote: >Could you provide examples of >languages that do support such extension points? JSON itself: if you specify that you are only interested in the property "foo" in your json-based data, you will automatically skip any other properties in the structure, wi

Re: JSOP extension points, was: JSOP

On 2011-12-05 15:02, Thomas Mueller wrote: Hi, Unless I'm missing something, a today's JSOP parsers will be unable to parse future messages that contain an extension defined like the above, as they won't know how to skip over it. What we currently don't have, and probably should add, is a way

[jira] [Commented] (JCR-3170) Precompile JavaCC parsers in jackrabbit-spi-commons

[ https://issues.apache.org/jira/browse/JCR-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162806#comment-13162806 ] Claus Köll commented on JCR-3170: - +1 from me :-) > Precompile JavaCC parse

[jira] [Resolved] (JCR-3170) Precompile JavaCC parsers in jackrabbit-spi-commons

[ https://issues.apache.org/jira/browse/JCR-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting resolved JCR-3170. Resolution: Fixed Fix Version/s: 2.3.5 Done in revision 1210476. > Precompile

Re: JSOP extension points, was: JSOP

On 5.12.11 13:35, Julian Reschke wrote: This highlights a general problem with the compact syntax; it lacks an extension point. Unless I'm missing something, a today's JSOP parsers will be unable to parse future messages that contain an extension defined like the above, as they won't know how

Re: JSOP extension points, was: JSOP

On 5.12.11 14:54, Michael Dürig wrote: Unless I'm missing something, a today's JSOP parsers will be unable to parse future messages that contain an extension defined like the above, as they won't know how to skip over it. We could add an extension point to the compact syntax through the foll

no PERSIST events?

Hi, I was just looking at a stream of events and noticed that we don't seem to generate PERSIST events? Is there a good reason for this, or is this just something we haven't done yet? Best regards, Julian

[jira] [Updated] (JCR-2541) spi2dav : EventJournal not implemented

[ https://issues.apache.org/jira/browse/JCR-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-2541: Attachment: ejpatch.diff Work in progress: implementation of EventJournal as Atom feed. Entry details

[jira] [Commented] (JCR-3170) Precompile JavaCC parsers in jackrabbit-spi-commons

[ https://issues.apache.org/jira/browse/JCR-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163107#comment-13163107 ] Felix Meschberger commented on JCR-3170: Sorry for being late. But I don't think, th