[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-3189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28154#action_28154
 ] 

Jan Haderka commented on MAGNOLIA-3189:
---------------------------------------

When a node type is registered it is registered for all workspaces including 
the {{mgnlSystem}}. The problem is usually the fact that you did not register 
the nodetype on the receiving instance. This is typically done in data module 
by activating the type itself. In case your type is already properly registered 
and you can create manually items of given type on the receiving instance, 
please attach the complete stacktrace.

> "NoSuchNodetypeException" in RecieveFilter when activating already published 
> nodes for a separate repository
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: MAGNOLIA-3189
>                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3189
>             Project: Magnolia
>          Issue Type: Bug
>          Components: activation
>    Affects Versions: 4.3.1
>            Reporter: Manuel Molaschi
>            Assignee: Jan Haderka
>
> We have two jcr repositories, the default one and a repository for media(with 
> custom nodetypes). I am publishing some medias (custom nodetype) from the 
> author instance of a staging env  (in the separated jcr repository) to the 
> author instance of a production env.
> When i publish new contents everything goes fine, but when i publish modified 
> contents i get an exception on the destination server:
> {{[gest-srv] ERROR 03.05.2010 12:44:06 
> info.magnolia.module.exchangesimple.ReceiveFilter 
> ReceiveFilter.java(importOnExisting:444) -- Exception caught}}
> {{javax.jcr.nodetype.NoSuchNodeTypeException: 
> {http://www.magnolia.info/jcr/mgnl}media}}
> Looking at source code, there is a temporary import to the mgnlSystem 
> workspace that resides in the default repository which have not the custom 
> nodetypes declarations (registered in the media repository).
> Possible solutions?
> - getting the SystemContext hierarchyManager for the destination workspace 
> instead of mgnlSystem
> - have a mgnlSystem ws in every repository mapped as mgnlSystem[repository 
> name]
> - register custom nodetypes also on default repository

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to