Re: [gatein-dev] Initial commit on API implementation
after a rapid at the implementation, you shall not use the MOP API directly for various
reasons
1/ performance, the component mop does not manage caching but services do
2/ some service provide value added on top of MOP (the NavigationService)
3/ you will not access some features managed by the portal (such as extended I18N)
instead you should use the various services in front of it:
1/ ModelDataStorage (legacy service) for portal / pages : not great to use but that's
the way it is until it is rewritten
2/ NavigationService for navigation
3/ DescriptionService for navigation i18n
On Jul 8, 2011, at 5:46 PM, 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