search

maheshwarirohit87 / typica

Automatically exported from code.google.com/p/typica
Apache License 2.0
0 stars 0 forks source link

API enchancement #69

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The current API enforeces to use typica model objects. i.e. The current 
API returns only data in typica defined model/pojo object. This request is 
to decouple api signature from typica model.

i.e. protected List<ImageDescription> describeImages(Map<String, String> 
params) throws EC2Exception {

Above method mandates to caller to use ImageDescription object. Instead, 
the caller should have the option to get JAXB converted POJO object and 
covert as required.
i.e.

protected List<DescribeImagesResponseInfoType> describeImages(Map<String, 
String> params) throws EC2Exception

Original issue reported on code.google.com by kulkarni...@gmail.com on 21 Nov 2009 at 5:02

GoogleCodeExporter commented 9 years ago 
This was done on purpose. The decision to decouple the API from the underlying 
XML 
marshalling/unmarshalling code is (as seen by many) a good design. That way, we 
could 
switch to something, perhaps JIBX and not have users change anything more than 
the 
included jars.

Original comment by dkavan...@gmail.com on 17 Feb 2010 at 9:36