Hi Sergey, thanks for your answer
having a shared method signature would be a nice feature to have but not mandatory.... We made a facade for REST and SOAP so the method signature can be adapted to the most suitable. For the time being, I work mostly on the REST Facade.... I would like to know if i should create method like this : upload(String id, byte[] content, List<String> metadata) or upload(Report report) and if so how can I handle method like this : uploadAndProcess(Report report, List<DataContext> data, Options options); So far I have no solution for the last case. I don't really want to create a custom request object for each method I create. Cheers, Pascal. 2011/6/7 Sergey Beryozkin <[email protected]> > Hi > > > > Would you like to have a shared signature for SOAP and REST services ? > You may want to have a method dedicated to serving SOAP requests only > and which would return say DataSource. That method may work for JAX-RS > too. > > And you may also try introducing a method which returns a JAXB bean > capturing the data - this will work for SOAP but also use CXF JAX-RS > RequestDispatcherProvider to redirect to HTML-aware handlers or use > XSLTJaxbProvider > > > http://cxf.apache.org/docs/jax-rs-redirection.html#JAX-RSRedirection-WithRequestDispatcherProvider > > http://cxf.apache.org/docs/jax-rs-advanced-xml.html#JAX-RSAdvancedXML-XSLTsupport > > RequestDispatcherProvider and XSLTJaxbProvider are not 'intrusive' and > can help with separating the presentation logic from the main > controller code. > > Some users are combining Struts with CXF as well - but I've no experience > there > > Cheers, Sergey > > > > > > > -- > > Pascal Leclercq > > > > > > -- > Sergey Beryozkin > > Application Integration Division of Talend > http://sberyozkin.blogspot.com > -- Pascal Leclercq
