On 29.11.17 14:37, Sergey Beryozkin wrote:
> Right, the transform feature is not meant to replace XSLT, it would be
> much faster for straightforward transforms at the element
> structure/namespace level but it's not a good fit for the complex
> transformations...
Indeed, we'd need something like
Right, the transform feature is not meant to replace XSLT, it would be
much faster for straightforward transforms at the element
structure/namespace level but it's not a good fit for the complex
transformations...
Note if all of these arbitrary simple elements are united by a namespace
which
I think either of us doesn't understand ;-)
Since the service provider essentially replaced the SOAP string type
with its own 'StringType' simple type that "VEMPTY" text content can
appear in any element. Hence, I need to globally replace that text in
every SOAP message - regardless of which XML
Or may be
"{http://bar}a;, "{http://bar}a= " or similar, please experiment.
XSLTFeature should def work though...
On 29/11/17 13:22, Sergey Beryozkin wrote:
You should be able to replace it:
You should be able to replace it:
https://github.com/apache/cxf/blob/master/core/src/test/java/org/apache/cxf/staxutils/transform/InTransformReaderTest.java#L56
and
https://github.com/apache/cxf/blob/master/core/src/test/java/org/apache/cxf/staxutils/transform/InTransformReaderTest.java#L73
We're consuming SOAP messages for which the string type was extended or
redefined (see at the bottom). To denote null/empty values the XML
element uses "VEMPTY" as text content.
Example: VEMPTY
Before the message is deserialized and mapped to the Java model we'd
like to transform "VEMPTY" to "".
