Hi Andi

Thanks for continuing stressing InTransformReader :-).
It was mainly used for basic transformations, and having it dealing with more involved transformations will help to make it more robust. I'm on vacation starting from tomorrow, so I'm not sure if I get a chance to fix it today. I will back online in early August. Aki may get a chance to contribute his own patch and that can help with resolving this issue too if I won't get it resolved before then, we'll see :-)

Cheers, Sergey

Hi Sergey,

I've started the test of my sample project with 2.4.2-SNAPSHOT but now it
fails in the DocLiteralInInterceptor. I'll try to create a unit test for
this problem.


11:22:54.675 WARN  [org.apache.cxf.phase.PhaseInterceptorChain] Interceptor
for {http://cxf.apache.org/transform}TransformTestService has thrown
exception, unwinding now
java.lang.IllegalStateException: Current event not START_ELEMENT or
END_ELEMENT
        at
com.ctc.wstx.sr.BasicStreamReader.getNamespaceURI(BasicStreamReader.java:775)
        at
org.apache.cxf.staxutils.DepthXMLStreamReader.getNamespaceURI(DepthXMLStreamReader.java:130)
        at
org.apache.cxf.staxutils.transform.InTransformReader.readCurrentElement(InTransformReader.java:163)
        at
org.apache.cxf.staxutils.transform.InTransformReader.getNamespaceURI(InTransformReader.java:142)
        at
org.apache.cxf.staxutils.transform.InTransformReader.getName(InTransformReader.java:170)
        at
org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:90)
        at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
        at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:118)
        at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:318)


Cheers
Andi

--
View this message in context: 
http://cxf.547215.n5.nabble.com/Problem-with-new-transform-feature-tp4599185p4634209.html
Sent from the cxf-user mailing list archive at Nabble.com.

Reply via email to