From my experience of writing camel-cxf[1] component, I think you just
do the basic part of the integration which can marshal and unmarshal the
request and response. You just delegate the servlet transport to JAXB
data binding.
As you know CXF has lots of interceptors which provides a great
extensibility to let CXF support WS* specification. I suggest you start
from the CXF front-end API which provides more feasible entry of CXF.
BTW, camel is the camel-sprint-intergration component[2], you don't have
to do such kind of integration job yourself with help of camel.
[1]http://camel.apache.org/cxf.html
[2]http://camel.apache.org/springintegration.html
On 2/21/12 11:11 AM, cogitate wrote:
Thanks Sergei...
(re:
http://cxf.547215.n5.nabble.com/CXF-embedded-within-a-SpringIntegration-Context-td5158465.html#a5455592)
two questions:
1. If i did write an adapter for SI, what's the point where i can fake
CXFServlet inputstream, outputstream, so that i don't have to change any CXF
config files / CXF jaxws Service Implementations or CXF jaxrs service
implementations?
i understand, i might have to implement some servlet lifecycle methods
(doGet, doPost..?)
2. given a service-interface ( w/ it's jaxb requests and response) which
part of the CXF engine allows to load the jaxb classes?
this is the stack i have from my naive debugging attempts, but i am not sure
if i need all this :
JaxWsProxyFactoryBean<--- ClientProxyFactoryBean
( calls ClientProxy ..)
finally uses :
AbstractServiceFactoryBean --> AbstractWSDLBasedEndpoint ( -->
AnnotationsFactoryBeanListener )
( uses JAXBDataBinding )
--> uses JAXBContextInitializer
--> uses ServiceModelVisitor
--> uses CachedContextAndSchemas
--> ( parses JAXBContext )
--> uses JAXBContextCache
--> JAXBUtils
does this mean i need a MessagePartsInfo object as an abstraction? you see,
i can still use oxm.springframework. jaxb marshallers and unmarshallers, it
requires the use of XmlRootNode within jaxb classes. this doesn't seem to be
a pre-requisite for CXF. it loads all the classes needed to get the
interfaces, the request and response objects - somewhat miraculously :)
thanks and regards,
-cogitate
--
View this message in context:
http://cxf.547215.n5.nabble.com/re-CXF-with-Sprint-Integration-tp5501007p5501007.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
