[ 
https://issues.apache.org/jira/browse/OODT-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768938#comment-13768938
 ] 

Ross Laidlaw commented on OODT-612:
-----------------------------------

Hi Rishi,

I've attached my latest patch.  I've made a lot of progress but still have a 
few things to add and tidy up.

I've added the following:

* Extension mappings (.file, .zip, .rdf, .rss, .xml, .json)
* Default XML and JSON outputs via JAXB
* RSS writers for references, products, datasets and transfers
* RDF writer for datasets
* Full mapping of original URLs to new scheme via an interceptor (might not be 
the best way of doing it!)
* Configurations for RSS and RDF (in progress) with the ability to have 
multiple configurations per format (as mentioned in OODT-613)

Todo:
* documentation (including Velocity stuff)
* formalise unit tests (I have various pieces of unit tests, not shown in 
patch, will patch them soon)
* finalise configurations (nearly there, just need to tidy up and test)
* dataset filters (i.e. filter on product type metadata or product metadata)

More details/progress to follow soon! :)

                
> Add content writers for XML, JSON, RDF and RSS
> ----------------------------------------------
>
>                 Key: OODT-612
>                 URL: https://issues.apache.org/jira/browse/OODT-612
>             Project: OODT
>          Issue Type: Sub-task
>          Components: product server
>    Affects Versions: 0.6
>            Reporter: Ross Laidlaw
>            Assignee: Ross Laidlaw
>              Labels: gsoc2013
>             Fix For: 0.7
>
>         Attachments: OODT-612+613.rlaidlaw.2013-09-16.patch.txt, 
> OODT-612.rlaidlaw.2013-09-06.patch.txt
>
>
> Convert the service added by OODT-611 to use MessageBodyWriters instead.  Use 
> JAXB annotations to enable marshalling of resource classes to XML and JSON.  
> Add custom MessageBodyWriters for RDF and RSS.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to