On Thu, Aug 16, 2012 at 10:46 PM, Christian Riedel <[email protected]> wrote:
> Having support for mongodb is a good thing but I think making morphia the > default mapper is not the best choice. > We have here some nice integration with the jackson mapper[1], which is not > so much hibernate-like and gives much more power over everything (we've > started with morphia as well). I could open-source the integration with > jackson in a couple of days just to have some more options. > > @Howard: I think these tools would also be sufficient to add the features you > are talking about. > Otherwise: reinvent the wheel and write a tapestry-json-mapper... Your path has been my first pass and I've made some experiment applying the same technologies used in tapestry "reserved" packages (pages, components, mixins...) to the "mongodb-entities" package just to tech each entity how to work with mongo and pojo, that path is definitely what sounds better for the future. I just wanted to have something out to spread the sparks of discussion. Morphia is simply a fact of quickness in the implementation, in fact I've tested Jongo (you can see the code in one of the module) which use Jackson under the hood and that has given me the idea illustrated above BTW in the above experiment there was some sort of a very limited JSON(Object|Array) to Entity coercion. Any contribution is welcome -- Massimo --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
