• 1 reply
  • Latest Post - ‏2013-04-05T16:39:06Z by SystemAdmin
3 Posts

Pinned topic JSF 2.0 Portal 8 portlet bridge?

‏2013-03-26T14:23:35Z |
Any news on JSF 2 bridge support (JSR 301) for Portal 8? Looking for some standard way to implement public parameter handling.
Currently working around with phase listener.

Updated on 2013-04-05T16:39:06Z at 2013-04-05T16:39:06Z by SystemAdmin
  • SystemAdmin
    14225 Posts

    Re: JSF 2.0 Portal 8 portlet bridge?


    you can review the particular JSRs: mentions
    "JSR 301: Portlet 1.0 Bridge for JavaServerTM Faces 1.2" mentions
    "JSR 329: Portlet 2.0 Bridge for JavaServerTM Faces 1.2"

    You indicate that you look for a JSF 2.0 portletbridge.
    WAS 8.0 ships starting from a JSF 2.0 JSR286 portletbridge.
    Portal 8.0 runs on WAS

    You might want to review interesting articles in the Portal Tools section of the RAD Wiki on Portal development with JSF2. The wiki also references an article on how to configure a third-party JSR301 portletbridge within RAD 7.5.
    The RAD 8.5 help explains as well how to configure a third-party JSR301 portletbridge
    To my knowledge there are those specifications, which are not yet finished or in final draft.
    See JSR 362: Portlet Specification 3.0
    which states: "* Optimize support for Java Server Faces" and "Depending on decisions taken by the workgroup, JSR 329 'Portlet 2.0 Bridge for JavaServerTM Faces 1.2 Specification' will potentially need to be revised."

    See JSR 344: JSF 2.2
    "Requirements in this category support an implementation of the Portlet Bridge 2.0 specification JSR-329 for JSF 2. In general, all the requirements relate to smoothing out the wrinkles in JSF 2 that arise when attempting to use JSF 2 features in a portlet runtime. Features in this category include, but are not limited to the following."
    You can file enhancement requests in the RFE community for WAS and RAD if you have specific requirements
    Hope this helps.


    The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM