Yes after thinking about it I also found that cxf would create an
endpoint or client for a original config. So I think you are right it
would be a bad idea.
Christian
Am 17.06.2011 09:17, schrieb Willem Jiang:
On 6/17/11 2:58 PM, Christian Schneider wrote:
If we just can treat the cxf endpoi
On 6/17/11 2:58 PM, Christian Schneider wrote:
Hi Willem,
thanks for you explanations.
I think the usage of the Spring*FactoryBeans is a good idea. It also
frees us from following every config change the cxf project does. Does
the style of calling a configure method on a factory come from CXF.
Hi Willem,
thanks for you explanations.
I think the usage of the Spring*FactoryBeans is a good idea. It also
frees us from following every config change the cxf project does. Does
the style of calling a configure method on a factory come from CXF. I
know that this is the default style in CXF.
The main reason that we use the SpringJAXRSClientFactoryBean and
SpringJAXBServerFactoryBean is I want the users of camel-cxfrs component
can still leverage their knowledge of CXF JAXRS front end.
And there are some difference between the client and server
configuration, we need to treat them
