[
http://jira.jboss.com/jira/browse/JBPORTAL-1149?page=comments#action_1235... ]
David Allen commented on JBPORTAL-1149:
---------------------------------------
In 2.6-ALPHA2, I can see that the fix has been applied to the tag handler to include the
HEADER_CONTENT property value. Unfortunately, in 2.6 (including the current SVN trunk),
the render response properties are not passed along through the FragmentResponse to the
WindowResult object where the tag retrieves the properties. The portlet content renderer
always passes "new Properties()" as the set of render response properties for
each new WindowResult. Of course, that's understandable at the moment since the
content renderer does not have access to the properties through the FragmentResponse being
processed nor via the response invocation object.
The other header content acquired from jboss-portlet.xml still works since that uses an
independent approach.
Tag header doesn't work
-----------------------
Key: JBPORTAL-1149
URL:
http://jira.jboss.com/jira/browse/JBPORTAL-1149
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.4 Final
Reporter: Vera Mickael
Assigned To: Roy Russo
Fix For: 2.6.Alpha1
The tag header doesn't work.
I started a thread in jbossportal forum but I didn't have many answers, the
descritption of the issue can be found at this URL :
http://jboss.org/index.html?module=bb&op=viewtopic&t=93920
The jbossportal documentation par 12.6.1 describes the way to inject header content :
http://docs.jboss.com/jbportal/v2.4/reference-guide/en/html/themeandlayou...
In the example we can see that a property name is used : HEADER_CONTENT
But in the whole jboss portal code, this property isn't used. This makes me think
that there is a mistake. In my forum thread I give a solution to make the work.
Regards,
Mickaƫl
--
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