We have modified the NuxeoPortlet structure. The class was implemented
to be used with Jahia and we think that NuxeoPortlet class must not
depend on the portlet container used.
The modifications are:
- The method getUIDForJahia from NuxeoPortlet class is now called getUID
and it's empty (returns null). We need to change every reference to
getUIDForJahia.
- We have created two new class that extends NuxeoPortlet:
NuxeoPortletForJBossPortal and NuxeoPortletForJahia. These classes
implement the method getUID in accordance with the portlet container in
question. With this structure, it's easier to add a new portlet container.
- In JBoss Portal we need to add the following line in the methods
doView, doEdit and doHelp:
response.setContentType("text/html");
So we add it in the NuxeoPortlet class.
- In the methods doRestleCall from NuxeoPortlet we add the following line:
initializeGlobalPreferences(preferencesKeyUID);
With this line, the portlet is initialized in accordance with the
portlet.xml file.
Now, when we want to design a new portlet we have to extend from the
corresponding NuxeoPortletForXXXX class.
If you think that these changes are useful we can submit it.
Regards.
--
Enrique Pérez Olivares.
Dpto I+D.
Yerbabuena Software.
[EMAIL PROTECTED]
http://www.yerbabuena.es
Tlf/Fax: 902 995 246
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
