[ https://jira.jboss.org/jira/browse/JBDS-1018?page=com.atlassian.jira.plug... ] Snjezana Peco commented on JBDS-1018: ------------------------------------- I have added the following functionalities: - the Portlet engine recognizes the GateIn and EPP server and offers Portlet facets for them - the Portlet facet configures web.xml if the target server is Gatein or EPP - the Java Portlet and JSF portlet can be deployed to the GateIn or EPP server - modified the Seam portlet archetype (seam-basic, 2.0.1) to work with GateIn and/or EPP There is a problem with deploying a Seam portlet created using the new Seam Web wizard because portletbridge-impl.jar and jboss-seam.jar contain the org.jboss.seam.jsf package. A Seam EAR application created with the new Seam Web wizard contains libraries in the WAR project (portletbridge, jsf-facelets.jar, for instance) and libraries in the EAR project (jboss-seam.jar). JBoss AS loads those libraries using different classloaders. That's why portletbridge can't call protected methods from the org.jboss.seam.jsf package. Seam WAR application can't be deployed when using signed portletbridge and jboss-seam libraries. I have tried to use Seam and Portletbridge from the EPP distribution and got the error "signer information does not match signer information of other classes in the same package". When using the standard Seam 2.2.0 and portletbridge 2.0.0.BETA, the Seam portlet is created correctly, but there is a problem when loading css resources from the stylesheet directory (error "Static resource not found for path /stylesheet/theme.xcss"). It is possible that the problem is described in https://jira.jboss.org/jira/browse/JBIDE-4500. Copying the stylesheet to WEB-INF/classes fixes the problem. I will try to find a solution for the Seam EAR portlet. Currently, we can use the portletbridge Seam archetype which creates a project containing libraries in the EAR project and can be deployed to EPP/GateIn. It is possible to use archetypes described on https://jira.jboss.org/jira/browse/JBIDE-4922 that create JBoos Tools EAR project with all the JBoss Tools features or the standard portletbridge archetypes described on http://vimeo.com/7255033 I would also suggest adding the following actions to the Servers view (when the user right-clicks the server) - in case of the EPP, Gatein or JBoss Portal server, the user would call "Open portalpage" that would open the http://<host>:<port>/portal URL in a browser which would fix https://jira.jboss.org/jira/browse/JBIDE-3908 - in case of the JBoss AS >= 5.0 (EAP/EPP/SOA >= 5.0), the user would call the "Admin server" action that would open the http://<host>:<port/admin-console URL in a browser We could add some more actions in a similar way (JBoss AS documentation, Open JMX console ...) and, eventually, could create a separate group for them within the server's context menu. I have tested the portlet feature using GateIn Beta4 and EPP 5.0 ER01 server. TODO - adding the portletbridge libraries from <SERVER_HOME>/../portletbridge for the EPP server by the Portlet Runtime target provider - testing the Seam portlet -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5741?page=com.atlassian.jira.plu... ] Max Rydahl Andersen moved JBDS-1018 to JBIDE-5741: -------------------------------------------------- Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio)) Key: JBIDE-5741 (was: JBDS-1018) Fix Version/s: 3.1.0.CR2 (was: 3.0.0.CR2) -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5741?page=com.atlassian.jira.plu... ] Snjezana Peco commented on JBIDE-5741: -------------------------------------- See PBR-139 -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5741?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-5741: -------------------------------------------- So if PBR-139 gets fixed are we good to go ? i.e. "normal" portlet functionallity will work, but jsf/seam integration will not correct ? And that is a runtime problem, not something we can fix. About the "open xyz" features lets put that in a separate jira. If we can only add the relevant menu for portal if portal is present then that definitly makes sense though. -- 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

[ https://jira.jboss.org/browse/JBIDE-5741?page=com.atlassian.jira.plugin.s... ] Snjezana Peco updated JBIDE-5741: --------------------------------- Fix Version/s: 3.2.0.M1 3.1.0.GA (was: 3.2.x) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira