[jira] Updated: (JCR-2192) handling of expanded-form jcr names by node type *Template classes

["Stefan Guggisberg (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JCR-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Guggisberg updated JCR-2192:
-----------------------------------

    Component/s:     (was: jackrabbit-core)
                 jackrabbit-spi-commons
        Summary: handling of expanded-form jcr names by node type *Template classes   (was: ItemDefinitionTemplate treats name as opaque, not a JCR name)

not sure whether i agree. 

IIRC *Template classes were intended to be simple bean classes with setter/getters, i.e. not necessarily session ns-mapping aware. 

however, the following methods would be affected:

package o.a.jackrabbit.spi.commons.nodetype:

AbstractItemDefinitionTemplate#getName()
NodeDefinitionTemplateImpl#getRequiredPrimaryTypeNames()
NodeDefinitionTemplateImpl#getDefaultPrimaryTypeName()
NodeTypeTemplateImpl#getName()
NodeTypeTemplateImpl#getDeclaredSupertypeNames()
NodeTypeTemplateImpl#getPrimaryItemName()


> handling of expanded-form jcr names by node type *Template classes 
> -------------------------------------------------------------------
>
>                 Key: JCR-2192
>                 URL: https://issues.apache.org/jira/browse/JCR-2192
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-spi-commons
>            Reporter: Julian Reschke
>
> ItemDefinitionTemplate treats the name as opque string, instead of a JCR Name.
> Example: when setting the name to
>   "{http://example.org/}foo"
> then getName() needs to return
>   "bar:foo"
> which the prefix "bar" being mapped to the namesapce "http://example.org/".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.