[Building Sakai] Any Comments on org.codehaus.jackson ??

[Steve Swinsburg]

It would actually be pretty trivial to move all of the EB entity providers over to a servlet style setup, map on the same paths using Jersey and keep the same input and output config. Though we also need to honour the other capabilities that can be performed through EB that may not have equivalents, but not impossible.

The nontrivial part would be wiring up registration code so that separate 'providers' in the various webapps could all participate under /direct. Though it has been mentioned before that the providers should be versioned like an API, so maybe they should all be in the one webapp?

I do like EB, but its possible to do what it does in other ways for sure. Part of Project Keitai will actually be looking at the performance of Entity Broker so this is a very timely discussion to be had.

cheers,
Steve


On 20/06/2013, at 8:55 PM, Adrian Fish <adrian.r.fish at gmail.com> wrote:

> Scalatra uses Jackson for its JSON support.
> 
> http://www.scalatra.org/guides/formats/json.html
> 
> I wonder whether it's worth at some point discussing whether EB as it stands is a good fit for actually mapping REST paths onto functionality? ActionsExecutable does a RESTlet type job in that you can pick out path components but in the end you just end up with an entity provider with one big executable action and some private methods for handling the incoming paths. What I'd like to do is just map paths onto handlers without repeatedly writing path parsing boilerplate.
> 
> EB does a good job and fills a gap, but it has to be maintained so it's perhaps worth considering whether we can use a more broadly used REST (and JSON) framework.
> 
> Cheers,
> Adrian.
> 
> 
> On 20 June 2013 00:27, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:
> Here's another perf comparison
> 
> http://blog.novoj.net/2012/02/05/json-java-parsers-generators-microbenchmark/
> 
> Sent from my iPhone
> 
> On 20/06/2013, at 2:30, "Zach A. Thomas" <zach.thomas at gmail.com> wrote:
> 
>> On the performance question, I have referred to this benchmark in the past:
>> https://github.com/eishay/jvm-serializers/wiki
>> 
>> As for other options, can you recommend an alternative?
>> 
>> Zach
>> On Jun 19, 2013, at 10:33 AM, Aaron Zeckoski <azeckoski at unicon.net> wrote:
>> 
>>>> 1) Jackson is the best/fastest JSON reader/writer and Object/JSON mapper. I would love to see us standardize on this. I am using in my own EntityProviders for output.
>>> 
>>> That's an opinion I strongly disagree with so I would not be a fan of
>>> us standardizing on this at all. I would like to see some strong
>>> evidence to backup this statement. I attempted to use this for JSON
>>> handling in multiple projects and we settled on other options in every
>>> case (re: matterhorn, dspace, EB, etc.). The handling of maps and
>>> collections was especially problematic (at the time anyway).
>> 
> 
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> 
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> 
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130620/bae9b884/attachment.html