Prepared TransformationFacade and FunctionTransform for parameter change

* FunctionTransform was adapted to support passing the transformation as either a string path or directly as a node-set / result-tree
** this in turn required changes to the TransformationFacade
** the implementation of a xalan::XSLTInputSource specialization for the XObjectValue::get template method was also required
* changed ixslt executable to match TransformationFacade constructor changes
* these changes were implemented in preparation for a restructuring of how the separate external functions provided by InputXSLT operate and work together
** the approach up until now was to provide non-combinable external functions for distinct task such as "read a file" and "transform that transformation using these parameters into that file"
** if you think about the areas of operations of these functions are overlapping quite a bit
*** e.g. FunctionTransform reads files, transforms DOM structures and writes files instead of only transforming things
** the new approach will be to limit the feature set of each function in the attempt of making the clearer and increasing their combinability
*** e.g. FunctionTransform won't read or write files but expect both the input-DOM and the transformation-DOM as node-sets or result trees and return the transformed document as a node-set to be written using FunctionWriteFile (to be implemented)

1 files changed, 1 insertions, 1 deletions

diff --git a/test/transform/transformation.xsl b/test/transform/transformation.xsl
index 0c6173d..fb7bf65 100644
--- a/test/transform/transformation.xsl
+++ b/test/transform/transformation.xsl
@@ -17,7 +17,7 @@
 
 	<xsl:variable name="command">
 		InputXSLT:transform(
-			$transformation,
+			string($transformation),
 			$target,
 			xalan:nodeset($parameters)
 		)