Hi Chris, Yes I agree they are completly different. And I also don't want SOAP in Rave. Nobody needs it.
But believe me. I have and implementation that does both specs from exactly the same code. I have it working right now. :D I mean CXF is by far better alternative than any other I know. I would propose install everything in Apache Cellar or at least Karaf or any other OSGi container. But I tried and up to now it's not a real alternative. There is a mess in dependencies that must be resolved before going serious with this kind of approach. The advantag would be that it will provide a real separation from the frontend. > > Hi > > > > Using Apache CXF will allow to enable even SOAP at 0 cost. > > > > CXF can support JAX-WS, you are correct, but it won't give SOAP support for > zero cost. JAX-RS and JAX-WS are two completely different specs and have > different approaches. I have no intention of adding a SOAP endpoint to Rave > at this point in time. > > > > > I have no vote but +1 on Apache CXF [image: ;-)] > > > > I even have the structure ready, already wired to Spring for beans. I can > > send you a skeleton ready for start implementing services. > > So you can modify it adapt, and start coding. > > > > In my case I use to use hibernate that makes no point here, but it has an > > advantage. It creates pojo and DTO on the fly by reverse engineer database. > > Maybe there's something similar in openJPA. > > > > > > > > El mié, 27-02-2013 a las 17:26 -0800, Raminder Singh escribió: > > > > I like the idea. This is aligned with our goal of rave data as REST API > > discussed at ApacheCon Meetup [1]. It will help to remove JSP dependency > > and help multiple views. What are ideas on securing these service? > > > > Thanks > > Raminder > > > > 1. http://wiki.apache.org/rave/MeetupApacheConNa2013 > > > > On Feb 27, 2013, at 4:46 PM, Sean Cooper wrote: > > > +1> > I am a big fan of simplifying.> On Feb 27, 2013 7:30 PM, "Ate > > > Douma" <[email protected]> wrote:> >> On Feb 27, 2013 2:09 PM, "Chris Geer" > > > <[email protected]> wrote:>>> >>> As part of our plan moving forward > > > we've discussed developing more robust>>> RESTful web services which > > > provide access to all Rave functions. Before>> we>>> started this I > > > wanted to ask the question regarding what tools we use to>>> develop > > > these. Right now our web services are using Spring MVC as the>>> > > > technology of choice mainly because we use Spring MVC for the whole UI>>> > > > framework. As we try and remove the server side views and really reduce>> > > > the>>> UI controllers we have less of a need for Spring MVC. I'd like to > > > propose>>> we consider developing the web services using standard JAX-RS > > > instead of>>> Spring MVC. Using JAX-RS we would have a choice of > > > implementations to use>>> including Apache CXF. Using Apache CXF would > > > still allow us to use Spring>>> for wiring beans together.>>> >>> > > > Thoughts?>> I'm +1 on this.>> >> The Spring MVC REST features are > > > particularly useful if and when combined>> with the whole of the Spring > > > MVC stack, but without (the need for) that I>> think they add little > > > extra functionality over 'plain' JAX-RS, while not>> been compatible with > > > it.>> CXF JAX-RS support and implementation is excellent and also used by > > > many>> other ASF projects so support is just around the corner if we > > > would need>> it, including further integration with things like security > > > services,>> Apache Camel, and what not.>> >>> >>> Chris>> > > > >
