You are viewing a plain text version of this content. The canonical link for it is here.
Posted to graffito-dev@incubator.apache.org by "Christophe Lombart (JIRA)" <ji...@apache.org> on 2007/02/15 21:50:05 UTC

[jira] Commented: (GRFT-40) Advanced support for JCR properties and node

    [ https://issues.apache.org/jira/browse/GRFT-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473526 ] 

Christophe Lombart commented on GRFT-40:
----------------------------------------

I just commit ed a couple of modifications : 
Name & path property types are supported with new atomic converter. They are mapped into String attribute (see ReferenceTypeConverterImpl & PathTypeConverterImpl) 
 
A couple a month ago, we added those features :
1/node.getNodes(nodepattern)  is partially supported  with a collection converter : NTCollectionConverterImpl
2/support for mandotory & autocreated props
3/Support for same-name siblings is done

In summary, we have to work on the following issues:
UUID support
Reference
Undefined type

Tomorrow,I will create subtasks for each issues

> Advanced support for JCR properties and node
> --------------------------------------------
>
>                 Key: GRFT-40
>                 URL: https://issues.apache.org/jira/browse/GRFT-40
>             Project: Graffito
>          Issue Type: Task
>          Components: JCR-Mapping
>            Reporter: Christophe Lombart
>         Assigned To: Christophe Lombart
>             Fix For: 1.0-a1-dev
>
>
> - We have to support the following JCR Types : 
>            * PropertyType.NAME
>            * PropertyType.PATH
>            * PropertyType.REFERENCE
>            * PropertyType.UNDEFINED
> - Map UUID and the path into the POJO object
> - Check if  mandatory & auto created properties are well managed. More unit test are required.
> - Support for same-name siblings : the query service should supported it ans we have also to support the method :  node.getNodes(nodepattern). We have also to check if the insert, update and delete methods support correctly the same-name sibling. 

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