The XSLT Actor accepts XML on it's input port, but does not use a XMLToken.
Several sample work-flows seem to pass it a StringToken,
which does not seem intuitive when I connect my actor that outputs an
XMLToken.

Additionally, I don't see an actor that would bridge this gap of turning
a XMLToken into a StringToken for actors that accept XML, but as a
StringToken.

Am I missing something? Is this a bug?

Chris

Reply via email to