[
https://issues.apache.org/jira/browse/OFBIZ-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
BJ Freeman resolved OFBIZ-1531.
-------------------------------
Resolution: Fixed
in then dev mailing list chris came up with a feasable solution
this is from his email.
You'll need to get put the <viewmap>@page value into the context and run a
script in your main-decorator to determine the correct values
if (page.like("component://partymgr")
applicationMenuName = "Party";
elseif(page.like("component://product")
applicationMenuName="Product";
etc
parameters.put("applicationMenuName", applicationMenuName);
then in your main-decorator, instead of having
<set field="applicationMenuName" value="SetupMainMenu" global="true"/>
you will have
<set field="applicationMenuName" vlaue="${parameters.applicationMenuName}"/>
etc
> implement a fix to solve the location="${parameters.mainDecoratorLocation}
> giving an error.
> -------------------------------------------------------------------------------------------
>
> Key: OFBIZ-1531
> URL: https://issues.apache.org/jira/browse/OFBIZ-1531
> Project: OFBiz
> Issue Type: Bug
> Affects Versions: SVN trunk, Release Branch 4.0
> Reporter: BJ Freeman
> Priority: Minor
> Fix For: SVN trunk, Release Branch 4.0
>
>
> Though not meant to be used for intra-apps
> the Include feature is being used that way in the controller for
> common-controller.
> there is a gotcha describe in the dev ML about
> .mainDecoratorLocation not being accessed when since it is in the context in
> the web.xml
> To remedy this
> all
> location="${parameters.mainDecoratorLocation}
> will be changed to the actual path found in the web.xml for each application.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
