https://issues.apache.org/jira/browse/CXF-1418
Thanks for the insight. As an end-user configuring CXF's behavior through XML, it's kind of weird to have CXF's behavior not match the XML I'm giving it, so I don't agree with keeping the current behavior as the default. However, I understand that it makes things simpler for the built-in components, so I guess it's a compromise. dkulp wrote: > > What might be a workable solution would be to add a method like: > > boolean allowDuplicates(); > > to PhaseInterceptor (default it to false in AbstractPhaseInterceptor for > compatibility) where an interceptor could say "I'm allowed to be in here > more than once". > > Feel free to log a JIRA for this. (and attach a patch :-) ) > > On Tuesday 05 February 2008, Aaron Pieper wrote: >> We have a homebrew CXF interceptor which extends >> AbstractSoapInterceptor. It's a generic XSLT interceptor which runs >> the input through a specified XSLT. We use two of them in our >> interceptor chain, configuring them with different XSLTs. However, CXF >> ignores the second interceptor. It seems like since >> AbstractPhaseInterceptor uses the class name for its ID, the second >> interceptor is assumed to be a duplicate of the first. > -- View this message in context: http://www.nabble.com/Problem-having-multiple-interceptors-of-the-same-type-on-the-interceptor-chain--tp15300074p15306508.html Sent from the cxf-user mailing list archive at Nabble.com.
