myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott O'Bryan (JIRA)" <>
Subject [jira] Commented: (TRINIDAD-134) StateManagerImpl is not fully compatible with JSR-301
Date Wed, 13 Feb 2008 16:21:08 GMT


Scott O'Bryan commented on TRINIDAD-134:

Yeah, I'm actually throwing around another lower impact solution which uses some of the portlet-bridge
api's.  I'm hoping to have something checked in my branch today for testing...  If that doesn't
work, I'll apply this patch.

> StateManagerImpl is not fully compatible with JSR-301
> -----------------------------------------------------
>                 Key: TRINIDAD-134
>                 URL:
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Portlet
>    Affects Versions: 1.2.1-core
>         Environment: JSR-168, JSR-301
>            Reporter: Scott O'Bryan
>            Assignee: Matthias We├čendorf
>             Fix For: 1.2.3-core
>         Attachments: trinidad-134.patch
> StateManagerImpl has a performance enhancement that is not compatible with JSR-301. 
Inside of the popRoot method inside of org.apache.myfaces.trinidadinternal.application.StateManagerImpl,
the view root is retrieved using Application.createComponent();.  The JSR-301 bridge has a
special UIViewRoot that, due to limitations in the JSF specification, can only reasonably
be retrieved through ViewHandler.createViewRoot().  We either need to try to try to retrieve
the UIViewRoot using this mechanism OR we need to disable this performance optimization in
a portal environment.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message