From 35334241ce4b76b1b1a66219ce938f27fdf39031 Mon Sep 17 00:00:00 2001
From: Adrian Kummerländer
Date: Tue, 20 May 2014 21:17:10 +0200
Subject: Replaced FunctionResolveInclude with IncludeEntityResolver * xalan /
 xerces offers the possibility of implementing custom entity resolvers which
 are called upon by "<xsl:include..." ** such a custom resolver was
 implemented to resolve include path entities * this is a much better way to
 support include paths than offering a custom external "resolve-include"
 function * as entity paths are expanded before they are passed to the entity
 resolver, a special "[path]" syntax simmilar to "#include <path>" had to be
 implemented

---
 src/transformation_facade.cc | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

(limited to 'src/transformation_facade.cc')

diff --git a/src/transformation_facade.cc b/src/transformation_facade.cc
index 07483c1..3bf1532 100644
--- a/src/transformation_facade.cc
+++ b/src/transformation_facade.cc
@@ -10,9 +10,14 @@
 
 namespace InputXSLT {
 
-TransformationFacade::TransformationFacade(const std::string& transformation):
+TransformationFacade::TransformationFacade(
+	const std::string& transformation,
+	IncludeEntityResolver* resolver
+):
 	transformation_{},
 	transformer_() {
+	this->transformer_.setEntityResolver(resolver);
+
 	this->transformer_.compileStylesheet(
 		xalan::XSLTInputSource(transformation.data()),
 		this->transformation_
-- 
cgit v1.2.3