[ http://jira.jboss.com/jira/browse/RF-3153?page=all ]
Svetlana mukhina closed RF-3153.
--------------------------------
Resolution: Done
> <a4j:portlet> not needed anymore with JBossPortletBridge => tell it in the
> doc.
> --------------------------------------------------------------------------------
>
> Key: RF-3153
> URL: http://jira.jboss.com/jira/browse/RF-3153
> Project: RichFaces
> Issue Type: Task
> Components: docs updated
> Affects Versions: 3.2.0
> Environment: JBoss PortletBridge B2 / RichFaces 3.2.0 / JBoss Portal
> Reporter: Antoine Herzog
> Assigned To: Gleb Galkin
> Priority: Minor
> Fix For: 3.2.1
>
>
> In another jira, Wesley says that :
> "The configurations used in this issue are old - like a4j:portlet is not
> needed. You should now be using JBoss Portlet Bridge
> (http://www.jboss.org/portletbridge/). the Beta2 demo application proves that
> this is working."
> JIRA is : http://jira.jboss.com/jira/browse/PBR-20
> (at the end of the comments)
> if the a4j:portlet is not needed :
> - not needed only with the JBoss PortletBridge, but needed with other
> bridges ?
> - not needed never ?
> It would be great to have something explained about that in the documentation
> of RichFaces.
> Or a "Deprecated" put on it.
> And in the doc or wiki of JBoss PortalBridge.
> Now, the component is described, nothing to prevent using it...
--
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
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
