Re: [gatein-dev] GateIn Api Discussion
On Jun 1, 2011, at 3:54 PM, Christophe Laprun wrote:
> 2/ There are two parts which are out of scope of the current API
that we should remove which are the portal container and the UI component.
>
> The current API should not mention the portal container and every work should be
scoped to the current portal container. This notion exist for isolating deployments (for
instance one portal container per customer). I think Matt has this right so far but not
Chris API that mentions it.
OK. I took the point of view that the API needed to be able to create portal containers
and portals and I indeed didn't scope the objects to the current portal. I will change
that.
Actually, thinking about it some more, it won't work for the navigation portlet use
case where you need to be able to list all the different portals a user has access to… So,
how do you propose that use case be handled?
Cordialement / Best,
Chris
==
Principal Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.
Follow GateIn: http://blog.gatein.org / http://twitter.com/gatein
Follow me: http://metacosm.info/metacosm / http://twitter.com/metacosm