+1 for the branch. this should be the fastest way to make a complete shift and solve all upcoming issues one by one.
I've got approval from my manager to spend quite some time during the next few weeks to get this task done. This way we should be able to keep the merging effort relatively low. Regards Jan > -----Original Message----- > From: Jean-Baptiste Onofré [mailto:[email protected]] > Sent: Freitag, 26. Oktober 2012 12:50 > To: [email protected] > Subject: Re: [DISCUSS] - Switch to use Apache CXF for REST interface > > Hi Francesco, > > Agree, I think a branch makes sense. > > Regards > JB > > On 10/26/2012 11:57 AM, Francesco Chicchiriccò wrote: > > On 26/10/2012 11:50, Jan Bernhardt wrote: > >> Sounds like everyone agrees with Colm's proposal to switch from Spring > to CXF (concerning REST Interface). > >> > >> I would like to volunteer for this task and provide a patch. > > > > Wow, that sounds very cool! > > > >> Should I create a JIRA ticket and assign this task to myself? > > > > I would say so; actually, this activity has a very deep impact on > > either the core (actually exposing the REST methods), the admin > > console (as primary REST client delegating all its functionality to > > this) and possibly the client. > > Hence, I would think that any partial commit would break the build > > (and more...). > > > > What's the best way to handle this? A separate branch from trunk to be > > eventually merged once everything is working with CXF? > > > > WDYT? > > > > Best regards. > > > >>> -----Original Message----- > >>> From: Denis Signoretto [mailto:[email protected]] > >>> Sent: Freitag, 26. Oktober 2012 10:02 > >>> To: [email protected] > >>> Subject: R: [DISCUSS] - Switch to use Apache CXF for REST interface > >>> > >>> +1 > >>> > >>>> -----Messaggio originale----- > >>>> Da: Colm O hEigeartaigh [mailto:[email protected]] > >>>> Inviato: giovedì 25 ottobre 2012 15:52 > >>>> A: [email protected] > >>>> Oggetto: [DISCUSS] - Switch to use Apache CXF for REST interface > >>>> > >>>> > >>>> Hi all, > >>>> > >>>> I would like to initiate a discussion about the merits of switching > >>>> to use Apache CXF to provide the REST interface, instead of the > >>>> current approach based on the Spring web stuff. Obviously, this is > >>>> quite a significant change to what's there at the moment, but I > >>>> want to see if other developers are at least open to the possibility. > >>>> > >>>> Here are some reasons to switch to using Apache CXF: > >>>> > >>>> a) Syncope does not use standard JAX-RS annotations, but rather > >>>> custom Spring annotations. > >>>> b) Using Apache CXF would give us access to the full power and > >>>> flexibility of the CXF stack. For example: > >>>> - We could add SOAP interfaces. > >>>> - We could use CXF interceptors...automatic support for a large > >>>> number of transports + security things like O-Auth, SAML, Kerberos, > >>>> WS-Trust etc. > >>>> c) (Trivial point) It is good to use fellow Apache products where > >>>> possible. > >>>> > >>>> What do you think? It is something that either I or another Talend > >>>> person could contribute to the product. Just to give a sample of > >>>> what the REST controllers might look like, see an example from the > >>>> CXF oauth demo: > >>>> > >>>> http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/releas > >>>> > e/samples/oauth/server/src/main/java/demo/oauth/server/SampleResour > >>>> ceProvider.java?view=markup > > > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com
