You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2007/03/30 18:43:25 UTC
[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
Project: Jackrabbit
Issue Type: Improvement
Components: JCR TCK
Reporter: Julian Reschke
Assigned To: Julian Reschke
Priority: Minor
For repositories that do only support binary properties in the form of jcr:content/jcr:data, the current configurability is not sufficient. To avoid more config params, I'd suggest to check for propertyName1 == "jcr:data" && node.hasNode("jcr:content"), and in that case to automatically navigate down to the "jcr:content" child node.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-830) SetValueBinaryTest: some repositories
have constraints on where binary properties can be set
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488394 ]
Julian Reschke commented on JCR-830:
------------------------------------
Also affects SetPropertyInputStreamTest.java.
> SetValueBinaryTest: some repositories have constraints on where binary properties can be set
> --------------------------------------------------------------------------------------------
>
> Key: JCR-830
> URL: https://issues.apache.org/jira/browse/JCR-830
> Project: Jackrabbit
> Issue Type: Improvement
> Components: JCR TCK
> Reporter: Julian Reschke
> Assigned To: Julian Reschke
> Priority: Minor
> Fix For: 1.3
>
> Attachments: diff.txt
>
>
> For repositories that do only support binary properties in the form of jcr:content/jcr:data, the current configurability is not sufficient. To avoid more config params, I'd suggest to check for propertyName1 == "jcr:data" && node.hasNode("jcr:content"), and in that case to automatically navigate down to the "jcr:content" child node.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-830) SetValueBinaryTest: some repositories
have constraints on where binary properties can be set
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke updated JCR-830:
-------------------------------
Attachment: diff.txt
Proposed patch.
> SetValueBinaryTest: some repositories have constraints on where binary properties can be set
> --------------------------------------------------------------------------------------------
>
> Key: JCR-830
> URL: https://issues.apache.org/jira/browse/JCR-830
> Project: Jackrabbit
> Issue Type: Improvement
> Components: JCR TCK
> Reporter: Julian Reschke
> Assigned To: Julian Reschke
> Priority: Minor
> Attachments: diff.txt
>
>
> For repositories that do only support binary properties in the form of jcr:content/jcr:data, the current configurability is not sufficient. To avoid more config params, I'd suggest to check for propertyName1 == "jcr:data" && node.hasNode("jcr:content"), and in that case to automatically navigate down to the "jcr:content" child node.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-830) SetValueBinaryTest: some repositories
have constraints on where binary properties can be set
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ 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 constraints on where binary properties can be set
> --------------------------------------------------------------------------------------------
>
> Key: JCR-830
> URL: https://issues.apache.org/jira/browse/JCR-830
> Project: Jackrabbit
> Issue Type: Improvement
> Components: JCR TCK
> Reporter: Julian Reschke
> Assigned To: Julian Reschke
> Priority: Minor
> Attachments: diff.txt
>
>
> For repositories that do only support binary properties in the form of jcr:content/jcr:data, the current configurability is not sufficient. To avoid more config params, I'd suggest to check for propertyName1 == "jcr:data" && node.hasNode("jcr:content"), and in that case to automatically navigate down to the "jcr:content" child node.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-830) SetValueBinaryTest: some repositories
have constraints on where binary properties can be set
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ 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.
> SetValueBinaryTest: some repositories have constraints on where binary properties can be set
> --------------------------------------------------------------------------------------------
>
> Key: JCR-830
> URL: https://issues.apache.org/jira/browse/JCR-830
> Project: Jackrabbit
> Issue Type: Improvement
> Components: JCR TCK
> Reporter: Julian Reschke
> Assigned To: Julian Reschke
> Priority: Minor
> Fix For: 1.3
>
> Attachments: diff.txt
>
>
> For repositories that do only support binary properties in the form of jcr:content/jcr:data, the current configurability is not sufficient. To avoid more config params, I'd suggest to check for propertyName1 == "jcr:data" && node.hasNode("jcr:content"), and in that case to automatically navigate down to the "jcr:content" child node.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-830) SetValueBinaryTest: some repositories
have constraints on where binary properties can be set
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-830.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.3
> SetValueBinaryTest: some repositories have constraints on where binary properties can be set
> --------------------------------------------------------------------------------------------
>
> Key: JCR-830
> URL: https://issues.apache.org/jira/browse/JCR-830
> Project: Jackrabbit
> Issue Type: Improvement
> Components: JCR TCK
> Reporter: Julian Reschke
> Assigned To: Julian Reschke
> Priority: Minor
> Fix For: 1.3
>
> Attachments: diff.txt
>
>
> For repositories that do only support binary properties in the form of jcr:content/jcr:data, the current configurability is not sufficient. To avoid more config params, I'd suggest to check for propertyName1 == "jcr:data" && node.hasNode("jcr:content"), and in that case to automatically navigate down to the "jcr:content" child node.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (JCR-830) SetValueBinaryTest: some repositories
have constraints on where binary properties can be set
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting reopened JCR-830:
-------------------------------
Reopening to change metadata
> SetValueBinaryTest: some repositories have constraints on where binary properties can be set
> --------------------------------------------------------------------------------------------
>
> Key: JCR-830
> URL: https://issues.apache.org/jira/browse/JCR-830
> Project: Jackrabbit
> Issue Type: Improvement
> Components: JCR TCK
> Reporter: Julian Reschke
> Assigned To: Julian Reschke
> Priority: Minor
> Fix For: 1.3
>
> Attachments: diff.txt
>
>
> For repositories that do only support binary properties in the form of jcr:content/jcr:data, the current configurability is not sufficient. To avoid more config params, I'd suggest to check for propertyName1 == "jcr:data" && node.hasNode("jcr:content"), and in that case to automatically navigate down to the "jcr:content" child node.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (JCR-830) SetValueBinaryTest: some repositories have
constraints on where binary properties can be set
Posted by "Julian Reschke (JIRA)" <ji...@apache.org>.
[ 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
> --------------------------------------------------------------------------------------------
>
> Key: JCR-830
> URL: https://issues.apache.org/jira/browse/JCR-830
> Project: Jackrabbit
> Issue Type: Improvement
> Components: JCR TCK
> Reporter: Julian Reschke
> Assigned To: Julian Reschke
> Priority: Minor
> Attachments: diff.txt
>
>
> For repositories that do only support binary properties in the form of jcr:content/jcr:data, the current configurability is not sufficient. To avoid more config params, I'd suggest to check for propertyName1 == "jcr:data" && node.hasNode("jcr:content"), and in that case to automatically navigate down to the "jcr:content" child node.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.