Thank you for the responses. However, I see two kinds of answers here. One saying that eventually it would be nice for JBoss Portal to be deployable to other AS, and the other saying that there are technical reasons why this won't happen. I understand that the Portal-PortletContainer contract is not standardized, but this doesn't prevent Portals like Liferay and eXo from being deployed to different AS. I'm new to JBoss, so I don't really know what JEMS is or what the implications of that link are, but it does seem that the JBoss team may have made choices to couple the Portal to JBoss in ways that are not an immediate consequence of the standards or lack of standards.
That being said, if worse comes to worse, we'd still be much better off from a cost of licensing standpoint if we have to deploy JBoss to deliver our Portal to a client who already has WebSphere than we would be if we had to deploy WebSphere to deliver our Portal to a client who already has JBoss. :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873490#3873490 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873490 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
