myfaces-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Myfaces Wiki] Trivial Update of "Using Portlets" by StephanStrittmatter
Date Thu, 03 Aug 2006 12:39:33 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Myfaces Wiki" for change notification.

The following page has been changed by StephanStrittmatter:

  While most MyFaces apps work seamlessly as a servlet or a portlet, changing a MyFaces appliction
into a portlet can sometimes raise issues.  There are several circumstances which make it
necessary to change sources to get it run. There is also the JIRA entry [
MYFACES-434] which addresses some of the issues.
- Shinsuke SUGAYA has done there already a lot work and provides at 
+ Shinsuke SUGAYA has done there already a lot work and provides at a !MyFaces-bridge (in Japanese).
  '''''Any help is welcome to improve the portal support of !MyFaces!'''''
@@ -9, +9 @@

  == Problems ==
  There are some issues, which cause the problems of using !MyFaces together with portals.
The !MyFaces-Team is working on these issues to reduce any limitation.
-  * ''["External Resources"]:'' 
+  * ''["External Resources"]:''
     !MyFaces uses also external resources like CSS and !JavaScripts files. Some of these
files are added by the framework only once to the head part of the generated HTML output.
Running as portlet, there is no access to this head as the portlet do not know about its container.
For this, special ''["External Resources"]'' implementations are required for specific portal
-  * ''Generated IDs'': 
+  * ''Generated IDs'':
     !MyFaces uses internal also IDs to identify the controls, but some portal servers rename
these IDs (prefixes them for example) which could cause problems with generated !JavaScript
code.  ''Actually, namespace prefixes are part of the JSF spec and should work okay, presuming
that the component is written well''
-  * ''Caching'': 
+  * ''Caching'':
     Portal servers provide often caching of the portlets. This could work different than
the expected caching provided by a commen web contaienr like Tomcat. One solution could be
to disable portlet caching, see
-  * ''FileUpload'' component: 
+  * ''FileUpload'' component:
     The file upload requires specific form parameters and do not work with no modifications
within portlets. See also: ["Setup For File Uploads"] and [
-  * ''Duplicate IDs'': 
+  * ''Duplicate IDs'':
     The Tomahawk Datatable doesn't work with two datascrollers. ERROR [portal-web.docroot.html.portal.render_portlet.jsp]
java.lang.IllegalStateException: Duplicate component ID found in view. (Liferay 4.0)
     Duplicate IDs are often thrown also during development when some of the jsf-pages are
not recompiled copmpletly. Then try to remove all compiled jsp files and it should work again.
See also the bullet on ''Caching''
@@ -27, +27 @@

   * ["CreatingJSFPortlets"] - Quick and dirty instructions to turn your !MyFaces app into
a portlet.
   * ["UsingPortletUtil"] - What to do if your application needs to know whether or not it
is running as a portlet.
   * ["UsingPortletModes"] - Make your !MyFaces portlet use portlet modes such as Edit and
-  * ["MavenLiferayPortlet"] - How to build a MyFaces app with Maven 2 and deploy it under
+  * ["MavenLiferayPortlet"] - How to build a !MyFaces app with Maven 2 and deploy it under
   * Remote Debugging could be useful if you are using Portals. How to set up Eclipse for
remote debugging, have a look at Levent Gurses' great article:
  == Portal Servers ==

View raw message