On 27/08/10 02:25, Alexander Klimetschek wrote:
And you only make node types for those things where you are sure they
are more or less fixed. For other things you keep going with
nt:unstructured. The same way that mandatory properties change in your
case, you will have the opposite, ie. that
On 26/08/10 19:47, Berry van Halderen wrote:
In Jackrabbit, only trivial nodetype changes are supported(see
o.a.j.c.nodetype.NodeTypeDefDiff) to reregister node types. In order to
change nodetypes we're currently using a module that can basically change any
nodetype structure. However this is
[
https://issues.apache.org/jira/browse/JCR-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12698162#action_12698162
]
Charles Brooking commented on JCR-2069:
---
Try using cglib-nodep instead. It has
[
https://issues.apache.org/jira/browse/JCR-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12680837#action_12680837
]
Charles Brooking commented on JCR-2011:
---
When you say 'semantic change' refers to node
: jackrabbit-core
Reporter: Charles Brooking
NodeImpl.setPrimaryType(String) attempts to redefine nodes and properties
that were defined by the previous node type if they also appear in the new
type. If there is no matching definition for a node/property in the new type -
or value
Thomas Müller wrote:
Just recently there was a discussion about getting the unique
identifier for a binary value. I created an issue:
https://issues.apache.org/jira/browse/JCR-1892
I am currently using the XMLPersistenceManager.
You should consider using a bundle database persistence
Hi all
I've had a requirement recently to access the (operating system) files in
which binary properties are stored. I know the standard means for
obtaining binary content is through streams, but here are my reasons:
* I need to use a third-party C library, through JNI, that takes
a file
