I see what you mean Hassan. I had a look at how the core portal engine accesses the portlets and it looks like it uses the plugins context to access it and this is just hidden from the user.
thanks On Mon, Nov 16, 2009 at 7:11 PM, Hassan Schroeder < hassan.schroe...@gmail.com> wrote: > On Mon, Nov 16, 2009 at 10:51 AM, Ziggy <zigg...@gmail.com> wrote: > > > I was recently looking at a CMS portal and found that the portal allowed > > plugins/application to be deployed as war files. The plugins themselves > are > > portlets so not quite the type of application i am using. > > > > Is it the case that maybe it is possible with portlets but not standard > > servlet based webapps? > > Sure, the whole point of a "portal" is to integrate non-related apps > and data sources. So you access the portal context which basically > proxies in the output of those "plugins". > > You could certainly integrate the output of other contexts into your > primary one, using iframes, AJAX widgets, backend web services, > etc. but ultimately they're still separate contexts. > > -- > Hassan Schroeder ------------------------ hassan.schroe...@gmail.com > twitter: @hassan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
