[
https://issues.apache.org/jira/browse/JCR-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved JCR-834.
--
Resolution: Duplicate
Ampersand In query constraint causes InvalidQueryException
Hi Sten,
I'd recommend to create a SOAP API based on the Jackrabbit SPI effort because it
is much easier to implement. In contrast to the JCR API the Jackrabbit SPI is
less object oriented (e.g. there are no methods to navigate between items, etc.)
and better suited for protocols.
See:
Thanks. I will look into the SPI package. The only thing is that it would be
nice if the SOAP api could be used with any JSR-170 compliant servers on the
backend.
/srs
On 4/10/07, Marcel Reutegger [EMAIL PROTECTED] wrote:
Hi Sten,
I'd recommend to create a SOAP API based on the Jackrabbit
A little fast on the trigger there. Looked at the SPI for a brief moment and
noticed that SPI2JCR project exists and that covers what I need to look at.
Thanks again.
/srs
On 4/10/07, Sten Roger Sandvik [EMAIL PROTECTED] wrote:
Thanks. I will look into the SPI package. The only thing is that
Hi Sten,
thanks for looking into that. I would like to express my support
of any effort going into that direction.
I think it would be great to have SOAP bindings for the SPI in Jackrabbit.
In combination with JCR2SPI and SPI2JCR it makes for a
very interesting remoting layer.
I think that this
[
https://issues.apache.org/jira/browse/JCR-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487770
]
Stefan Guggisberg commented on JCR-836:
---
for a related discussion on the users list see:
[
https://issues.apache.org/jira/browse/JCR-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487771
]
Jukka Zitting commented on JCR-836:
---
Such a feature would IMHO be best implemented with customizable startup scripts
MatchAllQuery does not implement extractTerms()
---
Key: JCR-837
URL: https://issues.apache.org/jira/browse/JCR-837
Project: Jackrabbit
Issue Type: Bug
Components: query
[
https://issues.apache.org/jira/browse/JCR-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved JCR-837.
--
Resolution: Fixed
Implemented in revision: 527132
MatchAllQuery does not implement
[
https://issues.apache.org/jira/browse/JCR-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487776
]
Darren Hartford commented on JCR-836:
-
JCR-771 is a good reference, sorry I must have missed that feature request.
[
https://issues.apache.org/jira/browse/JCR-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-838:
---
Summary: bad assumptions/error handling in SetValueVersionExceptionTest:
(was: bad assumtions/error
Have already code that exposes JCR as SOAP, but the SPI package is much more
exiting indeed. Will try to contribute some code in this area very soon. The
JCR - SPI - SOAP - JCR cycle would be the ultimate goal.
/srs
On 4/10/07, David Nuescheler [EMAIL PROTECTED] wrote:
Hi Sten,
thanks for
Sten Roger Sandvik wrote:
Have already code that exposes JCR as SOAP, but the SPI package is much more
exiting indeed. Will try to contribute some code in this area very soon.
looking forward to your contribution.
The JCR - SPI - SOAP - JCR cycle would be the ultimate goal.
I rather had
[
https://issues.apache.org/jira/browse/JCR-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke reassigned JCR-826:
--
Assignee: Julian Reschke
NodeTest.testAddNodeConstraintViolationExceptionUndefinedNodeType
Yes, sorry. I also thought of JCR - SPI - SOAP - SPI - JCR. Missed a
step there. Thanks for pointing that out.
Regards,
Sten Roger
On 4/10/07, Marcel Reutegger [EMAIL PROTECTED] wrote:
Sten Roger Sandvik wrote:
Have already code that exposes JCR as SOAP, but the SPI package is much
more
The following trace is occuring both when building directly from svn on
Lucene 2.0.0, and after hand-installing jcr-1.0.jar (which failed to
download) and Lucene 2.1.0, which isn't in maven yet. It's clear that
the compile failure (running unit tests) is not associated with which
Lucene is
[
https://issues.apache.org/jira/browse/JCR-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487896
]
Julian Reschke commented on JCR-826:
Fixed in several places with revision 527261.
Issue self-resolved when compiling from the distribution rather than
subversion. No problems running against Lucene 2.1.0 after tweaking
PersistentIndex.
Jack
Jack Park wrote:
The following trace is occuring both when building directly from svn on
Lucene 2.0.0, and after hand-installing
I use a db2 database on an iSeries (AS400) to store my project. I connect
just fine, and I can create nodes, child nodes and grandchild nodes, along
with appropriate properties. It's just that it is so very slow. 20-30
seconds per node! Am I doing anything wrong?
The controlling methods are:
I am also currently thinking about how to remote JCR through web services.
Sten, assuming you can contribute this (without intellectual property
issues)
would it be possible to add this under a jira issue and attach your
progress/sources?
Can an active committer confirm this is desirable?
Also
20 matches
Mail list logo
