Hi all,
Cool !
But: There is one important issue, though. Using annotations (out of the
box) requires Java 5, while Jackrabbit is still AFAIK intended to the
usable with Java 1.4.
Thus we would have to carefully decided on whether and how to apply this
patch to not loose 1.4 compatibility suppor
Hi,
As has recently been discussed, I'd like to promote the OCM component
from contrib status to be released as a part of Jackrabbit 1.4. The
component is seeing increasing levels of use, and making a formal
release would make it easier for people to depend on the component in
external projects.
Hi,
The SPI project is becoming more mature, and people are starting to
use it for connector and other stuff. The full round-trip from JCR to
SPI and back using the jcr2spi and spi2jcr components is also mostly
finished, which means that it is quite easy to hook up various JCR
stuff with the SPI.
Hi,
First off, I am all for a promotion to the main stream.
But then, I am somewhat reserved with respect to the Node Type
Management stuff. This is - as the respective API is not defined in JCR
- depending on the Jackrabbit-Core library.
So as first step, I suggest investigating whether it is p
Hi,
I agree to moved SPI to prime time, with one single exception:
> At this point we could make jackrabbit-core depend on spi and
> spi-commons for some of the generic functionality, even though we
> wouldn't still use the RepositoryService or the other central
> interfaces in jackrabbit-core.
On 7/3/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:
Hi,
I agree to moved SPI to prime time, with one single exception:
> At this point we could make jackrabbit-core depend on spi and
> spi-commons for some of the generic functionality, even though we
> wouldn't still use the RepositoryServi
[
https://issues.apache.org/jira/browse/JCR-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509851
]
angela commented on JCR-774:
the same applies for
- NodeCanAddMixinTest.testLocked
> TCK: Test that expect that modificat
[
https://issues.apache.org/jira/browse/JCR-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-774:
---
Attachment: NodeCanAddMixinTest.patch
> TCK: Test that expect that modifications made by Session1 are automatically
> v
SPI: provide batch read functionality
-
Key: JCR-999
URL: https://issues.apache.org/jira/browse/JCR-999
Project: Jackrabbit
Issue Type: New Feature
Components: SPI
Reporter: angela
JCR2SPI: remove duplicate item states
-
Key: JCR-1000
URL: https://issues.apache.org/jira/browse/JCR-1000
Project: Jackrabbit
Issue Type: Improvement
Components: SPI
Reporter: angela
Does anyone know how to order a collection of child nodes by a specific
property from the getNodes() call? or do i have to manually order the nodes
using java? Please let me know if you have any ideas. Is there a way to
query just for a parents child nodes and put an order by clause in the
query
Hi,
On 7/3/07, angela (JIRA) <[EMAIL PROTECTED]> wrote:
JCR2SPI: remove duplicate item states
-
Key: JCR-1000
Reporter: angela
You have filed the 1000'th Jackrabbit issue, and will thus be rewarded
by eternal fame in the issue tracker history. :-)
BR,
Jukk
Hi,
On 7/3/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> At this point we could make jackrabbit-core depend on spi and
> spi-commons for some of the generic functionality, even though we
> wouldn't still use the RepositoryService or the other central
> interfaces in jackrabbit-core.
If we
[
https://issues.apache.org/jira/browse/JCR-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-1000.
-
Resolution: Fixed
fixed with rev. 552873
> JCR2SPI: remove duplicate item states
> ---
[
https://issues.apache.org/jira/browse/JCR-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509913
]
angela commented on JCR-999:
initial changes for batch-read with rev. 552873
> SPI: provide batch read functionality
>
[
https://issues.apache.org/jira/browse/JCR-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-851.
Resolution: Fixed
applied patch with rev. 552909 and modified the QValueTest class accordingly
> Handling of binary
SPI: prefer 'Iterator' instead of specialized subclasses
Key: JCR-1001
URL: https://issues.apache.org/jira/browse/JCR-1001
Project: Jackrabbit
Issue Type: Improvement
Compone
On 7/3/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:
Hi all,
Cool !
But: There is one important issue, though. Using annotations (out of the
box) requires Java 5, while Jackrabbit is still AFAIK intended to the
usable with Java 1.4.
Thus we would have to carefully decided on whether and how
I'm agree with Felix :
1/ Move the jcr-mapping & drop ref to jackrabbit-core
2/ Wait for the node management tools. Why not to keep it in the contrib
areal until we found a solution ?
3/ The modification mades for Spring support can be contributed to the
Spring module project.
Christophe
On 7/
Hi,
> this doesn't affect the rest of jackrabbit, if you want to use java
> 1.4 with ocm you can use the digester implementation.
Don't you have to compile it using targetVM=1.5 ? In that case you would
not be able to use with 1.4 anymore due to the increased class file
version. I would love to b
On 7/3/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:
Hi,
> this doesn't affect the rest of jackrabbit, if you want to use java
> 1.4 with ocm you can use the digester implementation.
Don't you have to compile it using targetVM=1.5 ? In that case you would
not be able to use with 1.4 anymore
21 matches
Mail list logo
