Hi, Are you getting the same exception or another one? I just discovered a few issues while trying to write a small test case to reproduce your problem. There was one issue in the outbound transform (which I wanted to use to generate that particular input xml message) and another in the inbound transform. But this inbound issue occurs only for a Provider based service (i.e., with the Source binding) and it does't apply to your case.
I tried to reproduce your problem using a normal service while activating ws-security with usernametoken action, but I could not reproduce it. If you could share a small example that can reproduce your problem, that would be helpful. Regards, aki p.s. the two issues that I mentioned, I will fix them today. 2012/12/7 purecharger <[email protected]>: > I tried with 2.6.3 and still have the same issue. Note that this problem > happens when I've got the StaxTransformFeature enabled and I have a > SAAJInInterceptor added in PRE_PROTOCOL phase. > > On Thu, Dec 6, 2012 at 2:25 PM, Aki Yoshida-3 [via CXF] < > [email protected]> wrote: > >> Could you try with 2.6.3? >> I just ran your test with 2.6.3 and didn't see any issue. >> >> feeding the input to the inTransformer >> <getAreas xmlns="http://api.company.com/";> >> <siteId xmlns="">1</siteId> >> </getAreas> >> >> and getting the result >> <getAreas xmlns="http://api.company.com/";> >> <test xmlns=""> >> <siteId>1</siteId> >> </test> >> </getAreas> >> >> regards, aki >> >> > > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Namespace-exception-when-Transform-feature-enabled-tp5719871p5719882.html > Sent from the cxf-user mailing list archive at Nabble.com.
