[JBoss-dev] [Design of JBoss Portal] - Re: Will the Portal support deployment to other AS?
Portal heavily depends on the Servlet container implementation. Different vendor?s implementations known to be non compatible in some areas (thread allocation per request, redirect, include, forward, etc), that creates a lot of problems for portlet container implementation. In the future portlet container may be included in the standard j2ee server (j2ee 1.6). There is no standard contract defined between portal and portlet container, so it will be custom implementation for each supported AS. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3873453#3873453 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3873453 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Will the Portal support deployment to other AS?
today a given JBoss Portal version is targeted to run on a defined set of JBoss AS versions because JBoss Portal is part of JEMS. When we will support more servlet containers, we will ensure that the portlet container implementation is certified on JBoss AS. So far we cannot guarantee anything for other containers. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3873455#3873455 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3873455 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Will the Portal support deployment to other AS?
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=bbop=viewtopicp=3873490#3873490 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Will the Portal support deployment to other AS?
jjustice wrote : 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. The short technical answer is that it depends on the jboss5 pojo framework. jjustice wrote : | 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. The decision was made early on in the project to focus on JBoss AS, for reasons of resource-usage. It was much easier for us to focus on one container and do it well than focus on 5 containers and do it poorly with the fixed amount of resources we originally had. Aside from developing the portal, we have to hand the portal code over to our QA labs for testing. It also becomes a resource-usage issue then. jjustice wrote : | 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. :) This sentence confused me. ;-) View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3873495#3873495 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3873495 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Will the Portal support deployment to other AS?
Today JBoss Portal uses JBoss microkernel as integration bus for our services and in the future it will use JBoss microcontainer the next generation of the microkernel. Technically, JBoss upcoming micro container will run in any VM and will provide us portability for that layer. So the other technical aspect is about the servlet container layer on which the portal depends and that has already been adressed in a post earlier. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3873498#3873498 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3873498 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [Design of JBoss Portal] - Re: Will the Portal support deployment to other AS?
Eventually this will be something we look at, but it needs the jboss5 pojo framework to be a reality. We also have a lot of implementation work that we certainly don't want to impeded by having to worry about cross platform support. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3873306#3873306 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3873306 --- 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=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
