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

[Nicolas Malin (Jira)]

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.

[Nicolas Malin (Jira)]

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

[Nicolas Malin (Jira)]

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

Jacques Le Roux closed OFBIZ-2096.
----------------------------------

       Resolution: Fixed
    Fix Version/s: SVN trunk
         Assignee: Jacques Le Roux

Thanks Bruno,

Your patch is in trunk revision: 728251 .

I think you sould better discuss your idea on dev ML (hopefully you would get more answers ;o)

> Error in DashBoardExample
> -------------------------
>
>                 Key: OFBIZ-2096
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-2096
>             Project: OFBiz
>          Issue Type: Bug
>            Reporter: Bruno Busco
>            Assignee: Jacques Le Roux
>             Fix For: SVN trunk
>
>         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.