Hi
alex,
What if I want to
test for example the XSLFOConverter processer which directly serialize its
content. The inputs of the processor are no problem at all to test. But problem
occurs in the output. example of an output is :
<document xsi:type="xs:base64Binary" content-type="image/jpeg">/9j/4AAQSkZJRgABAQEBygHKAAD/2wBDAAQDAwQDAwQEBAQFBQQFBwsHBwYGBw4KCggLEA4R
...
KKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooA//2Q==
</document>
I don't want to put
this kind of code into my test case like:
<output name=\"data\">
<document xsi:type="xs:base64Binary" content-type="image/jpeg">/9j/4AAQSkZJRgABAQEBygHKAAD/2wBDAAQDAwQDAwQEBAQFBQQFBwsHBwYGBw4KCggLEA4R ... KKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooA//2Q==</document>
</output>
I only want to
compare the document element and it's attributes. The content i am not
interested in. Do you have something like a wildcard option so that the content
below the document element could be anything? for example:
<output name=\"data\">
<document xsi:type="xs:base64Binary" content-type="image/jpeg">*</document>
</output>
With kind
regards,
Cheers,
Mark
--
You receive this message as a subscriber of the
[hidden email] mailing list.
To unsubscribe: mailto:
[hidden email]
For general help: mailto:
[hidden email]?subject=help
OW2 mailing lists service home page:
http://www.ow2.org/wws