You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Jonathon Wong (JIRA)" <ji...@apache.org> on 2007/09/11 08:37:32 UTC

[jira] Commented: (OFBIZ-707) Inter webapp linking by name webapp name rather than mount-point

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

Jonathon Wong commented on OFBIZ-707:
-------------------------------------

Any progress on this one? If not, I'll take it up and complete it? Seems quite trivial to me, since I've recently taken apart the Controller chunk in OFBiz.

Let me get the checklist straight: .ftls, Screen/Form/Menu widgets. That's all?

I like this idea. Not just for security (when hiring outsourced developers), but also to reduce redundancy. The webapp name should be the canonical reference to the webapp. We shouldn't have to specify the mount-point when trying to refer to a webapp.

> 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
>          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.