Hi Benson
I'd consider using InputStream (or JAXP Source if applicable) as a
method parameter or use attachments given that CXF saves some of the
data to the temp files...
Sergey
On 28/03/16 19:07, Benson Margulies wrote:
If I want to handle posts with more payload than I want to have in
Hi
org.apache.cxf.servlet.service-list-path is a property that you can set
in Karaf, to something like "/services-list", etc
Thanks, Sergey
On 28/03/16 14:13, josephkampf wrote:
I have a service that has some extended path information that include the
work service
Example:
If I want to handle posts with more payload than I want to have in memory
all at once (with REST), what's recommended?
I have a service that has some extended path information that include the
work service
Example:
http://localhost:8181/cxf/abcd/services
The Rest service is abcd and extended path info is /services.
I see that this is being done in the web.xml that CXF is using for the
CXFServlet. How can I
Like said ... if your cxf endpoint address starts like /path then you use
servlet transport. If you use a fully qualified address then the jetty
transport is used.
Christian
2016-03-28 15:13 GMT+02:00 Setya :
> Hi Christian,
>
> Thank you for your explanation.
>
> How does
Hi Christian,
Thank you for your explanation.
How does using / make me using servlet transport instead if
Jetty's.
I mean how do I know which 1 I'm currently using ?
Thanks & Regards,
Setya
--
View this message in context:
The jetty transport will create a new jetty instance internally and listen
on the specified port. It directly depends on jetty.
The servlet transport uses the OSGi HttpService. It only depends on the
HttpService API. So to make it work you need to install a HttpService
implementation. By default