So looking into the REST part of the api, I have a few questions here
with the design of the API:
1) Does the API assume that only a superuser is ever going to use it, or
does it assume that other logged in (or unauthenticated) users will be
using it as well?
Ie I want to create a navigation/menu portlet. If I retrieve the nodes,
will I get only the nodes I have permission to view, or do I have to
retrieve them all and manually filter out the ones I don't have
permission to access?
It makes more sense for the rest service to only return elements the
user has permission to access, but we can filter that on the rest side
if needed.
2) Are we still going to be using java resources for internalization?
On Fri, 2011-07-08 at 17:46 +0200, Christophe Laprun wrote:
Folks,
I've committed the initial code for the API implementation:
https://source.jboss.org/changelog/GateIn?cs=6849
I've created a new branch for this work:
https://svn.jboss.org/repos/gatein/portal/branches/api
It currently won't compile because there is no deployed artifact for the prototype
API.
Action items:
- Please comment on code organization on the portal side.
- Please confirm the artifact and group IDs for the API proper and implementation Maven
artifacts.
- Please confirm API versioning scheme.
I need this information ASAP so that I can push forward with further implementation.
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
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev