THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
CXF
...
Bean
...
Component
The cxfbean: component allows other Camel endpoints to send exchange and invoke Web service bean objects. Currently, it only supports JAX-RS and JAX-WS (new to Camel 2.1) annotated service beans.
...
CxfBeanEndpoint is a ProcessorEndpoint so it has no consumers. It works similarly to a Bean component.
Maven users need to add the following dependency to their pom.xml to use the CXF Bean Component:
...
URI format
...
Where serviceBeanRef is a registry key to look up the service bean object. If serviceBeanRef references a List object, elements of the List are the service bean objects accepted by the endpoint.
Options
...
Name | Description | Example | Required? | Default Value |
|---|---|---|---|---|
| CXF bus reference specified by the | | No | Default bus created by CXF Bus Factory |
| CXF bean binding specified by the | | No | |
| Header filter strategy specified by the |
...
. |
|
...
No | | |
| Since 2.3, |
...
the |
...
wsdlLocation |
...
annotated |
...
in |
...
the |
...
POJO |
...
is |
...
ignored |
...
(by |
...
default) |
...
unless |
...
this |
...
option |
...
is |
...
set to |
...
Prior |
...
to |
...
2.3, |
...
the |
...
wsdlLocation |
...
annotated |
...
in |
...
the |
...
POJO |
...
is |
...
always |
...
honored |
...
and |
...
it |
...
is |
...
not |
...
possible |
...
to |
...
ignore. |
...
| No | | |
| Since 2.5, |
...
setting |
...
the |
...
providers |
...
for |
...
the |
...
CXFRS |
...
endpoint. |
...
|
...
No | | |||
| Will set the default bus when CXF endpoint create a bus by itself. | | No | |
Headers
...
Name | Description | Type | Required? | Default Value | In/Out | Examples |
|---|---|---|---|---|---|---|
|
...
|
...
) |
...
Character |
...
encoding |
...
| No | None | In | ISO-8859-1 |
...
|
...
2.0-m2: |
...
|
...
) |
...
Content |
...
type |
...
| No | */* |
...
In |
|
...
CamelHttpBaseUri |
...
and |
...
before: |
...
|
...
) |
...
The |
...
value |
...
of |
...
this |
...
header |
...
will |
...
be |
...
set |
...
in |
...
the |
...
CXF |
...
message |
...
as |
...
the |
...
|
...
property. |
...
It |
...
is |
...
needed |
...
by |
...
CXF |
...
JAX-RS |
...
processing. |
...
Basically, |
...
it |
...
is |
...
the |
...
scheme, |
...
host |
...
and |
...
port |
...
portion |
...
of |
...
the |
...
request |
...
URI. |
...
| Yes | The Endpoint URI of the source endpoint in the Camel exchange | In |
...
|
...
2.0-m2: |
...
|
...
h) |
...
Request |
...
URI's |
...
path |
...
| Yes | None | In | | |
|
...
|
...
) |
...
RESTful |
...
request |
...
verb |
...
| Yes | None | In | | ||
| HTTP response code | | No | None | Out | 200 |
...
Currently, the CXF Bean component has (only) been tested with the Jetty component. It understands headers from Jetty component without requiring conversion.
A Working Sample
This sample shows how to create a route that starts an embedded Jetty HTTP server. The route sends requests to a CXF Bean and invokes a JAX-RS annotated service.
First, create a route as follows: The from endpoint is a Jetty HTTP endpoint that is listening on port 9000. Notice that the matchOnUriPrefix option must be set to true because the RESTful request URI will not exactly match the endpoint's URI http://localhost:9000
...
.
...
...
The
...
to
...
endpoint
...
is
...
a
...
CXF
...
Bean
...
with
...
bean
...
name
...
customerServiceBean
...
.
...
The
...
name
...
will
...
be
...
looked
...
up
...
from
...
the
...
registry.
...
Next,
...
we
...
make
...
sure
...
our
...
service
...
bean
...
is
...
available
...
in
...
Spring
...
registry.
...
We
...
create
...
a
...
bean
...
definition
...
in
...
the
...
Spring
...
configuration.
...
In
...
this
...
example,
...
we
...
create
...
a
...
List
...
of
...
service
...
beans
...
(of
...
one
...
element).
...
We
...
could
...
have
...
created
...
just
...
a
...
single
...
bean
...
without
...
a
...
List.
...
...
That's
...
it.
...
Once
...
the
...
route
...
is
...
started,
...
the
...
web
...
service
...
is
...
ready
...
for
...
business.
...
A
...
HTTP
...
client
...
can
...
make
...
a
...
request
...
and
...
receive
...
response.
...