[
https://issues.apache.org/jira/browse/OFBIZ-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Busco updated OFBIZ-1999:
-------------------------------
Attachment: portalPages.patch
OK,
moved a little further.
Now the portlet edit form is able to retrieve and edit the portlet attributes
in the database.
What remains to do is to have the portlet screen to retrieve the attributes to
be used.
For this I have not yet a clear idea on the best way to do:
The portlets are defined as regular screens.
These are rendered by the pagePortal.ftl using the <render-screen> tag in a
<#list>.
To retrieve a portlet attribute map the getPortletAttribute servise must be
called specifing the portalPageId, portalPortletId and sequenceId that identify
the single portlet instance.
How to make the ftl call the service to retrieve the attributes and pass them
to the rendered screen?
Many thanks for any idea!
> A portal/portlet implementation
> -------------------------------
>
> Key: OFBIZ-1999
> URL: https://issues.apache.org/jira/browse/OFBIZ-1999
> Project: OFBiz
> Issue Type: New Feature
> Components: ALL COMPONENTS
> Reporter: Bruno Busco
> Priority: Minor
> Attachments: portalPage-configure-off.jpg,
> portalPage-configure-on.jpg, portalPageImages.zip, portalPages.patch,
> portalPages.patch, portalPages.patch, portalPages.patch, portalPages.patch,
> portalPages.patch, portalPages.patch, portalPages.patch, portalPages.patch,
> portalPages.patch
>
>
> Hi devs,
> I am trying to set up a portal/portlet model similar to what is implemented
> into JIRA user interface.
> The Idea is that every component can "register" its selected screens as
> system portlets using something like:
> <Portlet portletId="WELCOME" name="Welcome" description="Welcome message"
> screenPath="component://portal/widget/CommonScreens.xml#welcome" />
> In this case the portal component has registered a welcome screen as
> "WELCOME" portlet.
> The portlets can later be "mounted" into portals with the entity:
> <PortalPortletAppl portalId="DEFAULT" portletId="WELCOME"
> columnNum="1" sequenceNum="1" />
> <PortalPortletAppl portalId="DEFAULT" portletId="LOGIN"
> columnNum="2" sequenceNum="2" />
> <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET001"
> columnNum="1" sequenceNum="2" />
> <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET002"
> columnNum="3" sequenceNum="2" />
> <PortalPortletAppl portalId="DEFAULT" portletId="PORTLET003"
> columnNum="1" sequenceNum="2" />
> In this case the portlets WELCOME, LOGIN, PORTLET001, PORTLET002 and
> PORTLET003 are mounted into the DEFAULT portal into the indicated solumns and
> with the indicated order.
> Every portal is defined by the entity:
> <Portal portalId="DEFAULT" name="Default home portal" description="The
> default OFBiz portal" owner="admin" />
> And is related to a specific user. So every user can have as many portals he
> needs and a DEFAULT portal can be defined by the admin.
> In the attached zip file there is a very draft implementation of this that I
> would like so submit to your attention to share ideas about it and eventually
> develop together.
> Many thanks for your feedbacks,
> Bruno
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
