You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Bruno Busco (JIRA)" <ji...@apache.org> on 2008/12/20 00:58:44 UTC

[jira] Updated: (OFBIZ-2096) Error in DashBoardExample

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

Bruno Busco updated OFBIZ-2096:
-------------------------------

    Attachment: examplePortal.patch

> Error in DashBoardExample
> -------------------------
>
>                 Key: OFBIZ-2096
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-2096
>             Project: OFBiz
>          Issue Type: Bug
>            Reporter: Bruno Busco
>         Attachments: examplePortal.patch
>
>
> Hi,
> It seems there in an error accessing to https://demo.hotwaxmedia.com/example/control/dashboardExample
> (Could not find screen with name [main-decorator] in the same file as the screen with name [DisplayExamplePage])
> With the attached patch it is fixed. It seems that there was some dead code causing the bug.
> More in general I think we should better review the Portal pattern. It seems to me that transforming it from a centralized dashboard to an application distributed portals has left something to clean up.
> For example the dashboard and the ManagePortals requests should be merged toghether and only the ManagePortal should be used.
> The term "dashboard" should not be used becouse it should refer to a unique central customizable screen that we have not any more (we can have many in the applications).
> Does this make sense?

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