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/10/30 20:15:56 UTC
[jira] Created: (GRFT-67) Definition of Nodetype Management API
Definition of Nodetype Management API
-------------------------------------
Key: GRFT-67
URL: http://issues.apache.org/jira/browse/GRFT-67
Project: Graffito
Type: Task
Components: JCR-Nodemanagement
Versions: 1.0-a1-dev
Reporter: Oliver Kießler
Assigned to: Oliver Kießler
Fix For: 1.0-a1-dev
Definition of the "nodemanagement API" in the org.apache.portals.graffito.jcr.nodemanagement.NodeTypeManager interface.
--
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
Re: [jira] Commented: (GRFT-67) Definition of Nodetype Management API
Posted by Christophe Lombart <ch...@gmail.com>.
ok thanks for your answer - Now I see how it will work . This sounds
good for me.
Christophe
On 11/12/05, Oliver Kießler (JIRA) <ji...@apache.org> wrote:
> [ http://issues.apache.org/jira/browse/GRFT-67?page=comments#action_12357507 ]
>
> Oliver Kießler commented on GRFT-67:
> ------------------------------------
>
> Following last comment by Christophe:
>
> 1. A: The jcr-mapping file can be used to create JCR node types (see method "createNodeTypesFromMappingFiles" and others). It does not have to be converted into the custom_nodetypes.xml file (in case of jackrabbit) but rather converted into the correct Definition objects (implementations of ItemDefinition, NodeDefinition and PropertyDefinition) to create JCR node types. Converting the XML is not necessary.
>
> 1. B: This will be supported by the "createNodeTypesFromConfiguration" method that takes a vendor specific configuration file as input (and throws an exception if it is not supported by a JCR repository implementation).
>
> 1. C: As far as I know Jeceira and Exo are both GPL licensed, so I guess we can't support them anyways, can we?
>
> 2. See 1. C.
>
> I would like to avoid having to deal with two xml files to create JCR node types (jcr-mapping file *and* a vendor specific file). I would appreciate it if we could add the missing information to the jcr-mapping file if that makes sense. I will have to find out what kind of information is missing though.
>
> > Definition of Nodetype Management API
> > -------------------------------------
> >
> > Key: GRFT-67
> > URL: http://issues.apache.org/jira/browse/GRFT-67
> > Project: Graffito
> > Type: Task
> > Components: JCR-Nodemanagement
> > Versions: 1.0-a1-dev
> > Reporter: Oliver Kießler
> > Assignee: Oliver Kießler
> > Fix For: 1.0-a1-dev
>
> >
> > Definition of the "nodemanagement API" in the org.apache.portals.graffito.jcr.nodemanagement.NodeTypeManager interface.
>
> --
> 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
>
>
Re: [jira] Commented: (GRFT-67) Definition of Nodetype Management API
Posted by Christophe Lombart <ch...@gmail.com>.
No comment - You can add them.
Thanks,
Christophe
On 11/20/05, Oliver Kießler (JIRA) <ji...@apache.org> wrote:
> [ http://issues.apache.org/jira/browse/GRFT-67?page=comments#action_12358104 ]
>
> Oliver Kießler commented on GRFT-67:
> ------------------------------------
>
> 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
>
> I think that's it. There are more attributes in the jackrabbit nodetypes xml file and the JCR spec but I think these are the attributes that are sufficant for jcr-mapping and jcr-nodemanagement. Please comment if these attributes can be added to the jcr-mapping file or if I missed something...
>
> > Definition of Nodetype Management API
> > -------------------------------------
> >
> > Key: GRFT-67
> > URL: http://issues.apache.org/jira/browse/GRFT-67
> > Project: Graffito
> > Type: Task
> > Components: JCR-Nodemanagement
> > Versions: 1.0-a1-dev
> > Reporter: Oliver Kießler
> > Assignee: Oliver Kießler
> > Fix For: 1.0-a1-dev
>
> >
> > Definition of the "nodemanagement API" in the org.apache.portals.graffito.jcr.nodemanagement.NodeTypeManager interface.
>
> --
> 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-67) Definition of Nodetype Management API
Posted by "Oliver Kießler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-67?page=comments#action_12356982 ]
Oliver Kießler commented on GRFT-67:
------------------------------------
1) You are right, currently the jcr mapping file is not sufficant unless we work with defaults if that's possible. Maybe we should add these attributes but then the jcr mapping file and the custom_nodetypes.xml will not be much different...
2) I could implement the custom_nodetypes.xml import in the Jackrabbit Node Type Manager implementation (and keep that method out of the interface). I know Jeceira also supports this xml format but others might not... That's another question: Do we want to support other JCR implementations (like Jeceira, Exo...) or do we want to focus on Jackrabbit only?
> Definition of Nodetype Management API
> -------------------------------------
>
> Key: GRFT-67
> URL: http://issues.apache.org/jira/browse/GRFT-67
> Project: Graffito
> Type: Task
> Components: JCR-Nodemanagement
> Versions: 1.0-a1-dev
> Reporter: Oliver Kießler
> Assignee: Oliver Kießler
> Fix For: 1.0-a1-dev
>
> Definition of the "nodemanagement API" in the org.apache.portals.graffito.jcr.nodemanagement.NodeTypeManager interface.
--
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-67) Definition of Nodetype Management API
Posted by "Oliver Kießler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-67?page=comments#action_12356527 ]
Oliver Kießler commented on GRFT-67:
------------------------------------
I just commited my first version of the JCR Node Type Management API. Please have a look at the NodeTypeManager interface and let me know what you think about it, what you are missing or what you want to have added to it.
> Definition of Nodetype Management API
> -------------------------------------
>
> Key: GRFT-67
> URL: http://issues.apache.org/jira/browse/GRFT-67
> Project: Graffito
> Type: Task
> Components: JCR-Nodemanagement
> Versions: 1.0-a1-dev
> Reporter: Oliver Kießler
> Assignee: Oliver Kießler
> Fix For: 1.0-a1-dev
>
> Definition of the "nodemanagement API" in the org.apache.portals.graffito.jcr.nodemanagement.NodeTypeManager interface.
--
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-67) Definition of Nodetype Management API
Posted by "Oliver Kießler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-67?page=comments#action_12357507 ]
Oliver Kießler commented on GRFT-67:
------------------------------------
Following last comment by Christophe:
1. A: The jcr-mapping file can be used to create JCR node types (see method "createNodeTypesFromMappingFiles" and others). It does not have to be converted into the custom_nodetypes.xml file (in case of jackrabbit) but rather converted into the correct Definition objects (implementations of ItemDefinition, NodeDefinition and PropertyDefinition) to create JCR node types. Converting the XML is not necessary.
1. B: This will be supported by the "createNodeTypesFromConfiguration" method that takes a vendor specific configuration file as input (and throws an exception if it is not supported by a JCR repository implementation).
1. C: As far as I know Jeceira and Exo are both GPL licensed, so I guess we can't support them anyways, can we?
2. See 1. C.
I would like to avoid having to deal with two xml files to create JCR node types (jcr-mapping file *and* a vendor specific file). I would appreciate it if we could add the missing information to the jcr-mapping file if that makes sense. I will have to find out what kind of information is missing though.
> Definition of Nodetype Management API
> -------------------------------------
>
> Key: GRFT-67
> URL: http://issues.apache.org/jira/browse/GRFT-67
> Project: Graffito
> Type: Task
> Components: JCR-Nodemanagement
> Versions: 1.0-a1-dev
> Reporter: Oliver Kießler
> Assignee: Oliver Kießler
> Fix For: 1.0-a1-dev
>
> Definition of the "nodemanagement API" in the org.apache.portals.graffito.jcr.nodemanagement.NodeTypeManager interface.
--
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-67) Definition of Nodetype Management API
Posted by "Oliver Kießler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-67?page=comments#action_12356667 ]
Oliver Kießler commented on GRFT-67:
------------------------------------
1) You are right, we need to update to the latest Jackrabbit snapshot jar some time soon. I will take care of that and update the maven project file.
2) I have updated the NodeTypeManager interface to support multiple mapping files now. Please have a look at it.
3) In order to get to a JCR NodeTypeRegistry you need to have an established repository session and optain it through a Workspace object. Custom node types are available repository wide.
The graffito-jcr NodeTypeManager is intended to manage JCR nodes programmatically. You can use the NodeTypeManager in conjunction with graffito jcr-mapping. We could also come up with Ant tasks etc. that are built on top of the NodeTypeManager. I would like to pass a repository session to the NodeTypeManager and not let the NodeTypeManager create it himself. The NodeTypeManager should not contain any logic about how and where to get to a JCR repository session.
> Definition of Nodetype Management API
> -------------------------------------
>
> Key: GRFT-67
> URL: http://issues.apache.org/jira/browse/GRFT-67
> Project: Graffito
> Type: Task
> Components: JCR-Nodemanagement
> Versions: 1.0-a1-dev
> Reporter: Oliver Kießler
> Assignee: Oliver Kießler
> Fix For: 1.0-a1-dev
>
> Definition of the "nodemanagement API" in the org.apache.portals.graffito.jcr.nodemanagement.NodeTypeManager interface.
--
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-67) Definition of Nodetype Management API
Posted by "Oliver Kießler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-67?page=comments#action_12357140 ]
Oliver Kießler commented on GRFT-67:
------------------------------------
@Sandro: I don't think I am going to use XMLBeans (rather Commons Digester) but if you have any useful code I'd be happy to have a look at it.
> Definition of Nodetype Management API
> -------------------------------------
>
> Key: GRFT-67
> URL: http://issues.apache.org/jira/browse/GRFT-67
> Project: Graffito
> Type: Task
> Components: JCR-Nodemanagement
> Versions: 1.0-a1-dev
> Reporter: Oliver Kießler
> Assignee: Oliver Kießler
> Fix For: 1.0-a1-dev
>
> Definition of the "nodemanagement API" in the org.apache.portals.graffito.jcr.nodemanagement.NodeTypeManager interface.
--
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-67) Definition of Nodetype Management API
Posted by "Sandro Boehme (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-67?page=comments#action_12357205 ]
Sandro Boehme commented on GRFT-67:
-----------------------------------
It's nice to see you working on that issue. I will have a look on you code as soon as possible and hope to be able to merge my
code into your API for not loosing my information about the registration. If you want I could call you to discuss some details. Maybe at the end of the next week?
> Definition of Nodetype Management API
> -------------------------------------
>
> Key: GRFT-67
> URL: http://issues.apache.org/jira/browse/GRFT-67
> Project: Graffito
> Type: Task
> Components: JCR-Nodemanagement
> Versions: 1.0-a1-dev
> Reporter: Oliver Kießler
> Assignee: Oliver Kießler
> Fix For: 1.0-a1-dev
>
> Definition of the "nodemanagement API" in the org.apache.portals.graffito.jcr.nodemanagement.NodeTypeManager interface.
--
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-67) Definition of Nodetype Management API
Posted by "Sandro Boehme (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-67?page=comments#action_12358130 ]
Sandro Boehme commented on GRFT-67:
-----------------------------------
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.
> Definition of Nodetype Management API
> -------------------------------------
>
> Key: GRFT-67
> URL: http://issues.apache.org/jira/browse/GRFT-67
> Project: Graffito
> Type: Task
> Components: JCR-Nodemanagement
> Versions: 1.0-a1-dev
> Reporter: Oliver Kießler
> Assignee: Oliver Kießler
> Fix For: 1.0-a1-dev
>
> Definition of the "nodemanagement API" in the org.apache.portals.graffito.jcr.nodemanagement.NodeTypeManager interface.
--
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-67) Definition of Nodetype Management API
Posted by "Martin Koci (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-67?page=comments#action_12356607 ]
Martin Koci commented on GRFT-67:
---------------------------------
1) Jackrabbit maven build produces only one jar jackrabbit-1.0-snapshot placed in org.apache.jackrabbit. See issue "revert the great split" in jackrabbit mailing list.
2) I dont see simple method for loading nodetypes from xml containing multiple definitions
3) When to perform registration? Instace of workspace is needed so a user must be logged in, but nodetypes definitions are repository-wide.
Thanks,
Martin
> Definition of Nodetype Management API
> -------------------------------------
>
> Key: GRFT-67
> URL: http://issues.apache.org/jira/browse/GRFT-67
> Project: Graffito
> Type: Task
> Components: JCR-Nodemanagement
> Versions: 1.0-a1-dev
> Reporter: Oliver Kießler
> Assignee: Oliver Kießler
> Fix For: 1.0-a1-dev
>
> Definition of the "nodemanagement API" in the org.apache.portals.graffito.jcr.nodemanagement.NodeTypeManager interface.
--
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-67) Definition of Nodetype Management API
Posted by "Sandro Boehme (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-67?page=comments#action_12356984 ]
Sandro Boehme commented on GRFT-67:
-----------------------------------
I started refactoring the initial node type registration with XMLBeans. But I cannot promise to finish it in this month. So if somebody has more spare time I would hand it out.
> Definition of Nodetype Management API
> -------------------------------------
>
> Key: GRFT-67
> URL: http://issues.apache.org/jira/browse/GRFT-67
> Project: Graffito
> Type: Task
> Components: JCR-Nodemanagement
> Versions: 1.0-a1-dev
> Reporter: Oliver Kießler
> Assignee: Oliver Kießler
> Fix For: 1.0-a1-dev
>
> Definition of the "nodemanagement API" in the org.apache.portals.graffito.jcr.nodemanagement.NodeTypeManager interface.
--
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-67) Definition of Nodetype Management API
Posted by "Oliver Kießler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-67?page=all ]
Oliver Kießler resolved GRFT-67:
--------------------------------
Resolution: Fixed
I consider this issue resolved for now, reopen it if necessary. I will start implementing now.
> Definition of Nodetype Management API
> -------------------------------------
>
> Key: GRFT-67
> URL: http://issues.apache.org/jira/browse/GRFT-67
> Project: Graffito
> Type: Task
> Components: JCR-Nodemanagement
> Versions: 1.0-a1-dev
> Reporter: Oliver Kießler
> Assignee: Oliver Kießler
> Fix For: 1.0-a1-dev
>
> Definition of the "nodemanagement API" in the org.apache.portals.graffito.jcr.nodemanagement.NodeTypeManager interface.
--
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-67) Definition of Nodetype Management API
Posted by "Christophe Lombart (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-67?page=comments#action_12356954 ]
Christophe Lombart commented on GRFT-67:
----------------------------------------
That's sound good !
Just some comments :
* I'm wondering if our jcr xml mapping file is suffisant to register some node types. Maybe some information are missing. For example, attributes like requiredType, autoCreated, mandatory, onParentVersion, protected, multiple, ... (found in Jackrabbit custom_nodetypes.xml) are not yet present in our jcr mapping file.
* It should be nice to register node types from other kind of xml files (eg.Jackrabbit custom_nodetypes.xml). This features is interesting if we plan to open this tools to other projects (which are not using our jcr mapping persistence manager). Let me know your point of view on that.
Thanks,
Christophe
> Definition of Nodetype Management API
> -------------------------------------
>
> Key: GRFT-67
> URL: http://issues.apache.org/jira/browse/GRFT-67
> Project: Graffito
> Type: Task
> Components: JCR-Nodemanagement
> Versions: 1.0-a1-dev
> Reporter: Oliver Kießler
> Assignee: Oliver Kießler
> Fix For: 1.0-a1-dev
>
> Definition of the "nodemanagement API" in the org.apache.portals.graffito.jcr.nodemanagement.NodeTypeManager interface.
--
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-67) Definition of Nodetype Management API
Posted by "Christophe Lombart (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-67?page=comments#action_12357040 ]
Christophe Lombart commented on GRFT-67:
----------------------------------------
Following last Oliver comment :
1. If you find a solution to merge our jcr mapping file and the Jackrabbit custom_nodetypes.xml : you will be make a great job :-). That's very painful to add more and more attributes in the jcr mapping file. If needed, I'm agree to refactor the peristence manager implementation (mapper, class descriptor, ... ). Otherwise we have to add more info in the jcr xml mapping file with, as you suggested, some default values.
Another idea is to import from the Jackrabbit custom_nodetypes.xml and not from our jcr mapping file. It will simplify the import process because this custom_nodetypes file is more appropriate. Furthermore, it uses by other projects (at least Jeceira). In such case, the most complex issue is to map our jcr mapping file to custom_nodetypes.xml (or merge both file).
I see 3 use cases :
A.Import from our jcr mapping file (Graffito use case)
1. Convert the jcr mapping file into custom_nodetypes.xml. That is certainly the big deal.
2. Use the right API to import this custom_nodettypes.xml file.
B. Import from custom_nodetypes.xml (Jackrabbit use case)
Use the right API to import this custome nodettype file (same as A.2)
C. Support for other JCR implementation (Exo, Jeceira, ...) . In theory, it should be possible to use their own API with the custom_nodetypes.xml (same as B).
What do you think about that ? I just a suggestion which certainly need more analysis.
2. It is quite difficult to give a good anwser now. Maybe focus on Jackrabbit but I think later I will be interesting to support other solutions of course.
> Definition of Nodetype Management API
> -------------------------------------
>
> Key: GRFT-67
> URL: http://issues.apache.org/jira/browse/GRFT-67
> Project: Graffito
> Type: Task
> Components: JCR-Nodemanagement
> Versions: 1.0-a1-dev
> Reporter: Oliver Kießler
> Assignee: Oliver Kießler
> Fix For: 1.0-a1-dev
>
> Definition of the "nodemanagement API" in the org.apache.portals.graffito.jcr.nodemanagement.NodeTypeManager interface.
--
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-67) Definition of Nodetype Management API
Posted by "Costin Leau (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-67?page=comments#action_12357508 ]
Costin Leau commented on GRFT-67:
---------------------------------
Jeceira is under Apache 2.0 license, only Exo is GPL.
> Definition of Nodetype Management API
> -------------------------------------
>
> Key: GRFT-67
> URL: http://issues.apache.org/jira/browse/GRFT-67
> Project: Graffito
> Type: Task
> Components: JCR-Nodemanagement
> Versions: 1.0-a1-dev
> Reporter: Oliver Kießler
> Assignee: Oliver Kießler
> Fix For: 1.0-a1-dev
>
> Definition of the "nodemanagement API" in the org.apache.portals.graffito.jcr.nodemanagement.NodeTypeManager interface.
--
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-67) Definition of Nodetype Management API
Posted by "Oliver Kießler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/GRFT-67?page=comments#action_12358104 ]
Oliver Kießler commented on GRFT-67:
------------------------------------
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
I think that's it. There are more attributes in the jackrabbit nodetypes xml file and the JCR spec but I think these are the attributes that are sufficant for jcr-mapping and jcr-nodemanagement. Please comment if these attributes can be added to the jcr-mapping file or if I missed something...
> Definition of Nodetype Management API
> -------------------------------------
>
> Key: GRFT-67
> URL: http://issues.apache.org/jira/browse/GRFT-67
> Project: Graffito
> Type: Task
> Components: JCR-Nodemanagement
> Versions: 1.0-a1-dev
> Reporter: Oliver Kießler
> Assignee: Oliver Kießler
> Fix For: 1.0-a1-dev
>
> Definition of the "nodemanagement API" in the org.apache.portals.graffito.jcr.nodemanagement.NodeTypeManager interface.
--
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