If you just treat the communication with the WebSphere Message Broker as
a transport, you don't need to be messed with the CXF interceptor
chains. You can find more information about the transport here[1]
Can you also take a look at the Camel Transport[2] for CXF? it will save
you lots of time if you can find a camel component to deal with WMB.
[1]http://cxf.apache.org/docs/cxf-architecture.html#CXFArchitecture-Transports
[2]http://camel.apache.org/camel-transport-for-cxf.html
Willem
On 3/4/11 6:38 AM, eaudet wrote:
After a couple of hours of reading, I have came to a conclusion.
If I want to call my service implementation, I really need to start a server
instance. For example:
JaxWsServerFactoryBean sf = new JaxWsServerFactoryBean();
sf.setServiceClass(MyWsImpl.class);
sf.setAddress(wsURL);
sf.create();
Invoker wInvoker = sf.getInvoker();
And then call the server with my client code (using the code generated with
wsdl2java (-client option )).
I'm bit bumped because I wanted call my implementation without having to
create a server instance. Perhaps I should explain what I am trying to do.
WebSphere Message Broker 6.1 (yes I know it sucks) would call my CXF
generated classes from RMI (not SOAP-HTTP). This means I needed to create an
EJB that would call my interceptor chain and eventually reach me
implementation. I have two challenges:
1) Invoke my interceptor chain without starting a JaxWsServer instance;
2) Invoke my interceptor chain with a raw xml byte[];
Question: is there a way to call my web service method by passing xml in a
byte[] without starting a server?
Thanks for your help,
- Erick
--
View this message in context:
http://cxf.547215.n5.nabble.com/Calling-Interceptor-chain-directly-tp3403562p3408741.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
