Hi On Fri, Jul 8, 2011 at 4:47 AM, cogitate <[email protected]> wrote: > ok - just to close the loop . > what was happening is specific to cxf-2.4.0 and it's a bug that's been fixed > in cxf-2.4.1-SNAPSHOT as given below. > http://cxf.547215.n5.nabble.com/quot-Stream-is-closed-quot-Exception-when-upgrade-from-CXF-2-3-3-to-CXF-2-4-0-td4385277.html > cxf stream is closed early > > very very difficult to debug/find. > Thanks for the confirmation
> btw Sergei : > do you know if using TransformFeature/InTransformElements i can turn off the > prefix "ps1:" ? so that it makes it xmlns="<namespace>" and applies that to > all elements? > Enforcing a default namespace at the writer level is tricky. We can have a complex document going out with many namespaces, possibly with the existing default namespace and say we just need to update a namespace on one of the nodes only. Do you need this for some specific reasons, ex, concerned about the propagation of prefixes in a large doc ? I guess one option is to add a defaultNamespace property which can be used to emit a chosen namespace as the default one Sergey > regards > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/cxf-2-4-0-pattern-match-StaxTransformFeature-tp4381005p4563318.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Sergey Beryozkin http://sberyozkin.blogspot.com Talend - http://www.talend.com
