You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Darren Hartford (JIRA)" <ji...@apache.org> on 2007/04/09 22:14:32 UTC
[jira] Created: (JCR-836) Configuration of nodetypes vs programming
of nodetypes
Configuration of nodetypes vs programming of nodetypes
------------------------------------------------------
Key: JCR-836
URL: https://issues.apache.org/jira/browse/JCR-836
Project: Jackrabbit
Issue Type: New Feature
Components: nodetype
Affects Versions: 1.2.3, 1.2.2, 1.2.1, 1.1.1, 1.1, 1.0.1, 1.0, 0.9
Reporter: Darren Hartford
Mandating that you must use programming to define/install nodeTypes is very limiting. Recommend allowing the use of a CND configuration folder that is read on start-up to configure nodeTypes through CND text files without java programming.
There used to be a repository/nodetype folder that contained XML definitions, but those did not necessarily get read in without java programming. Follow through with the repository/nodetype folder for CND text files (and/or workspace/nodetype folder) that can be loaded on-startup without requiring programming.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-836) Configuration of nodetypes vs
programming of nodetypes
Posted by "Darren Hartford (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487776 ]
Darren Hartford commented on JCR-836:
-------------------------------------
JCR-771 is a good reference, sorry I must have missed that feature request.
I am a very strong believer in coding functionality. However, basic configuration should be just that - configuration.
Usecase: Someone creates a set of CNDs for certain sets of functionality:
*Dublin Core
*Common Web Content nodeTypes (Magnolia, etc)
*Hylafax content repository nodeTypes (storing sent and received faxes)
Basically, looking at http://wiki.apache.org/jackrabbit/NamespaceRegistry and http://wiki.apache.org/jackrabbit/NodeTypeRegistry there are some pre-existing, commonly accepted nodeTypes that are not the default Jackrabbit, but people would like to use.
Rather than require programming to enable those nodeTypes, some type of configuration (i.e. drop a group of CND files/bundle in a folder, load through node-type tool, etc) will greatly increase adoption of those nodeTypes and remove an existing barrier to, what I'm sure many people consider, configuration of the underlying repository (either Jackrabbit standalone or as a piece of a larger application).
The entire JCR spec is designed to help standardize content repositories. However, if each repository has different types of nodetypes for similar functionality due to lack of adoption of common nodetypes, we will have interoperability challenges related to the data stored in the repository. Making it easy to load CND files (without programming) will be an *enabler* towards common nodetypes for the many available scenarios and usage of the Jackrabbit repository.
JCR-324 looks like a good approach of configuring the nodetypes. Again, it's when you require programming of any sort to configure nodetypes is the only thing I personally would like to see removed.
> Configuration of nodetypes vs programming of nodetypes
> ------------------------------------------------------
>
> Key: JCR-836
> URL: https://issues.apache.org/jira/browse/JCR-836
> Project: Jackrabbit
> Issue Type: New Feature
> Components: nodetype
> Affects Versions: 0.9, 1.0, 1.0.1, 1.1, 1.1.1, 1.2.1, 1.2.2, 1.2.3
> Reporter: Darren Hartford
>
> Mandating that you must use programming to define/install nodeTypes is very limiting. Recommend allowing the use of a CND configuration folder that is read on start-up to configure nodeTypes through CND text files without java programming.
> There used to be a repository/nodetype folder that contained XML definitions, but those did not necessarily get read in without java programming. Follow through with the repository/nodetype folder for CND text files (and/or workspace/nodetype folder) that can be loaded on-startup without requiring programming.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-836) Configuration of nodetypes vs
programming of nodetypes
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487770 ]
Stefan Guggisberg commented on JCR-836:
---------------------------------------
for a related discussion on the users list see: http://thread.gmane.org/gmane.comp.apache.jackrabbit.user/2348
> Configuration of nodetypes vs programming of nodetypes
> ------------------------------------------------------
>
> Key: JCR-836
> URL: https://issues.apache.org/jira/browse/JCR-836
> Project: Jackrabbit
> Issue Type: New Feature
> Components: nodetype
> Affects Versions: 0.9, 1.0, 1.0.1, 1.1, 1.1.1, 1.2.1, 1.2.2, 1.2.3
> Reporter: Darren Hartford
>
> Mandating that you must use programming to define/install nodeTypes is very limiting. Recommend allowing the use of a CND configuration folder that is read on start-up to configure nodeTypes through CND text files without java programming.
> There used to be a repository/nodetype folder that contained XML definitions, but those did not necessarily get read in without java programming. Follow through with the repository/nodetype folder for CND text files (and/or workspace/nodetype folder) that can be loaded on-startup without requiring programming.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-836) Configuration of nodetypes vs
programming of nodetypes
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487771 ]
Jukka Zitting commented on JCR-836:
-----------------------------------
Such a feature would IMHO be best implemented with customizable startup scripts as proposed in JCR-324. Alternatively we should have a node type tool like the one included in Day's Content Explorer that could be used by an administrator to register new node types.
See also JCR-771 for the same feature request that was resolved as Won't Fix. I'm inclined to do the same for this issue unless the objections are countered.
> Configuration of nodetypes vs programming of nodetypes
> ------------------------------------------------------
>
> Key: JCR-836
> URL: https://issues.apache.org/jira/browse/JCR-836
> Project: Jackrabbit
> Issue Type: New Feature
> Components: nodetype
> Affects Versions: 0.9, 1.0, 1.0.1, 1.1, 1.1.1, 1.2.1, 1.2.2, 1.2.3
> Reporter: Darren Hartford
>
> Mandating that you must use programming to define/install nodeTypes is very limiting. Recommend allowing the use of a CND configuration folder that is read on start-up to configure nodeTypes through CND text files without java programming.
> There used to be a repository/nodetype folder that contained XML definitions, but those did not necessarily get read in without java programming. Follow through with the repository/nodetype folder for CND text files (and/or workspace/nodetype folder) that can be loaded on-startup without requiring programming.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.