[ https://jira.jboss.org/browse/JBDS-1410?page=com.atlassian.jira.plugin.sy... ] Jan Jamrich commented on JBDS-1410: ----------------------------------- I don't see how to change assignee for this JIRA, so please assign me to this JIRA. We need to find workaround for this issue for our (Portal, PortletBridge respectively) users, to let them able create working richfaces app using JBDS-3.0.1.GA -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBDS-1410?page=com.atlassian.jira.plugin.sy... ] Jan Jamrich commented on JBDS-1410: ----------------------------------- I found it in JBDS-3.0.1.GA, but haven't tried it on JBDS-4.0.0.B2. I'll try and update -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBDS-1410?page=com.atlassian.jira.plugin.sy... ] Snjezana Peco commented on JBDS-1410: ------------------------------------- The JBoss JSF portlet which includes Richfaces requires: 1) portlet-api that is within the EPP/GateIn distribution 2) portletbridge libraries placed within the portletbridge distribution 3) richfaces libraries within the richfaces distribution 4) dependent libraries I have succeeded to find the dependent libraries only within the portletbride richfaces example. The problem happens when the name of this example is changed in different portletbridge/EPP distributions - in the portletbridge 1.x that was RichFacesPortlet.war, in the portletbridge 2.0.0 BETA that was richFacesPortlet.war, in EPP 5.0 that is richFacesPortlet-2.0.0.FINAL.war ... - some previous version of EPP 5.0 has had seamPortlet.war, EPP 5.0.1 contains seamEAR.ear ... I understand that using the libraries from examples isn't the best solution, but I can't find them on any other place. The fix within JBIDE-7702 tries to find dependent libs in the following examples: - RichFacesPortlet..war - richFacesPortlet*.war - seamPortlet*.war - seam*.ear The best solution would be if portletbridge/EPP would contain dependencies for different portlets : JSF Portlet, RichFaces JSF portlet, Seam Portlet (war and EAR version) The following are workarounds for JBDS 3.0.1: 1) copy (or rename) portletbridge/examples/richFacesPortlet-2.0.0.FINAL.war to portletbridge/examples/RichFacesPortlet.war After that you will be able to create JSF Richfaces portlet using the above described case. This solution is valid for some version of portletbridge/EPP and richfaces. or 2) - create JSF Richfaces Portlet (richfaces 3.3.3 and EAP 5.0.1/portletbridge 2.0.0.FINAL) as described in this jira - add the following libs to WEB-INF/lib: commons-beanutils-1.8.0.jar commons-digester-1.8.1.jar jsf-facelets-1.1.15.B1.jar richfaces-api-3.3.3.Final.jar richfaces-impl-3.3.3.Final.jar richfaces-impl-jsf2-3.3.3.Final.jar (if you are using JSF 2.0) richfaces-ui-3.3.3.Final.jar These files can be found in <EPP_HOME>/portletbridge/examples/richFacesPortlet-2.0.0.FINAL.war!/WEB-INF/lib portletbridge-api-2.0.0.FINAL.jar and portletbridge-impl-2.0.0.FINAL.jar would need to be in WEB-INF/lib The solution is valid for richfaces 3.3.3 and portletbridge 2.0.0.FINAL. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBDS-1410?page=com.atlassian.jira.plugin.sy... ] Snjezana Peco commented on JBDS-1410: ------------------------------------- portletbridge-api-2.0.0.FINAL.jar and portletbridge-impl-2.0.0.FINAL.jar are already taken from the <EPP_HOME>/portletbridge/. I can get richfaces and other dependencies from <EPP_HOME>/seam/lib when using the EPP distro. I know what dependent libraries are necessary for EPP 5.0, 5.0.1, 5.1, but can't predict what libraries will be necessary for some future EPP versions. However, what if we use JBoss AS + GateIn or JBoss AS + JBoss Portal? The seam directory doesn't exist in this case.Can we do the following: - if the user uses EPP containing seam, we would only enable using richfaces from EPP's Seam distro (the user wouldn't be able to choose a richfaces community edition; he would have to use richfaces from the EPP's seam library). The user would have to use portletbridge from an EPP distro if exists (EPP 4.3 doesn't have portletbridge and we would have to enable the user to use a community portletbridge). - if the user uses JBoss AS+GateIn, JBoss AS+Portal, we could use dependent libs from examples (the only place where they exist). That is community edition and then there wouldn't be a problem using community libs. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBDS-1410?page=com.atlassian.jira.plugin.sy... ] Snjezana Peco resolved JBDS-1410. --------------------------------- Fix Version/s: 4.0.0.CR1 (was: 3.0.2.GA) (was: 4.0.0.Beta2) Resolution: Done JSF Portlet delegate behaves differently for EPP 5.x (which contains the portletbridge and seam distribution) and for other Portal servers (EPP 4.3, JBoss Portal, JBoss AS + GateIn) EPP is recognized if there is the portletbridge directory with, at least two portletbridge*.jar file and the seam/lib directory containing jsf-facelets*.jar file. Regarding EPP 5.x, the user just need to select to include the Richfaces libs (the pbridge.png screenshot) and all the necessary libraries will be included from the EPP distribution (portlebridge libraries are from the EPP's portletbridge distribution and the Richfaces and dependent libraries from the EPP's Seam distribution. When using JBoss Portal or GateIn, those libraries are copied from a separate portletbridge distribution, Richfaces distribution and portletbridge's examples as described in the previous message. According to Tomas and Max's suggestion, the workaround for JBDS 3.0.1 would be the following: - remove portletbridge*.jar from WEB-INF/lib dir - add portletbridge*.jar (two files) from <EPP_HOME>/portletbridge to WEB-INF/lib - add the following jars: commons-beanutils.jar commons-digester.jar jsf-facelets.jar richfaces-api.jar richfaces-impl.jar richfaces-ui.jar from <EPP_HOME>/seam/lib to WEB-INF/lib We could also create project examples for EPP 5.x (Core Portlet, JSF Portlet, JSF Richfaces Portlet and Seam Portlet). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBDS-1410?page=com.atlassian.jira.plugin.sy... ] Dominik Pospisil reopened JBDS-1410: ------------------------------------ Still, I do not see any way how to add richfaces libraries to the project using new dynamic project wizard. There is only one option - Libraries provided by richfaces distribution, but even if I check this and browse RF richfaces-ui-3.3.3.Final distribution, libs are not added to the project. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBDS-1410?page=com.atlassian.jira.plugin.sy... ] Dominik Pospisil commented on JBDS-1410: ---------------------------------------- You said: if the user uses EPP containing seam, we would only enable using richfaces from EPP's Seam distro (the user wouldn't be able to choose a richfaces community edition; he would have to use richfaces from the EPP's seam library) Is this implemented? Maybe I am missing something, but I do not see this. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBDS-1410?page=com.atlassian.jira.plugin.sy... ] Snjezana Peco resolved JBDS-1410. --------------------------------- Resolution: Done This issue is fixed in 4.0.0.CR1 (trunk). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1410?page=com.atlassian.jira.plugin.... ] Dominik Pospisil reopened JBDS-1410: ------------------------------------ Snjezana, the richfaces libs are now added to the project correctly. However, RF components within a portlet do not by default render correctly, due to the following setting is added to web.xml by JBDS: <context-param> <param-name>org.richfaces.LoadStyleStrategy</param-name> <param-value>NONE</param-value> </context-param> <context-param> <param-name>org.richfaces.LoadScriptStrategy</param-name> <param-value>NONE</param-value> </context-param> Why we are adding these settings? Is there any particular reason for that? If this is left to default, seems that things would be much easier. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1410?page=com.atlassian.jira.plugin.... ] Dominik Pospisil commented on JBDS-1410: ---------------------------------------- With the above setting, richfaces styles and scripts must be loaded from each page manually... <a4j:loadStyle src="/faces/rfRes/org/richfaces/skin.xcss"/> <a4j:loadScript src="/faces/rfRes/org/richfaces/ui.pack.js" /> <a4j:loadScript src="/org/ajax4jsf/framework.pack.js" /> <a4j:loadScript src="faces/rfRes/org/richfaces/ui.pack.js" /> <a4j:loadScript src="org/ajax4jsf/framework.pack.js" /> -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1410?page=com.atlassian.jira.plugin.... ] Dominik Pospisil commented on JBDS-1410: ---------------------------------------- Great, thanks! -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira