I am creating web services using jaxrs specification, which uses
Camel-CXF-Spring-jaxrs (Servicemix) 

1: I have created web services in CXF on jaxrs specification and deployed in
osgi container (camel) and it is working fine. I am able to call the web
service from client. 

Request Statement:
I shall send the HTTP request from browser -> receive request from client -
> filter the headers (Filters) -> send for processing (web service method)
-> filter the response header (Filter) -> send response to client 


Problem:
2: I want to use the spring's DelegatingFilterProxy (I dont have servlet
context in osgi container) to filter the header processing. I have my own
filters in place but I can not able to deligate the web service call to
filter proxy. so that I can intercept the request and filter them and then
send it to processing (jaxrs:serviceprovider) 


        <bean id="delegateFilterProxy"
class="org.springframework.security.web.FilterChainProxy">
                <constructor-arg>
                        <list>
                                <security:filter-chain pattern="/**" 
                                       
filters="GenericHeaderFilter,requestIdentityFilter" />
                        </list>
                </constructor-arg>
        </bean>



3: or I have to use jaxrs:inINterceptor to have that functionality to filter
the header information. 
        <jaxrs:server id="WsTradeService" address="/WsDaltrade">
<jaxrs:inInterceptor>
                        <ref bean="ininterceptorbean" />
                </jaxrs:inInterceptor>
                
<jaxrs:serviceBeans>
                        <ref bean="WsTradeSrv" />
                </jaxrs:serviceBeans>
        </jaxrs:server>
<jaxrs:outInterceptor>
                        <ref bean="outinterceptorbean" />
                </jaxrs:inInterceptor>





--
View this message in context: 
http://servicemix.396122.n5.nabble.com/Web-service-in-CXF-need-to-use-spring-filter-for-header-processing-tp5718387.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to