[ 
https://issues.apache.org/jira/browse/TUSCANY-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605406#action_12605406
 ] 

Jean-Sebastien Delfino commented on TUSCANY-2393:
-------------------------------------------------

One more requirement:

Better error reporting:
- a mapping between common runtime errors and HTTP status codes should be 
defined
- somebody should investigate how to map business exceptions to Atom responses 
(or define a fixed set of business exceptions that can be reported, like we've 
done for the NotFoundException)
- the Atom Javascript client proxy should report these exceptions in a usable 
form to the Javascript client program.


> Complete Atom binding implementation
> ------------------------------------
>
>                 Key: TUSCANY-2393
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2393
>             Project: Tuscany
>          Issue Type: Wish
>          Components: Java SCA ATOM Binding Extension
>            Reporter: Jean-Sebastien Delfino
>             Fix For: Java-SCA-Next
>
>
> I would like to see the following features completed in the Tuscany Atom 
> binding:
> - support for eTags, last-modified headers, complete support for location 
> header
> - on the client side, caching using eTag and/or lastModified
> - the ability to negociate content types (XML, JSON etc) and use the 
> corresponding Tuscany databindings to provide data with the requested content 
> type
> - support for postMedia and putMedia, including the ability to stream that 
> content in the target application component
> - support for security as required by the Atompub spec, and mapping between 
> the security features and corresponding SCA security policies
> - complete generation of an AtomPub workspace/service document, for a 
> service, component or a group of related components (potentially in a 
> composite), somebody should study this to find the correct granularity level
> - samples/scenarios that help us explore how to implement relationships 
> between two (Atom) collections of resources (e.g. Customer and Account, with 
> a Customer owning multiple Accounts)
> - A proper Javascript object model for an Atom collection and Atom entries to 
> facilitate the use of Atom in Javascript clients, modeled after the Abdera 
> model for collection and entry.
> - A Javascript model for Atom collections and entries mirroring the Tuscany 
> Java data.Collection interface, providing simple access to business data 
> objects in an Atom collection.  
> - Finally somebody should do a pass through the Atom and AtomPub specs and 
> make sure that we're not missing any big feature from the spec.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to