You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Stefan Guggisberg (JIRA)" <ji...@apache.org> on 2005/03/14 15:01:09 UTC
[jira] Commented: (JCR-61) Docview import fails, if attribute and childelem have same name
[ http://issues.apache.org/jira/browse/JCR-61?page=comments#action_60752 ]
Stefan Guggisberg commented on JCR-61:
--------------------------------------
i was wrong, this is not a specification issue.
=======================================
quote from the specification:
7.3.2 Import from Document View
...
10. An XML element can have a child element and an attribute with the same name while a JCR node cannot have a child node and property with the same name. For example, <a b="x"><b/></a> would imply a JCR node with one property called b and one child node also called b, which is not allowed. Therefore if such a fragment of XML is encountered on import it is an implementation issue as to how to deal with it.
=======================================
so the current behaviour (ItemExistsException) is accordance with the spec
("is an implementation issue as to how to deal with it").
but i guess we will have to come up with a way to import such xml fragments
(e.g. with a child node construct that represents a 'colliding' property,
similar to jcr:xmltext for character data)
> Docview import fails, if attribute and childelem have same name
> ---------------------------------------------------------------
>
> Key: JCR-61
> URL: http://issues.apache.org/jira/browse/JCR-61
> Project: Jackrabbit
> Type: Bug
> Components: xml
> Environment: jackrabbit r157173
> Reporter: Tobias Strasser
> Assignee: Stefan Guggisberg
>
> docimport fails, if element has same name as one of the attributes of its parent element.
> example:
> <?xml version="1.0" encoding="UTF-8"?>
> <feature plugin="foobar">
> <plugin>test</plugin>
> </feature>
> importing this results in a ItemExistsException: 'plugin'
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira