OpenPortal Portlet Container is consumed
By karthiksudarshan on Jun 18, 2007
The OpenPortal build has started to consume the OpenPortal Portlet Container binaries on the fly :) This just goes to show how modular the Portlet Container itself is, and how easy it is to consume it. Moreover, it provides for innovation to happen in pieces. So contributors to the Portlet Container can continue to contribute knowing that it is not going to be just part of a server side component, but it will be part of an enterprise level Portal implementation.
The Ivy dependency management tool is being used to manage the dependency on the Portlet Container. This is part of the OpenPortal component based architecture, and is thus providing fruitful results. For instance, if a developer just wants to check out the portlets to test for compliance or to just get a feel of how it might look and work, the OpenPortal Portlet Container, which provides the runtime environment for Portlets, can be downloaded and used easily. The same can then be deployed on the enterprise class OpenPortal knowing that it will work fine, since the OpenPortal is just bundling the same Portlet Container that you tested on. Similarly other components will be consumed on the fly thus providing the level of flexibility yearned by everyone in the open community.
So, if you are still on the fence about the OpenPortal community, just be careful, for the fence is becoming thinner and there is a good chance that you will be forced to jump over it to our side very soon :)