[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wink-dev
Subject:    Re: start contributing to Wink with implementing google-gson provider
From:       Daniel Kulp <dkulp () apache ! org>
Date:       2012-10-25 16:29:57
Message-ID: 05D0BE31-35F0-45AD-9766-A69B0F67A631 () apache ! org
[Download RAW message or body]


On Oct 25, 2012, at 12:04 PM, Shameera Rathnayaka <shameerainfo@gmail.com> wrote:

> Hi Daniel,
> 
> On Mon, Oct 22, 2012 at 7:06 PM, Daniel Kulp <dkulp@apache.org> wrote:
> 
> > 
> > Just an aside, this is something that the CXF JAX-RS implementation would
> > love to have as well.  CXF currently does not have anything gson related.
> > With CXF being used as the JAX-RS implementation for TomEE/JAX-RS, there
> > could be a lot of people that could benefit from it.
> > 
> 
> What you suggest is implement gson support for CXF or if i implement a new
> provider for wink using gson there is a feasibility to add it to CXF too?

Depends on how you write it.   If you implement the support using standard JAX-RS \
MessageBodyReader/MessageBodyWriter interfaces and avoid the Wink and CXF internals, \
it's likely that it would "just work" for both CXF and Wink (and Jersey and \
RestEasy).

The part that would be different is how it's plugged into the runtime.   For CXF, it \
would likely be user supplied Spring configuration.  Not sure on the others. 

CXF has a separate jar/bundle where we have many of the extra providers:
http://svn.apache.org/repos/asf/cxf/trunk/rt/rs/extensions/providers/

That said, most of the stuff in there does have some tie into CXF internals for \
things like configuration or XML/StAX utilities and such.


> > If it can be made "generic" enough (maybe just using the JAX-RS api's) it
> > may be something that the two implementations could share.   Or maybe work
> > on becoming a committer on both Wink and CXF.   :-)
> > 
> 
> > Seriously, there is a severe lack of cooperation between Wink and CXF.
> > Both projects could likely benefit if there was more cooperation.
> > 
> 
> As i am not familiar with CXF I will go through CXF documentations too.But
> if you could explain the scenario(how we can use wink implementations for
> CXF) here it would be helpful to me to understand the process.

Not having seen any of your code, I just don't know how "generic" it is in respects \
to using just the pure JAX-RS API's and extension mechanisms.  JAX-RS has the \
Reader/Writer interfaces that are specifically designed to allow plugging in \
additional mappings like this and, IMO, it would likely be a good idea to use those \
interfaces if possible to make it portable across JAX-RS implementations.

Dan




> 
> Thanks,
> Shameera.
> 
> 
> > 
> > Dan
> > 
> > 
> > 
> > > Other than that i would like to be familiar with the code base. If
> > somebody
> > > can point out few potential bugs to fix in startup that would be a great
> > > help.
> > > 
> > > [0]
> > > 
> > https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2012/shameera/18002
> > 
> > > [1] https://issues.apache.org/jira/browse/AXIS2-3967
> > > 
> > > Thanks,
> > > Shameera.
> > > 
> > > --
> > > Shameera Rathnayaka
> > > Undergraduate
> > > Department of Computer Science and Engineering
> > > University of Moratuwa.
> > > Sri Lanka.
> > > 
> > > Blog : http://shameerarathnayaka.blogspot.com/
> > 
> > --
> > Daniel Kulp
> > dkulp@apache.org - http://dankulp.com/blog
> > Talend Community Coder - http://coders.talend.com
> > 
> > 
> 
> 
> -- 
> Shameera Rathnayaka
> Undergraduate
> Department of Computer Science and Engineering
> University of Moratuwa.
> Sri Lanka.
> 
> Blog : http://shameerarathnayaka.blogspot.com/

-- 
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com


[prev in list] [next in list] [prev in thread] [next in thread]