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 "Oliver Kießler (JIRA)" <ji...@apache.org> on 2005/11/21 06:25:41 UTC
[jira] Created: (GRFT-78) Add additional attributes to jcr-mapping xml file
Add additional attributes to jcr-mapping xml file
-------------------------------------------------
Key: GRFT-78
URL: http://issues.apache.org/jira/browse/GRFT-78
Project: Graffito
Type: Improvement
Components: JCR-Mapping
Versions: 1.0-a1-dev
Reporter: Oliver Kießler
Assigned to: Oliver Kießler
Fix For: 1.0-a1-dev
Here is a list of additional attributes that are needed for JCR node type creation from the jcr-mapping file:
class-descriptor
- jcrSuperTypes (comma separated list of jcr node supertypes) I am not so sure if this should be used, we might end up with conflicts...)
field-descriptor
- jcrType (jcr type that is supposed to be used, if the jcr-node management has access to the java class I could use reflection but is that always the case? Maybe the java classes are not in the classpath during node type creation...)
- jcrAutoCreated (boolean) default is "false" if not specified in jcr-mapping file
- jcrMandatory (boolean) default is "false" if not specified in jcr-mapping file
- jcrOnParentVersion default is "IGNORE" if not specified
- jcrProtected (boolean) default is "false" if not specified
- jcrMultiple (boolean) default is "false" if not specified
bean-descriptor:
- jcrNodeType (defines the child node type)
- jcrAutoCreated (boolean) default is "false" if not specified in jcr-mapping file
- jcrMandatory (boolean) default is "false" if not specified
- jcrOnParentVersion default is "IGNORE" if not specified
- jcrProtected (boolean) default is "false" if not specified
- jcrSameNameSiblings (boolean) default is "false" if not specified
collection-descriptor:
- jcrNodeType (defines the child node type)
- jcrAutoCreated (boolean) default is "false" if not specified in jcr-mapping file
- jcrMandatory (boolean) default is "false" if not specified
- jcrOnParentVersion default is "IGNORE" if not specified
- jcrProtected (boolean) default is "false" if not specified
- jcrSameNameSiblings (boolean) default is "false" if not specified
Have a look at GRFT-67 also.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GRFT-78) Add additional attributes to jcr-mapping xml file
Posted by "Sandro Boehme (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-78?page=comments#action_12358699 ]
Sandro Boehme commented on GRFT-78:
-----------------------------------
You can have an own component which uses JDK 1.5 to generate the XML file from annotations. The registration component can use JDK 1.4 and read the generated XML file. But this is just one example to give others the possibility to use the registration component.
> Add additional attributes to jcr-mapping xml file
> -------------------------------------------------
>
> Key: GRFT-78
> URL: http://issues.apache.org/jira/browse/GRFT-78
> Project: Graffito
> Type: Improvement
> Components: JCR-Mapping
> Versions: 1.0-a1-dev
> Reporter: Oliver Kießler
> Assignee: Oliver Kießler
> Fix For: 1.0-a1-dev
>
> Here is a list of additional attributes that are needed for JCR node type creation from the jcr-mapping file:
> class-descriptor
> - jcrSuperTypes (comma separated list of jcr node supertypes) I am not so sure if this should be used, we might end up with conflicts...)
> field-descriptor
> - jcrType (jcr type that is supposed to be used, if the jcr-node management has access to the java class I could use reflection but is that always the case? Maybe the java classes are not in the classpath during node type creation...)
> - jcrAutoCreated (boolean) default is "false" if not specified in jcr-mapping file
> - jcrMandatory (boolean) default is "false" if not specified in jcr-mapping file
> - jcrOnParentVersion default is "IGNORE" if not specified
> - jcrProtected (boolean) default is "false" if not specified
> - jcrMultiple (boolean) default is "false" if not specified
> bean-descriptor:
> - jcrNodeType (defines the child node type)
> - jcrAutoCreated (boolean) default is "false" if not specified in jcr-mapping file
> - jcrMandatory (boolean) default is "false" if not specified
> - jcrOnParentVersion default is "IGNORE" if not specified
> - jcrProtected (boolean) default is "false" if not specified
> - jcrSameNameSiblings (boolean) default is "false" if not specified
> collection-descriptor:
> - jcrNodeType (defines the child node type)
> - jcrAutoCreated (boolean) default is "false" if not specified in jcr-mapping file
> - jcrMandatory (boolean) default is "false" if not specified
> - jcrOnParentVersion default is "IGNORE" if not specified
> - jcrProtected (boolean) default is "false" if not specified
> - jcrSameNameSiblings (boolean) default is "false" if not specified
> Have a look at GRFT-67 also.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GRFT-78) Add additional attributes to jcr-mapping xml file
Posted by "Sandro Boehme (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-78?page=comments#action_12358129 ]
Sandro Boehme commented on GRFT-78:
-----------------------------------
It's maybe a little late but it adds much complexity to the mapping file and people like Brian Moseley could not have the node type registration bundled separately.
If you generate the xml data from lets say annotations in the code, you would need to merge it with the other data in the mapping file.
My node type registration works with XMLBeans now. So if you want, we can use that for a starting point and if it's stabalized we can later
switch to Digester.
> Add additional attributes to jcr-mapping xml file
> -------------------------------------------------
>
> Key: GRFT-78
> URL: http://issues.apache.org/jira/browse/GRFT-78
> Project: Graffito
> Type: Improvement
> Components: JCR-Mapping
> Versions: 1.0-a1-dev
> Reporter: Oliver Kießler
> Assignee: Oliver Kießler
> Fix For: 1.0-a1-dev
>
> Here is a list of additional attributes that are needed for JCR node type creation from the jcr-mapping file:
> class-descriptor
> - jcrSuperTypes (comma separated list of jcr node supertypes) I am not so sure if this should be used, we might end up with conflicts...)
> field-descriptor
> - jcrType (jcr type that is supposed to be used, if the jcr-node management has access to the java class I could use reflection but is that always the case? Maybe the java classes are not in the classpath during node type creation...)
> - jcrAutoCreated (boolean) default is "false" if not specified in jcr-mapping file
> - jcrMandatory (boolean) default is "false" if not specified in jcr-mapping file
> - jcrOnParentVersion default is "IGNORE" if not specified
> - jcrProtected (boolean) default is "false" if not specified
> - jcrMultiple (boolean) default is "false" if not specified
> bean-descriptor:
> - jcrNodeType (defines the child node type)
> - jcrAutoCreated (boolean) default is "false" if not specified in jcr-mapping file
> - jcrMandatory (boolean) default is "false" if not specified
> - jcrOnParentVersion default is "IGNORE" if not specified
> - jcrProtected (boolean) default is "false" if not specified
> - jcrSameNameSiblings (boolean) default is "false" if not specified
> collection-descriptor:
> - jcrNodeType (defines the child node type)
> - jcrAutoCreated (boolean) default is "false" if not specified in jcr-mapping file
> - jcrMandatory (boolean) default is "false" if not specified
> - jcrOnParentVersion default is "IGNORE" if not specified
> - jcrProtected (boolean) default is "false" if not specified
> - jcrSameNameSiblings (boolean) default is "false" if not specified
> Have a look at GRFT-67 also.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (GRFT-78) Add additional attributes to jcr-mapping xml file
Posted by "Oliver Kießler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-78?page=all ]
Oliver Kießler resolved GRFT-78:
--------------------------------
Resolution: Fixed
> Add additional attributes to jcr-mapping xml file
> -------------------------------------------------
>
> Key: GRFT-78
> URL: http://issues.apache.org/jira/browse/GRFT-78
> Project: Graffito
> Type: Improvement
> Components: JCR-Mapping
> Versions: 1.0-a1-dev
> Reporter: Oliver Kießler
> Assignee: Oliver Kießler
> Fix For: 1.0-a1-dev
>
> Here is a list of additional attributes that are needed for JCR node type creation from the jcr-mapping file:
> class-descriptor
> - jcrSuperTypes (comma separated list of jcr node supertypes) I am not so sure if this should be used, we might end up with conflicts...)
> field-descriptor
> - jcrType (jcr type that is supposed to be used, if the jcr-node management has access to the java class I could use reflection but is that always the case? Maybe the java classes are not in the classpath during node type creation...)
> - jcrAutoCreated (boolean) default is "false" if not specified in jcr-mapping file
> - jcrMandatory (boolean) default is "false" if not specified in jcr-mapping file
> - jcrOnParentVersion default is "IGNORE" if not specified
> - jcrProtected (boolean) default is "false" if not specified
> - jcrMultiple (boolean) default is "false" if not specified
> bean-descriptor:
> - jcrNodeType (defines the child node type)
> - jcrAutoCreated (boolean) default is "false" if not specified in jcr-mapping file
> - jcrMandatory (boolean) default is "false" if not specified
> - jcrOnParentVersion default is "IGNORE" if not specified
> - jcrProtected (boolean) default is "false" if not specified
> - jcrSameNameSiblings (boolean) default is "false" if not specified
> collection-descriptor:
> - jcrNodeType (defines the child node type)
> - jcrAutoCreated (boolean) default is "false" if not specified in jcr-mapping file
> - jcrMandatory (boolean) default is "false" if not specified
> - jcrOnParentVersion default is "IGNORE" if not specified
> - jcrProtected (boolean) default is "false" if not specified
> - jcrSameNameSiblings (boolean) default is "false" if not specified
> Have a look at GRFT-67 also.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (GRFT-78) Add additional attributes to jcr-mapping xml file
Posted by "Oliver Kießler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-78?page=comments#action_12358131 ]
Oliver Kießler commented on GRFT-78:
------------------------------------
I like the idea of using Annotations but I think graffito is a JDK 1.4 project only, is it?
> Add additional attributes to jcr-mapping xml file
> -------------------------------------------------
>
> Key: GRFT-78
> URL: http://issues.apache.org/jira/browse/GRFT-78
> Project: Graffito
> Type: Improvement
> Components: JCR-Mapping
> Versions: 1.0-a1-dev
> Reporter: Oliver Kießler
> Assignee: Oliver Kießler
> Fix For: 1.0-a1-dev
>
> Here is a list of additional attributes that are needed for JCR node type creation from the jcr-mapping file:
> class-descriptor
> - jcrSuperTypes (comma separated list of jcr node supertypes) I am not so sure if this should be used, we might end up with conflicts...)
> field-descriptor
> - jcrType (jcr type that is supposed to be used, if the jcr-node management has access to the java class I could use reflection but is that always the case? Maybe the java classes are not in the classpath during node type creation...)
> - jcrAutoCreated (boolean) default is "false" if not specified in jcr-mapping file
> - jcrMandatory (boolean) default is "false" if not specified in jcr-mapping file
> - jcrOnParentVersion default is "IGNORE" if not specified
> - jcrProtected (boolean) default is "false" if not specified
> - jcrMultiple (boolean) default is "false" if not specified
> bean-descriptor:
> - jcrNodeType (defines the child node type)
> - jcrAutoCreated (boolean) default is "false" if not specified in jcr-mapping file
> - jcrMandatory (boolean) default is "false" if not specified
> - jcrOnParentVersion default is "IGNORE" if not specified
> - jcrProtected (boolean) default is "false" if not specified
> - jcrSameNameSiblings (boolean) default is "false" if not specified
> collection-descriptor:
> - jcrNodeType (defines the child node type)
> - jcrAutoCreated (boolean) default is "false" if not specified in jcr-mapping file
> - jcrMandatory (boolean) default is "false" if not specified
> - jcrOnParentVersion default is "IGNORE" if not specified
> - jcrProtected (boolean) default is "false" if not specified
> - jcrSameNameSiblings (boolean) default is "false" if not specified
> Have a look at GRFT-67 also.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira