Hi Andi Sorry, I actually missed your previous email, so thanks for trying to figure out where the problem is. Have a look please, if you get a chance at org.apache.cxf.staxutils.transform.InTransformReader and the way StaxUtils.read(filteredReader)) interacts with it. What may be happening is that StaxUtils calls some XMLStreamReader method which InTransformReader does not override or perhaps there's some problem with the way InTransformReader manages NamespaceContext -
Please create a JIRA if you won;t have time or get stuck thanks, Sergey On Wed, Jul 20, 2011 at 9:53 PM, akuhtz <[email protected]> wrote: > Hi Sergey, > > I've done some more debugging on this problem and found that the loop > appears in the processing of ReadHeadersInterceptor.handleMessage() when CXF > try to get the header element from the message (line 159: doc = > StaxUtils.read(filteredReader)). In StaxUtils around line 966 a new element > is created and in the next line the prefix of the reader is set on the > element but this is the wrong namespace (the original and not the > converted). I'm not sure 100% if this is the reason that the while-loop > around is not left .... > > Currently I'm stuck and I don't know where to start looking for a fix for > this situation ... > > Attached is the updated sample project. Shall I create a JIRA issue? > > http://cxf.547215.n5.nabble.com/file/n4617249/cxf-transform-sample.zip > cxf-transform-sample.zip > > Cheers > Andi > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Problem-with-new-transform-feature-tp4599185p4617249.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Sergey Beryozkin http://sberyozkin.blogspot.com Talend - http://www.talend.com
