it's a rats nest at the moment. I'd like to see some way of registering/injecting new conversion code for BeanXStreamAtomConverter so modules can add their custom conversions but have not had time to work that out as of yet.
On Mon, Oct 11, 2010 at 2:32 PM, Art Corl Jr <[email protected]> wrote: > Hi, > > We're adding the xstream implementation for mapping JSON activitystreams > to ATOM & XML, and would like advice on how to handle the > configuration/dependencies. > > AtomEntry class (in the shindig-social-api project) must be updated > (ActivityEntryImpl object is being passed in). However, these updates need > to make references to classes in shindig-extras (e.g. > ActiityEntry.getTitle() etc.). This creates a circular dependency > (shindig-extra already references shindig-social-api). > > One idea is to create a sublass of AtomEntry (ASAtomEntry) and put it in > shindig-extras. But, the instantiation flow for ASAtomEntry would still > originate in social-api ... SocialApiGuiceModule (social-api) -> > BeanXStreamAtomConverter (social-api) -> AtomFeed (social-api) -> > AtomEntry (social-api). So, we could also subclass all (or most) of those > class as well (ASSocialApiGuiceModue, for example). > > Any better way to do this? > > Thanks! > Art Corl > > [email protected] > -- Paul Lindner -- [email protected] -- linkedin.com/in/plindner
