[ https://jira.jboss.org/jira/browse/JBIDE-3642?page=com.atlassian.jira.plu... ] Snjezana Peco commented on JBIDE-3642: -------------------------------------- These constants are used to check if a JBoss Server has portal deployer. If portal deployer exists, the portlet facet adds the portlet-api library to the classpath container. Within the JBoss Portal server Comunity Edition/JBoss Portletcontainer, portal deployer exists only in the default configuration. If we use "programmatic" configuration (Rob's proposal) for testing portlet capabilities and adding the library, the JBoss Portal Server with all and minimal configuration won't be recognized as a portlet capable portal server. The portlet-api library won't be added to the container. If we use "hard-coded" configuration (the default conf.), the JBoss Portal server will always be recognized as portlet capable, but deployment will fail in case of using all/minimal configuration. There is yet another use case : - create the JBoss Portal server with the default configuration (portlet deployer exists) - add some portlet - change the configuration to minimal (portlet deployer doesn't exist) If we use "programmatic" configuration, the classpath container will be invalidated (the classpath container won't contain the portlet-api library); the project will have compile errors. If we use "hard-coded" configuration, the project will be compiled, but deployment will fail. I am not sure which of these two methods is better. As to the EPP distribution, there is portlet deployer in all,default and production configuration. The Portlet facet won't recognize portal deployer because it is placed in jboss-portal-ha.sar. I will create a new jira for this issue. -- 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-3642?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-3642: -------------------------------------------- Thomas, what is the justification/difference between using jboss-portal.sar and jboss-portal-ha.sar ? ha is for high availability ? -- 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-3642?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-3642: -------------------------------------------- ok, so both names can be seen in the wild for both EPP and .org portal ? -- 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-3642?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-3642: -------------------------------------------- Ok, so we should simply just look for <config>/deploy/jboss-portal.sar and <config>/deploy/jboss-portal-ha.sar to detect if Portal is present in both EPP or .org Does portal and epp.sar's have a consistent version numbering inside the .sar somewhere ? i.e. 2.7.0 in org and 2.7.0_AP for EPP or something ? Something we can use to detect if it is .org or epp, plus have a version number to show/validate against. -- 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-3642?page=com.atlassian.jira.plu... ] Snjezana Peco updated JBIDE-3642: --------------------------------- Fix Version/s: 3.0.0.GA -- 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