On Mon, Jun 1, 2009 at 11:55 PM, ant elder <[email protected]> wrote: > On Thu, May 28, 2009 at 10:18 PM, Luciano Resende <[email protected]> > wrote: >> Tuscany currently supports two Collection interfaces for the Atom >> Binding, one based on the Apache Abdera models, and another based on >> generics that uses Tuscany Databinding to transform the atom content >> to business objects. TUSCANY-2939 expose the scenario where you want >> to use the generic collection and reference a regular atom feed with >> html entries, which causes NPE exceptions due to databinding framework >> trying to parse html as xml. For now, I have a fix/workaround that >> checks the feed entry content type, and only uses the databinding >> framework when the contents are XML and default back to a Item when >> the content type is HTML, but wanted to hear from the databinding >> experts if there is any better solution here... >> >> Thoughts ? >> > > Would the ideal solution be to avoid application code needing to use > those Collection interfaces? We can do that now that the Tuscany > runtime has the wireformat and operation selection mechanisms so all > this protocol specific code could be put into custom > wireformat/operation selectors. >
I was hopping that JAX-RS would be the best solution here, but I'm open to ideas... Using wireformat/operation selectors, what would be the user experience to map HTTP operations to their implementation operations when developing a new SCA component; also, how to enforce that these operations follow a giving expected pattern ? -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/
