Dear All,
not that proud to present the JSR 279 spec we filed in the middle of December.
The dash and its imprints can be seen quite clearly.
Well, the implementation side wanted a freezed version and now they have one:
http://jcp.org/aboutJava/communityprocess/pr/jsr279/index2.html
The API enables relatively easy way to read and update Atom feeds.
The feedback from RI implementation will stabilize the spec and trim most
of the errors. As well as comments, which are also welcome.
One comment from our EG:
There is no attempt at binding services to Java interfaces and other high-level abstractions. Some of the interaction modes come across as too low-level. For example take the blog update example (p125). There is some attempt at abstracting the blog entries, which is good. But the interaction is very low level -- for example there are some inlined http status codes there which users should not have to deal with.
Agreed. The problem is not yet solved.
Maybe an ErrorMessage inherited from a Message could solve this,
basically the information 'ok-or-not' is enough, checking the
response type would then suffice. Also, I think, links to other resources
(a newly created resource in the Location endpoint, too) should be accessible
a more convenient way.
- Pia