]
Thomas Heute commented on JBPORTAL-1321:
----------------------------------------
It sounds like a Portlet bridge issue, not a portal issue. Can you confirm ?
This behavior would most likely be different on different implementations of a JSF portlet
bridge
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, preftest.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: