Hi, In inbound chain CXF has three sources/options to determine operation name: 1. WS-Addressing headers 2. SOAP Action (it works only with HTTP protocol) 3. Top payload element (regarding WS-I basic profile top element name of input message should be the equals to operation name).
In case if you use document literal binding and JAXB marshalling, DocLiteralInInterceptor builds OperationInfo.class structure based on payload (option 3). DocLiteralInInterceptor also unmarshalls XML payload and packs input parameters as MessageContentList into message content on UNMARSHAL phase. As far as message is already read from XML reader in DocLiteralInInterceptor, you cannot read it again in you interceptor placed after UNMARSHAL phase, but you have access to OperationInfo.class and unmarshalled payload in form of MessageContentList. There are some options to resolve it, but I would like to understand your use case a little bit more: is unmarshalled payload not usable for your interceptor? Do you need message in stream form? Cheers, Andrei. > -----Original Message----- > From: marcin.kasinski [mailto:[email protected]] > Sent: Samstag, 2. März 2013 21:11 > To: [email protected] > Subject: Re: Operation name null in inInterceptor > > After additional debugging.... > > Phase UNMARSHAL = here I can read operation name using > OperationInfo.class , but can not read input XML. > > Phase before UNMARSHAL (RECEIVE, READ,...)= here I CAN NOT read > operation name using OperationInfo.class , but can read input XML. > > Now my question is : > > Is there any chance to read OperationInfo and input XML in one phase in > input service interceptor ? > > > > > > ----- > > Regards > Marcin Kasinski > http://itzone.com.pl > -- > View this message in context: http://cxf.547215.n5.nabble.com/Operation- > name-null-in-inInterceptor-tp5723927p5723958.html > Sent from the cxf-dev mailing list archive at Nabble.com.
