...some quick feedback regarding the relative path issues: the
doc(...) function in the schema declaration can be skipped and
replaced by a simple path string. This could already resolve the path
discussed issues:
Old:
validate:xsd(a /, doc(../xsd/XDW.xsd)
New:
validate:xsd(a /,
Hi Wendell,
My apologies if this post is no help but only a me too. :-)
no need for excuses. You mentioned that you have similar problems, proposed a
hint on how that could be resolved and in general showed, that this is an issue
of importance for you.
We, the BaseX community, definitely
I feel the problem is the same.
The issue is just that the resolver for imports and includes (both XSD
and XSL) in BaseX seems not being able to resolve relative uris. We
fixed temporarely by creating a folder with all schemas and stylesheets
locally to the BazeX dist folder and transforming
Hi Marco, hi Seenivasan, hi Wendell,
thanks for your comments; I’ve added a GitHub entry for that issue [1].
The original BaseX code is found at [2]. It gives some insight into
how the XSLT processor is triggered via
TransformerFactory.newInstance() etc., so if you should manage to get
these few
Hi,
I've run into a similar problem to the one described (I think) below:
I can invoke XSLT in BaseX (fantastic) but I get compiler errors if
the stylesheet relies on xsl:import or xsl:include (not so good).
As I understand it, the JAXP interface (supported by Saxon and Xalan)
allows you to
5 matches
Mail list logo