[
http://jira.jboss.com/jira/browse/JBPORTAL-1501?page=comments#action_1236... ]
Antoine Herzog commented on JBPORTAL-1501:
------------------------------------------
Yes, I saw the changes : not possible anymore to get the window name from the rendering
part.
I worked around : define some new regions in the layout, and set to it only one portlet.
it makes more regions, but more clean way to put porltet/window in the layout...
I guess this Jira can be closed...
PortletTagHandler : not yet programmed in 2.6.0RC3
--------------------------------------------------
Key: JBPORTAL-1501
URL:
http://jira.jboss.com/jira/browse/JBPORTAL-1501
Project: JBoss Portal
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Portal Core
Affects Versions: 2.6 CR3
Environment: JPB2.6.0 RC3
Reporter: Antoine Herzog
Assigned To: Julien Viet
Fix For: 2.6.1 Final
The PortletTagHandler class is not yet programmed.
The former code (for 2.4.1) is commented out.
This class was patched for 2.4.2 and 2.4.6
See :
http://jira.jboss.com/jira/browse/JBPORTAL-1316
It seems that the portlet rendering API has changed quiet a lot for 2.6
Any tips of what have changed : general philosophy of the change, where to find what have
moved, etc... are welcome to help make a patch.
I think this should be done for 2.6.0 final, has I know 2 portal in prod that use it yet
(in 2.4.1).
It is very usefull to put some portlets directly in the layout jsp framework, and not in
"all the pages" :
- chose the locale,
- chose the theme (for special accessibility prestentation),
- login and user portlet,
- general main navigation, etc...
Thanks
--
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