Hi Karel,
In BaseX, modules either need to be located in the module repository,
or the relative path needs to be specified in the import module
statement. Some more information on locating modules can be found in
our Wiki [1].
Hope this helps,
Christian
[1] http://docs.basex.org/wiki/Repository
Hi,
I am trying to run xquery file on basex, but it depends on xquery module
located in classpath. I have found parameter "org.basex.QUERYPATH", that
configures module lookup on filesystem. Is there way to lookup modules
in classpath?
Thanks,
Karel Hovorka, Semantico LTD
On Wed, 2015-04-08 at 10:37 +0200, Jérôme Chauveau wrote:
> Unfortunatly, the "id" notation fails...
>
>
Are you validating against a DTD? If not, the "ID-ness" property won't
be set...
It might work if the document uses xml:id without DTD validation.
Liam
Sure, I'm going to try this evening. If it's indeed Saxon we would
probably need one anyways.
--Marc
On Wed, Apr 8, 2015 at 2:23 PM, Christian Grün
wrote:
> Hi Marc,
>
> I would tend to say it's a Saxon issue. We have no Saxon-specific code
> in our XSLT functions, and the complete stack trace se
Hi Marc,
I would tend to say it's a Saxon issue. We have no Saxon-specific code
in our XSLT functions, and the complete stack trace seems to indicate
that something is going wrong in Saxon. – However, I can also have a
look at this if you send me an SSCCE for that bug.
Best,
Christian
On Wed,
Hi,
I have hit something which is related to Saxon XSLT. The XSLT in
question runs fine standalone (via Oxygen). But when hooked up via
RESTXQ I get the type of tracebacks (i've listed all traceback from
where it enters Saxon code below).
Although I don't have a full repro case I did manage to ma
Same problem with tomcat7 and BaseX8.1, but fixed with the latest snapshot.
Thanks.
Jérôme.
Le 08/04/2015 10:19, George Karakatsiotis a écrit :
I've just tried the latest snapshot and it was deployed successfully
Thanks!
Gk
On Tue, Apr 7, 2015 at 12:46 PM, Christian Grün
mailto:christian.gr.
Hi,
thank you for your answer. It was helpfull.
Java XInclude support seems to not fully handle XPointer attributes.
One solution consists in using the "element" scheme with the "descendant
path" notation:
Unfortunatly, the "id" notation fails...
Regards,
Jérôme.
Le 07/04/2015 12:38,
I've just tried the latest snapshot and it was deployed successfully
Thanks!
Gk
On Tue, Apr 7, 2015 at 12:46 PM, Christian Grün
wrote:
> And once more… Hi George, please try the latest snapshot and give us
> feedback if the problem has not been solved.
>
> Thanks,
> Christian
>
> [1] http://fi
9 matches
Mail list logo