This content has been marked as final.
Show 6 replies
-
1. Re: Custom mapper for cms
theute Dec 18, 2006 6:19 AM (in response to hurzeler)in portal-cms-sar/META-INF/jboss-service.xml you will find where the default command mapper is defined:
<mbean code="org.jboss.portal.core.controller.command.mapper.CommandFactoryDelegate" name="portal:commandFactory=Delegate,path=content" xmbean-dd="" xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean"> <xmbean/> <attribute name="Path">/content</attribute> <depends optional-attribute-name="DelegatingFactory" proxy-type="attribute">portal:commandFactory=Delegating</depends> <depends optional-attribute-name="DelegateFactory" proxy-type="attribute">portal:commandFactory=CMSObject</depends> </mbean>
Here you can replace it by a command mapper of your choice.
You will see that the tragetWindowRef is defined in the mbean: portal:commandFactory=CMSObject
You can choose to replace this command factory instead of the whole command mapper. -
2. Re: Custom mapper for cms
hurzeler Dec 18, 2006 6:32 AM (in response to hurzeler)what is the class of:
mbean: portal:commandFactory=CMSObject -
3. Re: Custom mapper for cms
theute Dec 18, 2006 6:37 AM (in response to hurzeler)You should open the jboss-service.xml file...
org.jboss.portal.core.cms.CMSObjectCommandFactory -
-
5. Re: Custom mapper for cms
hurzeler Dec 18, 2006 6:59 AM (in response to hurzeler)I just had a closer look. I might have missunderstood. Did you mean that it is sufficient to just change the tragetWindowRef ?
-
6. Re: Custom mapper for cms
hurzeler Dec 18, 2006 7:01 AM (in response to hurzeler)Further what would it be for a custom page on the same level as default, let's say Home.
default.default.DefaultCMSPortletWindow
to
default.Home.DefaultCMSPortletWindow
??