there are too many packages which is noise and makes less API less decodable when you look
at the packages globally.
- some package are sharing more or less the same concern : commons / util
- I guess i18n could be also in commons
- the exceptions package would be avoided and exceptions put in the org.gatein.api
package
at the end I would rather see:
org.gatein.api
org.gatein.api.commons
org.gatein.api.portal
org.gatein.api.security
more readable.
Julien Viet
julienviet.com
On Monday, July 9, 2012 at 5:38 PM, Boleslaw Dawidowicz wrote:
We would like to share some early stage of work around GateIn public
Java APIs.
Currently it covers mostly all operations around MOP focusing on "Navigation
Portlet" and "Sites Management" use cases. What is missing and mainly
excluded at the moment is app registry and page layouts which will be covered later.
Initial draft of the API is released here:
https://github.com/gatein/gatein-api-java/tree/1.0.0.Beta03
Javadoc:
http://gatein.github.com/gatein-api-java/
Implementation:
https://github.com/nscavell/gatein-portal/tree/api-1.0.0.Beta03/component...
We don't have much examples or documentation besides Javadoc and test cases at the
moment - those will follow.
In the implementation there is very bare and minimal example of NavigationPortlet:
https://github.com/nscavell/gatein-portal/blob/api-1.0.0.Beta03/examples/...
Most of credits go to Nick who has been leading this work past few weeks. It also builds
on top of previous implementation from Chris and Julien. Thanks guys for your hard work!
Again this is quite an early preview but we wanted to release it for review and feedback.
Please take a look and comment!
Bolek
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org (mailto:gatein-dev@lists.jboss.org)
https://lists.jboss.org/mailman/listinfo/gatein-dev