+1 from me. I'm very glad to see that CXF is welcome in Syncope.
Being able to use the full set of CXF features as well as being able to easily plugin custom interceptors will be a great benefit to syncope as well as to our current project. Using a standard API (by using JAX-WS annotations) also has the benefit, that anyone could also replace CXF with another Webservice-Stack easily, if desired (hopefully there is no reason to replace CXF ;-) ). Best regards Jan > -----Original Message----- > From: Francesco Chicchiriccò [mailto:[email protected]] > Sent: Donnerstag, 25. Oktober 2012 16:31 > To: [email protected] > Subject: Re: [DISCUSS] - Switch to use Apache CXF for REST interface > > On 25/10/2012 15:51, Colm O hEigeartaigh wrote: > > 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. > > Hi Colm, > believe it or not, it's quite some time that I am mumbling about this. > > I was actually starting from SYNCOPE-150, e.g. providing a rich Java client > library allowing to call REST methods transparently from proper Java APIs, but > maybe it's too complex for the moment. > > Another reason that made me think about this is implementing a SCIM > interface (SYNCOPE-152). > > Anyway, I am completely +1 for this, especially if CXF could give us the > additional bonus of some semi-automatic REST (and SOAP) APIs > documentation... (see SYNCOPE-151) > > > 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/release/s > > > amples/oauth/server/src/main/java/demo/oauth/server/SampleResourceP > rov > > ider.java?view=markup > > Hey, it looks very similar to Cocoon 3 REST controllers :-) > http://svn.apache.org/viewvc/cocoon/cocoon3/trunk/cocoon- > sample/src/main/java/org/apache/cocoon/sample/controller/DemoRESTCo > ntroller.java?view=markup > > > Regards. > > -- > Francesco Chicchiriccò > > ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member > http://people.apache.org/~ilgrosso/
