jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "hector rovira (JIRA)" <j...@apache.org>
Subject [jira] Created: (JCR-1422) Support and Document Node Type Definitions in XML or Java API
Date Tue, 26 Feb 2008 20:44:51 GMT
Support and Document Node Type Definitions in XML or Java API

                 Key: JCR-1422
                 URL: https://issues.apache.org/jira/browse/JCR-1422
             Project: Jackrabbit
          Issue Type: Improvement
          Components: nodetype
            Reporter: hector rovira
            Priority: Minor

I have been using Jackrabbit for the past few months, and all the APIs are accessible and
relatively easy to configure and understand.
Except when it comes to configuring custom NodeTypes.  I read the documentation (http://jackrabbit.apache.org/node-type-notation.html)
and it seems impractical to require developers to learn a new notation, just because you want
to compress the size of the document.

It makes sense to compress the size of the document if you are transmitting lots of information
and want to improve performance (i.e. JSON).  But to configure an application, you want to
be as clear (and accessible) as possible.

I spend most of my development effort integrating open source software components.  I would
like to be able to do this as quickly as possible, with standard mechanisms and APIs.  That
is why XML is such a great standard for integration (Maven, Spring).

Also, I don't even know how to programmatically create a node type.  What if I wanted to expose
such a functionality through a UI?

I think the case needs to be reopened.

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

View raw message