You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by "renutcs@gmail.com" <re...@gmail.com> on 2014/03/05 17:45:21 UTC

RE: Information on using Interceptors in Service Side

Hi Andrei,

Thanks for the support. We tried the approach and have few doubts

1) ServiceImpl class which has the invoke method doesn't have access to the
message object. In our case , we want to access some custom objects which
are already initialized by our engine in class where we are registering the
transport layer. How can we get hold of the objects in ServiceImpl class(in
our case mysourcepayloader class)? 

2) If we plan to have a custom interceptor to access the custom objects
which are required for our processing, how can we build the outmessage. From
the code it seems like out message is set after ServiceInvokerInterceptor is
called and invoke of ServiceImpl is invoked. Is there a way to return null
from ServiceImpl or rebuild out message in custom interceptor.

3) What if we just have a conduit , create a JAXWSFactorybean object and
have a custominterceptors to preprare the processed response. Why do we
require a transport?

4) I tried to create server using JaxWsFactoryBean object. Whenever I passes
soap 1.2 message I get an error. How to set it to use SOAP 1.2 binding?

Thanks 



--
View this message in context: http://cxf.547215.n5.nabble.com/Information-on-using-Interceptors-in-Service-Side-tp5740165p5740871.html
Sent from the cxf-user mailing list archive at Nabble.com.