TBH…
The API feel looks quite good.
There are some odd things but we discussed about it already:
- some common classes -> util like Describable etc…
- what do you think of replacing org.gatein.api.portal.Group and
org.gatein.api.portal.User by java.security.Principal ?
- is the interface org.gatein.portal.api.Formatted really necessary with respect to the
java.util.Formattable interface ?
- I would renamed Visibility.Flag to Visibility.Status
I would organize differently the exception to make it simpler : one single exception
ApiException but that uses error code enum instead of subtypes:
public enum ErrorCode {
PAGE_NOT_FOUND, etc…
}
On Dec 11, 2012, at 1:24 AM, Nick Scavelli <nscavell(a)redhat.com> wrote:
All,
I wanted to send an email to discuss the public API and more specifically the current
efforts around Navigation. I created a forum post here
https://community.jboss.org/thread/215521 to show the information a little easier;
however, since I think discussions are easier to follow in an email, I encourage people to
reply to this email rather then the forum for further discussion.
Javadoc published here:
http://gatein.github.com/gatein-api-java/ (I had problems with
Chrome cache, so clear cache if you get 404 errors)
Since the navigation part of the public API is the part we've been focusing on,
it's going to be the most complete in terms of design, javadoc, etc. So I am expecting
more feedback in this area as apposed to things like pages and sites.
- Nick
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev