aboutsummaryrefslogtreecommitdiff
path: root/src/support/type
diff options
context:
space:
mode:
authorAdrian Kummerlaender2014-06-16 23:01:23 +0200
committerAdrian Kummerlaender2014-06-16 23:01:23 +0200
commit741a70f5fecc38033832728f4ecc62a6abe328b2 (patch)
tree5cf421ece0eb745a618f654ecbdaeb21587c2875 /src/support/type
parent32c65970263c65022f5278b568c07b63c3d5d64b (diff)
downloadInputXSLT-741a70f5fecc38033832728f4ecc62a6abe328b2.tar
InputXSLT-741a70f5fecc38033832728f4ecc62a6abe328b2.tar.gz
InputXSLT-741a70f5fecc38033832728f4ecc62a6abe328b2.tar.bz2
InputXSLT-741a70f5fecc38033832728f4ecc62a6abe328b2.tar.lz
InputXSLT-741a70f5fecc38033832728f4ecc62a6abe328b2.tar.xz
InputXSLT-741a70f5fecc38033832728f4ecc62a6abe328b2.tar.zst
InputXSLT-741a70f5fecc38033832728f4ecc62a6abe328b2.zip
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)
Diffstat (limited to 'src/support/type')
-rw-r--r--src/support/type/xobject_value.cc19
1 files changed, 19 insertions, 0 deletions
diff --git a/src/support/type/xobject_value.cc b/src/support/type/xobject_value.cc
index cdeb9c6..812be52 100644
--- a/src/support/type/xobject_value.cc
+++ b/src/support/type/xobject_value.cc
@@ -1,5 +1,8 @@
#include "xobject_value.h"
+#include <xalanc/XSLT/XSLTInputSource.hpp>
+#include <xalanc/XalanDOM/XalanDocumentFragment.hpp>
+
#include <boost/algorithm/string.hpp>
#include <string>
@@ -20,6 +23,22 @@ xalan::XObjectPtr get<xalan::XObjectPtr>(const xalan::XObjectPtr& ptr) {
return ptr;
}
+template <>
+xalan::XSLTInputSource get<xalan::XSLTInputSource>(
+ const xalan::XObjectPtr& ptr) {
+ switch ( ptr->getType() ) {
+ case xalan::XObject::eObjectType::eTypeNodeSet: {
+ return xalan::XSLTInputSource(ptr->nodeset().item(0));
+ }
+ case xalan::XObject::eObjectType::eTypeResultTreeFrag: {
+ return xalan::XSLTInputSource(ptr->rtree().getFirstChild());
+ }
+ default: {
+ return xalan::XSLTInputSource(ptr->str());
+ }
+ }
+}
+
}
}