THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
The cxfrs: component provides integration with Apache CXF for connecting to JAX-RS 1.1 and 2.0 services hosted in CXF.
Maven users will need to add the following dependency to their pom.xml for this component:
...
Name | Description | Example | Required? | default value |
|---|---|---|---|---|
| The resource classes which you want to export as REST service. Multiple classes can be separated by comma. |
| No | None |
| Deprecated: Use |
| No | None |
| new to Camel 2.1 If it is true, the CxfRsProducer will use the HttpClientAPI to invoke the service | httpClientAPI=true | No | true |
| New in 2.5, this option will let CxfRsConsumer decide to use sync or async API to do the underlying work. The default value is false which means it will try to use async API by default. | synchronous=true | No | false |
| New in 2.6, this option tells the CxfRsProducer to inspect return codes and will generate an Exception if the return code is larger than 207. | throwExceptionOnFailure=true | No | true |
| New in 2.6, you can set a IN message header CamelDestinationOverrideUrl to dynamically override the target destination Web Service or REST Service defined in your routes. The implementation caches CXF clients or ClientFactoryBean in CxfProvider and CxfRsProvider. This option allows you to configure the maximum size of the cache. | maxClientCacheSize=5 | No | 10 |
| New in 2.9.0. Will set the default bus when CXF endpoint create a bus by itself |
| No | false |
| New in 2.9.0. A default bus created by CXF Bus Factory. Use |
| No | None |
| As of 2.11. Sets how requests and responses will be mapped to/from Camel. Two values are possible:
|
| No | Default |
| Allows you to specify a custom CxfRsBinding implementation to perform low-level processing of the raw CXF request and response objects. The implementation must be bound in the Camel registry, and you must use the hash (#) notation to refer to it. | binding=#myBinding | No | DefaultCxfRsBinding |
| Since Camel 2.12.2 set custom JAX-RS providers list to the CxfRs endpoint. |
| No | None |
| Since Camel 2.12.2 Sets the locations of the schemas which can be used to validate the incoming XML or JAXB-driven JSON. |
| No | None |
| Since Camel 2.12.3 Set the feature list to the CxfRs endpoint. |
| No | None |
| Since Camel 2.12.4 Set the properties to the CxfRs endpoint. |
| No | None |
| Since Camel 2.12.4 Set the inInterceptors to the CxfRs endpoint. |
| No | None |
| Since Camel 2.12.4 Set the outInterceptor to the CxfRs endpoint. |
| No | None |
| Since Camel 2.12.4 Set the inFaultInterceptors to the CxfRs endpoint. |
| No | None |
| Since Camel 2.12.4 Set the outFaultInterceptors to the CxfRs endpoint. |
| No | None |
| Since Camel 2.14.0 This option is used to set the CXF continuation timeout which could be used in CxfConsumer by default when the CXF server is using Jetty or Servlet transport. (Before Camel 2.14.0, CxfConsumer just set the continuation timeout to be 0, which means the continuation suspend operation never timeout.) |
| No | 30000 |
ignoreDeleteMethodMessageBody | Since Camel 2.14.1 This option is used to tell CxfRsProducer to ignore the message body of the DELETE method when using HTTP API. | ignoreDeleteMethodMessageBody=true | No | false |
| Since Camel 2.14.2 This option is used to specify the model file which is useful for the resource class without annotation. Since Camel 2.15 This option can point to a model file without specifying a service class for emulating document-only endpoints |
| No | None |
| Since Camel 2.15 When the option is true, camel will perform the invocation of the resource class instance and put the response object into the exchange for further processing. |
| No | false |
| propagateContexts | Since Camel 2.15 When the option is true, JAXRS UriInfo, HttpHeaders, Request and SecurityContext contexts will be available to custom CXFRS processors as typed Camel exchange properties. These contexts can be used to analyze the current requests using JAX-RS API. |
You can also configure the CXF REST endpoint through the spring configuration. Since there are lots of difference between the CXF REST client and CXF REST Server, we provide different configuration for them.
Please check out the schema file and CXF JAX-RS documentation for You can also configure the CXF REST endpoint through the spring configuration. Since there are lots of difference between the CXF REST client and CXF REST Server, we provide different configuration for them.
Please check out the schema file and CXF JAX-RS documentation for more information.
How to configure the REST endpoint in Camel
...
| Info | ||
|---|---|---|
| ||
Resource By default, JAX-RS resource classes are only used to configure JAX-RS properties. Methods will not be executed during routing of messages to the endpoint. Instead, it is the responsibility of the route to do all processing. Note that starting from Camel 2.15 it is also sufficient to provide an interface only as opposed to a no-op service implementation class for the default mode. Starting from Camel 2.15, if a performInvocation option is enabled, the service implementation will be invoked first, the response will be set on the Camel exchange and the route execution will continue as usual. This can be useful for integrating the existing JAX-RS implementations into Camel routes and for post-processing JAX-RS Responses in custom processors.
|
| Wiki Markup |
|---|
{snippet:id=example|lang=java|url=camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/jaxrs/testbean/CustomerServiceResource.java} |
...