[ 
https://issues.apache.org/jira/browse/OFBIZ-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rupert Howell updated OFBIZ-707:
--------------------------------

    Attachment: WebappNameIncludedOnInterAppFramework.patch
                WebappNameIncludedOnInterAppForms.patch

Here are the patches - All Forms widgets hyperlink and sub-hyperlink elements 
for target-type="inter-app" can now have a webapp-name attribute referring to 
the webapp name as definied in the relevant ofbiz-component.xml file

For example.
<hyperlink target="control/viewparty?partyId=${partyId}" also-hidden="false" 
description="${uiLabelMap.ViewParty}" target-type="inter-app" 
webapp-name="party" /> 

Once I know I have done this correctly I will continue with this issue. 

> Inter webapp linking by name webapp name rather than mount-point
> ----------------------------------------------------------------
>
>                 Key: OFBIZ-707
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-707
>             Project: OFBiz (The Open for Business Project)
>          Issue Type: Improvement
>          Components: framework
>            Reporter: Rupert Howell
>            Priority: Minor
>         Attachments: WebappNameIncludedOnInterAppForms.patch, 
> WebappNameIncludedOnInterAppFramework.patch
>
>
> For security reasons I don't necessarily want others to know how to find any 
> of the back-office webapps so I change the mount-points for all of them. I 
> then have to find each time that webapp is called in all the ftls, 
> Screen/Form/Menu widgets and replace them with this new value. A good example 
> is the number of times partymgr is called from the order module.
> I would like to investigate the best way to link using the webapp's name 
> rather than mount-point each time so only one change has to be made. I would 
> be happy to attempt to implement this - does anyone have any comments on this?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to