[jira] Created: (JCR-389) WebDAV server should treat non-wellformed XML in request bodies as error

WebDAV server should treat non-wellformed XML in request bodies as error Key: JCR-389 URL: http://issues.apache.org/jira/browse/JCR-389 Project: Jackrabbit Type: Bug Components: webdav

[jira] Updated: (JCR-389) WebDAV server should treat non-wellformed XML in request bodies as error

[ http://issues.apache.org/jira/browse/JCR-389?page=all ] Julian Reschke updated JCR-389: --- Attachment: diffs This patch adds DavException to the signature of getRequestDocument(), and attempts to make sure that an exception is thrown when a request body

[jira] Created: (JCR-391) WebDAV method invocation trying to create a new resource should fail with 409 (Conflict) if parent resource does not exist

WebDAV method invocation trying to create a new resource should fail with 409 (Conflict) if parent resource does not exist -- Key: JCR-391 URL:

[jira] Commented: (JCR-391) WebDAV method invocation trying to create a new resource should fail with 409 (Conflict) if parent resource does not exist

[ http://issues.apache.org/jira/browse/JCR-391?page=comments#action_12373842 ] Julian Reschke commented on JCR-391: Angela, confirmed: modifying the Litmus test case to use Depth: Infinity shows that in this case the correct response code is returned.

[jira] Updated: (JCR-391) WebDAV method invocation trying to create a new resource should fail with 409 (Conflict) if parent resource does not exist

[ http://issues.apache.org/jira/browse/JCR-391?page=all ] Julian Reschke updated JCR-391: --- Attachment: diff.txt OK, as Angela pointed out, this is because Litmus is trying a shallow copy, which currently isn't implemented. Returning 403 in this case is

[jira] Created: (JCR-406) If header evaluation compliance provlems

If header evaluation compliance provlems Key: JCR-406 URL: http://issues.apache.org/jira/browse/JCR-406 Project: Jackrabbit Type: Bug Components: webdav Reporter: Julian Reschke There is a problem with the

[jira] Updated: (JCR-405) PROPPATCH doesn't respect document order

[ http://issues.apache.org/jira/browse/JCR-405?page=all ] Julian Reschke updated JCR-405: --- Attachment: diffs.txt OK, the attached patch: - deprecates the old alterProperties method, - introduces a new method with List parameter as discussed, -

[jira] Commented: (JCR-405) PROPPATCH doesn't respect document order

[ http://issues.apache.org/jira/browse/JCR-405?page=comments#action_12376010 ] Julian Reschke commented on JCR-405: Sorry, forgot to mention that this change is *not* well tested yet (I've verified in the debugger that the code executes as designed,

[jira] Commented: (JCR-473) Some enhancements to jackrabbit commons

[ http://issues.apache.org/jira/browse/JCR-473?page=comments#action_12419458 ] Julian Reschke commented on JCR-473: Regarding QName...: Did anybody consider to require JAXP 1.3 (available as seperate download for JDK 1.4), and just to use

[jira] Commented: (JCR-480) JCR connectivity with FrontPage 2003

[ http://issues.apache.org/jira/browse/JCR-480?page=comments#action_12421644 ] Julian Reschke commented on JCR-480: Well. 1) Does this occur only for Frontpage, or for all MS Office applications? 2) Could you please try to obtain HTTP

[jira] Created: (JCR-482) DocViewSaxEventGenerator may generate non-NS-wellformed XML

DocViewSaxEventGenerator may generate non-NS-wellformed XML --- Key: JCR-482 URL: http://issues.apache.org/jira/browse/JCR-482 Project: Jackrabbit Issue Type: Bug Components:

[jira] Updated: (JCR-516) remove dependencies of XPathQueryBuilder on core Jackrabbit code

[ http://issues.apache.org/jira/browse/JCR-516?page=all ] Julian Reschke updated JCR-516: --- Attachment: patch-JCR-516.txt Proposed patch. remove dependencies of XPathQueryBuilder on core Jackrabbit code

[jira] Updated: (JCR-519) Missing support for some general relations in QueryTreeDump and xpath.QueryFormat

[ http://issues.apache.org/jira/browse/JCR-519?page=all ] Julian Reschke updated JCR-519: --- Attachment: patch-JCR-519.txt (proposed patch) Missing support for some general relations in QueryTreeDump and xpath.QueryFormat

[jira] Commented: (JCR-516) remove dependencies of XPathQueryBuilder on core Jackrabbit code

[ http://issues.apache.org/jira/browse/JCR-516?page=comments#action_12424045 ] Julian Reschke commented on JCR-516: Oops. My patch failed to remove the import statement for SearchManager. remove dependencies of XPathQueryBuilder on core

[jira] Commented: (JCR-523) QueryManagerImpl hardwires supported query languages

[ http://issues.apache.org/jira/browse/JCR-523?page=comments#action_12424525 ] Julian Reschke commented on JCR-523: I guess that would require extending QueryTreeBuilder with a method that returns all supported languages, such as Set

[jira] Updated: (JCR-523) QueryManagerImpl hardwires supported query languages

[ http://issues.apache.org/jira/browse/JCR-523?page=all ] Julian Reschke updated JCR-523: --- Attachment: JIRA-523.diff.txt Patch, as proposed in previous comment. QueryManagerImpl hardwires supported query languages

[jira] Updated: (JCR-482) DocViewSaxEventGenerator may generate non-NS-wellformed XML

[ http://issues.apache.org/jira/browse/JCR-482?page=all ] Julian Reschke updated JCR-482: --- Attachment: JIRA-482.diff.txt Proposed patch (serializer remembers previously written namespace declarations and adds new ones when needed).

[jira] Created: (JCR-534) RepositoryStub fails to load default properties file

RepositoryStub fails to load default properties file Key: JCR-534 URL: http://issues.apache.org/jira/browse/JCR-534 Project: Jackrabbit Issue Type: Bug Components: JCR TCK

[jira] Created: (JCR-536) Session leak in API test cases

Session leak in API test cases -- Key: JCR-536 URL: http://issues.apache.org/jira/browse/JCR-536 Project: Jackrabbit Issue Type: Bug Components: JCR TCK Reporter: Julian Reschke

[jira] Updated: (JCR-536) Session leak in API test cases

[ http://issues.apache.org/jira/browse/JCR-536?page=all ] Julian Reschke updated JCR-536: --- Attachment: JCR-536.diff.txt Proposed Patch. Session leak in API test cases -- Key: JCR-536 URL:

[jira] Updated: (JCR-540) AbstractJCRTest fails on level 1 repositories

[ http://issues.apache.org/jira/browse/JCR-540?page=all ] Julian Reschke updated JCR-540: --- Attachment: JCR-540.diff.txt Proposed patch. AbstractJCRTest fails on level 1 repositories - Key:

[jira] Created: (JCR-541) NPE in PredefinedNodeTypeTest.getPropertyDefSpec

NPE in PredefinedNodeTypeTest.getPropertyDefSpec Key: JCR-541 URL: http://issues.apache.org/jira/browse/JCR-541 Project: Jackrabbit Issue Type: Bug Components: JCR TCK

[jira] Updated: (JCR-540) AbstractJCRTest fails on level 1 repositories

[ http://issues.apache.org/jira/browse/JCR-540?page=all ] Julian Reschke updated JCR-540: --- Attachment: JCR-540.diff.txt New proposed patch, not using NotExecutableException. I'd still like to see an easy way to find out whether a repository supports L1

[jira] Commented: (JCR-540) AbstractJCRTest fails on level 1 repositories

[ http://issues.apache.org/jira/browse/JCR-540?page=comments#action_12427479 ] Julian Reschke commented on JCR-540: Marcel, yes that patch works for me. Thanks. AbstractJCRTest fails on level 1 repositories

[jira] Commented: (JCR-488) DASL basicsearch support

[ http://issues.apache.org/jira/browse/JCR-488?page=comments#action_12429370 ] Julian Reschke commented on JCR-488: Well, in *general* you can't correctly map the query. JCR queries use two-valued boolean logic, while DASL/basicsearch uses

[jira] Commented: (JCR-488) DASL basicsearch support

[ http://issues.apache.org/jira/browse/JCR-488?page=comments#action_12429408 ] Julian Reschke commented on JCR-488: Marcel, no I think it's much more complicated. Consider [EMAIL PROTECTED] or @b=1] This will eval to true for any node

[jira] Created: (JCR-547) SimpleSelectionTest assumes RowIterator.getSize() not to return -1

SimpleSelectionTest assumes RowIterator.getSize() not to return -1 -- Key: JCR-547 URL: http://issues.apache.org/jira/browse/JCR-547 Project: Jackrabbit Issue Type: Bug

[jira] Commented: (JCR-482) DocViewSaxEventGenerator may generate non-NS-wellformed XML

[ http://issues.apache.org/jira/browse/JCR-482?page=comments#action_12431254 ] Julian Reschke commented on JCR-482: Related to this, ExportDocViewTest.compareNamespaces() makes the assumption that *all* registered namespaces need to be

[jira] Commented: (JCR-519) Missing support for some general relations in QueryTreeDump and xpath.QueryFormat

[ http://issues.apache.org/jira/browse/JCR-519?page=comments#action_12442188 ] Julian Reschke commented on JCR-519: [[ Old comment, sent by email on Fri, 28 Jul 2006 11:35:09 +0200 ]] Not directly, but it some of what I currently do

[jira] Commented: (JCR-604) After saving over Webdav the jcr:encoding property is deleted

[ http://issues.apache.org/jira/browse/JCR-604?page=comments#action_12444631 ] Julian Reschke commented on JCR-604: As far as I understand, the jcr:encoding property only makes sense if the mime type is text/*. As this isn't the case for

[jira] Created: (JCR-615) JCR2SPI: NPE when parentId returned by NodeInfo.getParentId does not show up in parent's child node list

JCR2SPI: NPE when parentId returned by NodeInfo.getParentId does not show up in parent's child node list Key: JCR-615 URL:

[jira] Created: (JCR-616) Completeness/Freshness of Namespace Registry

Completeness/Freshness of Namespace Registry Key: JCR-616 URL: http://issues.apache.org/jira/browse/JCR-616 Project: Jackrabbit Issue Type: Bug Components: SPI Reporter:

[jira] Commented: (JCR-616) Completeness/Freshness of Namespace Registry

[ http://issues.apache.org/jira/browse/JCR-616?page=comments#action_12446916 ] Julian Reschke commented on JCR-616: I like 1) alot (in fact I was going to suggest something like this myself...), but 2 and 3 would work well for me as well.

[jira] Commented: (JCR-616) Completeness/Freshness of Namespace Registry

[ http://issues.apache.org/jira/browse/JCR-616?page=comments#action_12446931 ] Julian Reschke commented on JCR-616: One problem with approach 4) is that in some backend systems, users can set arbitrary custom properties. That is, there is

[jira] Commented: (JCR-647) NodeType.canRemoveItem does not consider residual definitions (JCR2SPI)

[ http://issues.apache.org/jira/browse/JCR-647?page=comments#action_12454968 ] Julian Reschke commented on JCR-647: For the record: - I agree with Angela's analysis, and - I was wrong when I thought I say other related problems when the

[jira] Commented: (JCR-666) Importing XML with character entities fails

[ http://issues.apache.org/jira/browse/JCR-666?page=comments#action_12456389 ] Julian Reschke commented on JCR-666: How would that be a bug? If that's all you try to import: it's not well-formed XML; you'd need to declare the entity.

[jira] Commented: (JCR-134) Unreferenced VersionHistory should be deleted automatically.

[ http://issues.apache.org/jira/browse/JCR-134?page=comments#action_12457445 ] Julian Reschke commented on JCR-134: Isn't it a common use case that version histories need to be preserved even after the last reference is gone? It seems to me

[jira] Commented: (JCR-688) Improve name resolution

[ http://issues.apache.org/jira/browse/JCR-688?page=comments#action_12461041 ] Julian Reschke commented on JCR-688: If we know that name prefix resolution causes this amount of pain, shouldn't we consider adding QName-based addressing in

[jira] Commented: (JCR-691) Let NameException extend RepositoryException

[ http://issues.apache.org/jira/browse/JCR-691?page=comments#action_12461168 ] Julian Reschke commented on JCR-691: I completely agree with this. Everytime I catch a NameException I wrap it into a RepositoryException. But this change may

[jira] Created: (JCR-724) PropertyReadMethodsTest.testIsSame leaks session

PropertyReadMethodsTest.testIsSame leaks session Key: JCR-724 URL: https://issues.apache.org/jira/browse/JCR-724 Project: Jackrabbit Issue Type: Bug Components: test

[jira] Resolved: (JCR-724) PropertyReadMethodsTest.testIsSame leaks session

[ https://issues.apache.org/jira/browse/JCR-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-724. Resolution: Fixed Fixed with revision 501921. PropertyReadMethodsTest.testIsSame leaks session

[jira] Created: (JCR-727) NamespaceRegistryTest uses an invalid URI as namespace URI

NamespaceRegistryTest uses an invalid URI as namespace URI -- Key: JCR-727 URL: https://issues.apache.org/jira/browse/JCR-727 Project: Jackrabbit Issue Type: Bug Components:

[jira] Resolved: (JCR-727) NamespaceRegistryTest uses an invalid URI as namespace URI

[ https://issues.apache.org/jira/browse/JCR-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-727. Resolution: Fixed Fixed with revision 502263. NamespaceRegistryTest uses an invalid URI as

[jira] Commented: (JCR-727) NamespaceRegistryTest uses an invalid URI as namespace URI

[ https://issues.apache.org/jira/browse/JCR-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469521 ] Julian Reschke commented on JCR-727: Just a nit: www.apache.org/... is a relative reference

[jira] Commented: (JCR-739) Predefined entity references are not decoded in string literal

[ https://issues.apache.org/jira/browse/JCR-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471730 ] Julian Reschke commented on JCR-739: Is this on the level of the JCR API? Why would we want to decode entity

[jira] Commented: (JCR-739) Predefined entity references are not decoded in string literal

[ https://issues.apache.org/jira/browse/JCR-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471986 ] Julian Reschke commented on JCR-739: Oops. I think JSR-170 is precise in that it's not an XQuery expression, but

[jira] Assigned: (JCR-741) Handling of multiple residual prop defs in EffectiveNodeTypeImpl

[ https://issues.apache.org/jira/browse/JCR-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reassigned JCR-741: -- Assignee: Julian Reschke Handling of multiple residual prop defs in EffectiveNodeTypeImpl

[jira] Commented: (JCR-741) Handling of multiple residual prop defs in EffectiveNodeTypeImpl

[ https://issues.apache.org/jira/browse/JCR-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474224 ] Julian Reschke commented on JCR-741: Fixing this properly requires several changes. (1) Do not consider multiple

[jira] Created: (JCR-752) Test cases leak sessions

Test cases leak sessions Key: JCR-752 URL: https://issues.apache.org/jira/browse/JCR-752 Project: Jackrabbit Issue Type: Bug Components: test Reporter: Julian Reschke Priority:

[jira] Created: (JCR-759) handling of namespace registrations in AbstractJCRTest

handling of namespace registrations in AbstractJCRTest -- Key: JCR-759 URL: https://issues.apache.org/jira/browse/JCR-759 Project: Jackrabbit Issue Type: Bug Components: JCR TCK

[jira] Commented: (JCR-741) Handling of multiple residual prop defs in EffectiveNodeTypeImpl

[ https://issues.apache.org/jira/browse/JCR-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475647 ] Julian Reschke commented on JCR-741: (1) Done earlier. (2) I just spent more time on this, and the key problem

[jira] Commented: (JCR-741) Handling of multiple residual prop defs in EffectiveNodeTypeImpl

[ https://issues.apache.org/jira/browse/JCR-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475858 ] Julian Reschke commented on JCR-741: - I do agree that we should avoid server round trips if the property

[jira] Commented: (JCR-741) Handling of multiple residual prop defs in EffectiveNodeTypeImpl

[ https://issues.apache.org/jira/browse/JCR-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476122 ] Julian Reschke commented on JCR-741: That would work, but why would the SPI implementation would ever need the

[jira] Commented: (JCR-741) Handling of multiple residual prop defs in EffectiveNodeTypeImpl

[ https://issues.apache.org/jira/browse/JCR-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476925 ] Julian Reschke commented on JCR-741: Not convinced. If the node type allows multiple property definitions here,

[jira] Commented: (JCR-741) Handling of multiple residual prop defs in EffectiveNodeTypeImpl

[ https://issues.apache.org/jira/browse/JCR-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478035 ] Julian Reschke commented on JCR-741: my point is to possibly avoid a call (by an spi implementation) to the store

[jira] Commented: (JCR-741) Handling of multiple residual prop defs in EffectiveNodeTypeImpl

[ https://issues.apache.org/jira/browse/JCR-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478798 ] Julian Reschke commented on JCR-741: OK, I've added the most simple thing that will work for my case in Revision

[jira] Commented: (JCR-779) Timeout for Session and/or Lock

[ https://issues.apache.org/jira/browse/JCR-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479292 ] Julian Reschke commented on JCR-779: I think lock timeouts are very valuable for open-scoped locks, if only for the

[jira] Created: (JCR-789) PathElement.equals doesn't handle INDEX_UNDEFINED

PathElement.equals doesn't handle INDEX_UNDEFINED - Key: JCR-789 URL: https://issues.apache.org/jira/browse/JCR-789 Project: Jackrabbit Issue Type: Bug Components: core

[jira] Updated: (JCR-789) PathElement.equals doesn't handle INDEX_UNDEFINED

[ https://issues.apache.org/jira/browse/JCR-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-789: --- Attachment: jcr789.diff.txt Proposed patch. PathElement.equals doesn't handle INDEX_UNDEFINED

[jira] Commented: (JCR-779) Timeout for Session and/or Lock

[ https://issues.apache.org/jira/browse/JCR-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481570 ] Julian Reschke commented on JCR-779: I don't think that option 1 is going to work well. It would introduce local

[jira] Commented: (JCR-779) Timeout for Session and/or Lock

[ https://issues.apache.org/jira/browse/JCR-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481599 ] Julian Reschke commented on JCR-779: I feared you would ask .-) For lock timeout, we would - need the ability to

[jira] Commented: (JCR-779) Timeout for Session and/or Lock

[ https://issues.apache.org/jira/browse/JCR-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481681 ] Julian Reschke commented on JCR-779: Actually, it probably will not be sufficient. The store I'm currently working

[jira] Created: (JCR-809) Misleading method names in SetValueBinaryTest

Misleading method names in SetValueBinaryTest - Key: JCR-809 URL: https://issues.apache.org/jira/browse/JCR-809 Project: Jackrabbit Issue Type: Improvement Components: JCR TCK

[jira] Resolved: (JCR-809) Misleading method names in SetValueBinaryTest

[ https://issues.apache.org/jira/browse/JCR-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-809. Resolution: Fixed Resolved with revision 521299. Misleading method names in SetValueBinaryTest

[jira] Closed: (JCR-809) Misleading method names in SetValueBinaryTest

[ https://issues.apache.org/jira/browse/JCR-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke closed JCR-809. -- Misleading method names in SetValueBinaryTest -

[jira] Created: (JCR-810) Typos in method names in test classes (SetPropertyAssumeTypeTest)

Typos in method names in test classes (SetPropertyAssumeTypeTest) - Key: JCR-810 URL: https://issues.apache.org/jira/browse/JCR-810 Project: Jackrabbit Issue Type: Improvement

[jira] Resolved: (JCR-810) Typos in method names in test classes (SetPropertyAssumeTypeTest)

[ https://issues.apache.org/jira/browse/JCR-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-810. Resolution: Fixed Fixed with revision 521310. Typos in method names in test classes

[jira] Closed: (JCR-810) Typos in method names in test classes (SetPropertyAssumeTypeTest)

[ https://issues.apache.org/jira/browse/JCR-810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke closed JCR-810. -- Typos in method names in test classes (SetPropertyAssumeTypeTest)

[jira] Created: (JCR-811) SetPropertyAssumeTypeTest check for non-protected string array property

SetPropertyAssumeTypeTest check for non-protected string array property --- Key: JCR-811 URL: https://issues.apache.org/jira/browse/JCR-811 Project: Jackrabbit Issue Type:

[jira] Commented: (JCR-801) Support for single-workspace repositories

[ https://issues.apache.org/jira/browse/JCR-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483228 ] Julian Reschke commented on JCR-801: More thoughts on this: - leaving javax.jcr.tck.workspacename undefined may be

[jira] Assigned: (JCR-801) Support for single-workspace repositories

[ https://issues.apache.org/jira/browse/JCR-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reassigned JCR-801: -- Assignee: Julian Reschke Support for single-workspace repositories

[jira] Resolved: (JCR-801) Support for single-workspace repositories

[ https://issues.apache.org/jira/browse/JCR-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-801. Resolution: Fixed Fixed with revision 521728. Support for single-workspace repositories

[jira] Created: (JCR-818) test granularity for calendar (date) properties

test granularity for calendar (date) properties --- Key: JCR-818 URL: https://issues.apache.org/jira/browse/JCR-818 Project: Jackrabbit Issue Type: Improvement Components: JCR TCK

[jira] Resolved: (JCR-818) test granularity for calendar (date) properties

[ https://issues.apache.org/jira/browse/JCR-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-818. Resolution: Fixed Turns out that this already is under the implementation's control, because what's

[jira] Closed: (JCR-818) test granularity for calendar (date) properties

[ https://issues.apache.org/jira/browse/JCR-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke closed JCR-818. -- test granularity for calendar (date) properties ---

[jira] Commented: (JCR-817) TCK vs available property types

[ https://issues.apache.org/jira/browse/JCR-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484445 ] Julian Reschke commented on JCR-817: After discussing this with Marcel, the new proposal is to have the affected

[jira] Commented: (JCR-817) TCK vs available property types

[ https://issues.apache.org/jira/browse/JCR-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484449 ] Julian Reschke commented on JCR-817: Revision 522894: add convenience method to AbstractJCRTest, use it in

[jira] Commented: (JCR-817) TCK vs available property types

[ https://issues.apache.org/jira/browse/JCR-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484482 ] Julian Reschke commented on JCR-817: Revision 522953: same for Double property related tests. TCK vs available

[jira] Commented: (JCR-817) TCK vs available property types

[ https://issues.apache.org/jira/browse/JCR-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484882 ] Julian Reschke commented on JCR-817: Revision 523341: same for ReferencesTest.java TCK vs available property

[jira] Updated: (JCR-823) NamespaceRegistryTest makes assumptions about legal names

[ https://issues.apache.org/jira/browse/JCR-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-823: --- Issue Type: Bug (was: Test) NamespaceRegistryTest makes assumptions about legal names

[jira] Updated: (JCR-826) NodeTest.testAddNodeConstraintViolationExceptionUndefinedNodeType relies on addNode(name, nt:base)

[ https://issues.apache.org/jira/browse/JCR-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-826: --- Issue Type: Bug (was: Test) NodeTest.testAddNodeConstraintViolationExceptionUndefinedNodeType relies

[jira] Closed: (JCR-827) SetValueFormatExceptiontest.testNode() relies on addMixin(), does not allow specification of node type

[ https://issues.apache.org/jira/browse/JCR-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke closed JCR-827. -- Resolution: Fixed Fixed with revision 523719. SetValueFormatExceptiontest.testNode() relies on

[jira] Created: (JCR-828) CheckPermissionTest-testCheckPermission() doesn't allow config of node type to be created

CheckPermissionTest-testCheckPermission() doesn't allow config of node type to be created - Key: JCR-828 URL: https://issues.apache.org/jira/browse/JCR-828

[jira] Resolved: (JCR-828) CheckPermissionTest-testCheckPermission() doesn't allow config of node type to be created

[ https://issues.apache.org/jira/browse/JCR-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-828. Resolution: Fixed Fixed with revision 523759. CheckPermissionTest-testCheckPermission() doesn't

[jira] Commented: (JCR-789) PathElement.equals doesn't handle INDEX_UNDEFINED

[ https://issues.apache.org/jira/browse/JCR-789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485342 ] Julian Reschke commented on JCR-789: BTW, is there even a need for the INDEX_UNDEFINED case? In other words, could

[jira] Created: (JCR-830) SetValueBinaryTest: some repositories have constraints on where binary properties can be set

SetValueBinaryTest: some repositories have constraints on where binary properties can be set Key: JCR-830 URL: https://issues.apache.org/jira/browse/JCR-830

[jira] Resolved: (JCR-830) SetValueBinaryTest: some repositories have constraints on where binary properties can be set

[ https://issues.apache.org/jira/browse/JCR-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-830. Resolution: Fixed Added with revision 524776. SetValueBinaryTest: some repositories have

[jira] Closed: (JCR-830) SetValueBinaryTest: some repositories have constraints on where binary properties can be set

[ https://issues.apache.org/jira/browse/JCR-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke closed JCR-830. -- SetValueBinaryTest: some repositories have constraints on where binary properties can be set

[jira] Updated: (JCR-838) bad assumptions/error handling in SetValueVersionExceptionTest:

[ 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

[jira] Assigned: (JCR-826) NodeTest.testAddNodeConstraintViolationExceptionUndefinedNodeType relies on addNode(name, nt:base)

[ 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

[jira] Commented: (JCR-826) NodeTest.testAddNodeConstraintViolationExceptionUndefinedNodeType relies on addNode(name, nt:base)

[ 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.

[jira] Closed: (JCR-842) support stores where binary properties are mandatory (such as in nt:resource)

[ https://issues.apache.org/jira/browse/JCR-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke closed JCR-842. -- support stores where binary properties are mandatory (such as in nt:resource)

[jira] Assigned: (JCR-842) support stores where binary properties are mandatory (such as in nt:resource)

[ https://issues.apache.org/jira/browse/JCR-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reassigned JCR-842: -- Assignee: Julian Reschke support stores where binary properties are mandatory (such as in

[jira] Created: (JCR-842) support stores where binary properties are mandatory (such as in nt:resource)

support stores where binary properties are mandatory (such as in nt:resource) - Key: JCR-842 URL: https://issues.apache.org/jira/browse/JCR-842 Project: Jackrabbit

[jira] Resolved: (JCR-842) support stores where binary properties are mandatory (such as in nt:resource)

[ https://issues.apache.org/jira/browse/JCR-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-842. Resolution: Fixed Resolved with revision 527952. support stores where binary properties are

[jira] Commented: (JCR-830) SetValueBinaryTest: some repositories have constraints on where binary properties can be set

[ https://issues.apache.org/jira/browse/JCR-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488396 ] Julian Reschke commented on JCR-830: Fixed for SetPropertyInputStreamTest.java in revision 527970.

[jira] Reopened: (JCR-842) support stores where binary properties are mandatory (such as in nt:resource)

[ https://issues.apache.org/jira/browse/JCR-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reopened JCR-842: Also applies to SetPropertyInputStreamTest.java. support stores where binary properties are mandatory

[jira] Resolved: (JCR-842) support stores where binary properties are mandatory (such as in nt:resource)

[ https://issues.apache.org/jira/browse/JCR-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-842. Resolution: Fixed Fixed for SetPropertyInputStreamTest.java in revision 527982. support stores

[jira] Assigned: (JCR-811) SetPropertyAssumeTypeTest check for non-protected string array property

[ https://issues.apache.org/jira/browse/JCR-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke reassigned JCR-811: -- Assignee: Julian Reschke SetPropertyAssumeTypeTest check for non-protected string array property

[jira] Commented: (JCR-838) bad assumptions/error handling in SetValueVersionExceptionTest:

[ https://issues.apache.org/jira/browse/JCR-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488662 ] Julian Reschke commented on JCR-838: Undid the change with revision 528478: addNode(xyz, null) has different

  1   2   3   4   5   6   7   8   9   10   >