Issue Subscription
Filter: open issues (215 issues)
Open Issues for Apache Jackrabbit
Subscriber: jackrabbitdev
Key Summary
JCR-1413[PATCH] retain exception stack traces
https://issues.apache.org/jira/browse/JCR-1413
JCR-1412[Patch] Pure Java-based configuration of Jac
Hello,
I had a look at the getOutputStream method of the
org.apache.jackrabbit.core.fs.mem.MemoryFileSystem class, its code is
presented below:
public OutputStream getOutputStream(String filePath) throws
FileSystemException
{
String folderPath = filePath;
if (filePat
Julian Reschke wrote:
...
Going back to the original discussion:
what I think we need is a way to return NodeInfos, not ChildInfos.
Right now, when browsing a collection of 1000 items, getting information
about each node (timestamps, dates, ...) requires 1000 individual calls
through SPI.
One of the reasons I really don't like Iterators in SPI is because they
make it hard to perform logging. I have a dynamic proxy that performs
trace logging for SPI calls. So in my SPI's I use Apache
ResettableIterator's wherever I can, which my trace logger knows about.
For any other Iterator thoug
...continuing on the mailing list; I think this exceeds what an issue
tracker is good for.
angela (JIRA) wrote:
angela commented on JCR-1405:
-
julian:
if you cant determine the childinfos upon creating the nodeinfo you should (as
stated by the javadoc) simply ret
[
https://issues.apache.org/jira/browse/JCR-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571713#action_12571713
]
angela commented on JCR-1405:
-
julian:
if you cant determine the childinfos upon creating the no
