[jira] [Commented] (JCR-609) Empty custom_nodetypes.xml after restart

["Marek Slama (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCR-609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588373#comment-13588373 ] 

Marek Slama commented on JCR-609:
---------------------------------

Still present in 2.4.0. Only workaround I found is to modify directly jackrabbit-core/src/main/resources/org/apache/jackrabbit/core/nodetype/builtin_nodetypes.cnd. In my case I only needed to add small modification of nt:unstructured. I added new type directly to builtin_nodetypes.cnd. I know it is only workaround till this issue is fixed.
                
> Empty custom_nodetypes.xml after restart
> ----------------------------------------
>
>                 Key: JCR-609
>                 URL: https://issues.apache.org/jira/browse/JCR-609
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-jca
>    Affects Versions: 1.1
>         Environment: oc4j 10.1.3
>            Reporter: Magnus Grimsell
>
> I run jackrabbit jca on oc4j 10.1.3.
> First time the server is started I execute the following code on the empty repository :
> JackrabbitNodeTypeManager manager =	
>   (JackrabbitNodeTypeManager)session.getWorkspace().getNodeTypeManager();
> InputStream nodeTypes = this.getClass().getClassLoader().getResourceAsStream(res);
> manager.registerNodeTypes(nodeTypes, JackrabbitNodeTypeManager.TEXT_X_JCR_CND);
> session.save();
> This works fine. I can create nodes of custom type. However when restarting the server I get the following error:
> Error creating a Connection Factory from class 'org.apache.jackrabbit.jca.JCAManagedConnectionFactory'. Reason: javax.resource.ResourceException: Failed to create session: internal error: failed to read custom node type definitions stored in custom_nodetypes.xml:
> custom_nodetypes.xml exists but is empty.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira