[
https://jira.jboss.org/jira/browse/JBIDE-3635?page=com.atlassian.jira.plu...
]
Thomas Heute commented on JBIDE-3635:
-------------------------------------
From what I'm hearing we should simply ignoring everything except
what PortletBridge Beta 6 provides (i.e. independence of Richfaces), correct ?
Not sure what you mean
Plain portlet project - unaffected
JSF portlet project - works with both
AS/portlet.org and EAP/EPP since it just needs a
recent Porlet release and JSF 1.2
Seam portlet project - works with respect to plain JSF, will have some issues with
Richfaces if the RF part is not upgraded to 3.3
Is that correct ?
correct, you're just missing, JSF/Richfaces portlet (no Seam) would require RF 3.3
If yes, what are the issues that will happen in a Seam portlet
project ? Will it not even start up ?
Yes
Will it be able to run pure JSF pages in portlet as long as no
richfaces components are on that page ?
If no RF settings are done yes.
Will pages with richfaces work fine as long as they are not hooked
into a portlet ?
EAP won't be affected
Will it be able to run pure JSF pages in portlet as long as no
richfaces components are on that page ?
Fine with me
Fix compatibility issues with Portletbridge distribution
--------------------------------------------------------
Key: JBIDE-3635
URL:
https://jira.jboss.org/jira/browse/JBIDE-3635
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Portal
Affects Versions: 3.0.0.CR2
Reporter: Snjezana Peco
Assignee: Snjezana Peco
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira