Re: [basex-talk] Issue with the Java 11 XML Catalog API and xsl:import/xsl:include

2023-03-09 Thread Christian Grün
Hi Gerrit,

Thanks for the report. I’m pretty sure we can (and should) return a
proper error message. It may be trickier to find out why the paths are
not resolved by the new Catalog API. I’ve opened an issue on that [1],
and I’m glad to hear that Norm’s XML resolver can cope with your
input.

All the best,
Christian

[1] https://github.com/BaseXdb/basex/issues/2186


On Wed, Mar 8, 2023 at 1:08 PM Imsieke, Gerrit, le-tex
 wrote:
>
> Hi,
>
> We experience an issue with the new catalog resolver when importing or
> including XSLT from another, possibly already catalog-resolved, XSLT file.
>
> If you unzip attached catalog_test.zip and set the catalog location by a
> pragma around xsl.xq or by
>
> set BASEX_JVM="-Dorg.basex.catalog=../catalog_test/xmlcatalog/catalog.xml"
>
> prior to invoking basexgui.bat or bin\basex.bat ..\catalog_test\xsl.xq,
> you will get an exception
>
> Improper use? Potential bug? Your feedback is welcome:
> Contact: basex-talk@mailman.uni-konstanz.de
> Version: BaseX 10.4
> Java: Eclipse Adoptium, 17.0.4.1
> OS: Windows 11, amd64
> Stack Trace:
> javax.xml.catalog.CatalogException: JAXP09040002: No match found for
> href 'other.xsl' and base
> 'file:/C:/Users/gerrit/Dev/catalog_test/xsl/imported.xsl'.
> …
>
> If I use Norm’s resolver by putting xmlresolver-5.1.1.jar and
> xmlresolver-5.1.1-data.jar into lib/custom, I get the expected result
>
> other.xsl was imported!
>
> Therefore the issue isn’t urgent. We just use Norm’s resolver.
>
> Should I file an issue on Github?
>
> Gerrit
>
> --
> Gerrit Imsieke
> Geschäftsführer / Managing Director
> le-tex publishing services GmbH
> Weissenfelser Str. 84, 04229 Leipzig, Germany
> Phone +49 341 355356 110, Fax +49 341 355356 510
> gerrit.imsi...@le-tex.de, http://www.le-tex.de
>
> Registergericht / Commercial Register: Amtsgericht Leipzig
> Registernummer / Registration Number: HRB 24930
>
> Geschäftsführer / Managing Directors:
> Gerrit Imsieke, Svea Jelonek, Thomas Schmidt


Re: [basex-talk] Progress bar (again)

2023-03-09 Thread Christian Grün
Hi Daniel,

> can anyone say what might be needed to implement this as a module?

Looks interesting! I hope our Wiki article on creating and installing
modules is helpful [1].

Cheers,
Christian

[1] https://docs.basex.org/wiki/Repository

>
> Daniel
>


[basex-talk] Progress bar (again)

2023-03-09 Thread Zimmel, Daniel
Hey,

I have a task that may take longer to execute (several minutes), so I felt I 
got to have a fancy progress bar on the command line to entertain me.

No progress bar though, found this in the archives: 
https://mailman.uni-konstanz.de/pipermail/basex-talk/2020-November/015845.html

So this is the closest I got (running BaseX from an Ant task):

xquery_update_db:
 [echo] XQuery Update (Database) wird ausgeführt: xquery/basex.reduce.xquery
[apply] EXPORTER: omit-xml-declaration=no
[apply] Database 'DEBUGX' was opened in 113.62 ms.
[apply] "FORTSCHRITT: 0%"
[apply] "FORTSCHRITT: *5%"
[apply] "FORTSCHRITT: **10%"
[apply] "FORTSCHRITT: ***15%"
[apply] "FORTSCHRITT: 20%"
[apply] "FORTSCHRITT: *25%"

While I am happy enough with this (it is quite accurate and I like the 
dramatically mounting effect), can anyone say what might be needed to implement 
this as a module?

Daniel