I do not see the benefit if you still need to add entity definition in the XML data file.
2010/9/13 Erwan de FERRIERES <[email protected]> > Le 13/09/2010 15:11, Bruno Busco a écrit : > >> I connot see what is the purpose of a portlet like this: >> >> >> <screen name="GenericScreenlet"> >> <section> >> <actions> >> <script >> >> location="component://common/webcommon/WEB-INF/actions/includes/retrievePortletAttributes.groovy"/> >> </actions> >> <widgets> >> <screenlet title="${uiLabelMap.${titleLabel}}" >> collapsible="true" id="scrlt_${formName}"> >> <include-form name="${formName}" >> location="${formLocation}"/> >> </screenlet> >> </widgets> >> </section> >> </screen> >> >> could you please help me? >> Thank you. >> >> Here is an example on how to use it : > <PortalPagePortlet portalPageId="TActWorkflowMgmt" > portalPortletId="GenericScreenlet" portletSeqId="00001" columnSeqId="00001" > sequenceNum="5"/> > <PortletAttribute portalPageId="TActWorkflowMgmt" portletSeqId="00001" > portalPortletId="GenericScreenlet" attrName="titleLabel" > attrValue="PageTitleTActWorkflowMgmt"/> > <PortletAttribute portalPageId="TActWorkflowMgmt" portletSeqId="00001" > portalPortletId="GenericScreenlet" attrName="formName" > attrValue="findWorkflowType"/> > <PortletAttribute portalPageId="TActWorkflowMgmt" portletSeqId="00001" > portalPortletId="GenericScreenlet" attrName="formLocation" > attrValue="component://tcm/widget/tcm/IntervTypesForms.xml"/> > > As you can see, we are just defining the simple parameters for a form, and > it's included as a portlet in a portal > > > -- > Erwan de FERRIERES > www.nereide.biz >
