[jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1321) In a JSF portlet, reading preferences returns various values

[Adam Warski (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBPORTAL-1321?page=all ]

Adam Warski updated JBPORTAL-1321:
----------------------------------

    Attachment: pref-test-bin.tar.gz

Binary version of the failing portlet.

> In a JSF portlet, reading preferences returns various values
> ------------------------------------------------------------
>
>                 Key: JBPORTAL-1321
>                 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1321
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.6.Beta1
>         Environment: AS 4.0.5, Portal 2.6 beta 1
>            Reporter: Adam Warski
>             Fix For: 2.6.CR1
>
>         Attachments: pref-test-bin.tar.gz, pref-test.tar.gz
>
>
> In a JSF portlet, during various phases of the request lifecycle, I read a portlet preference, and get different values. More precisely:
> * I get the default value of the preference (as written in portlet.xml), during the initial phases (this value is incorrect)
> * I get the proper value, from the portlet instance definition (as written in portlet-instances.xml), during later phases
> This has many weird implications, like jsf actions seeming not to work etc. I attach a sample portlet in both binary and source versions. When deployed, go to the "testfacelets" page, and click on the "Invoke action" link, and observe output of the server. You'll see that in the beginning, when the "pref1" preference is read, it returns a value from project.xml - 0. Later, the proper value from portlet-instances.xml, namely 1.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira