Re: [gatein-dev] Initial commit on API implementation
On Jul 8, 2011, at 6:07 PM, Julien Viet wrote:
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
OK. This is not the kind of feedback I was expecting but it's good to know. :)
2/ NavigationService for navigation
I was planning on using this.
3/ DescriptionService for navigation i18n
This is scheduled for the next iteration.
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