XConf | XConf 基于 go-micro 构建的分布式配置中心，提供配置的管理与发布、实时推送 | Configuration Management library

I now realized that the problem is not in Apache FOP but it's in my code. Our system is doing some additional schema validation (javax.xml.validation.Validator) against the plain fo schema and doesn't see the fox extension.

fox:alt-text is not a part of the original fo schema's fo:external-graphic definition and is causing validation failures.

The file can be now located at the server after maven build.

The vfs path is internal, virtual file system Jboss creates for itself, but only inside memory used by jboss. The new File() looks on the real harddrive location. There is no such path, because it is only virtual there. That's a common problem since Jboss version 5, so the solution pass through this question answered here: Not getting absolute file path from resources if you get java.lang.ClassCastException: java.io.FileInputStream cannot be cast to org.jboss.vfs.VirtualFile just try that without cast. hope it help somebody.

I would post a comment, but I don't have enough points. I am not sure if this is going to solve your whole issue with the RESTXQ because I have not used it in my application, but it seems that you have placed collection.xconf file in the wrong collection. It should be placed in the system collection: /db/system/config. That means that your configuration file should be in /db/system/config/db/apps/superapp collection. More info on triggers you have on the exist-db website on the documentation page: Configuring Database Triggers

Without looking at any documentation, we know this much: this is in the context of do-notation for whatever type is needed by withFocused. It apparently takes a function as argument, and that function must return a monadic value of some type. The value of this do-notation block must have that same type. It certainly does not have the type [(String, X ())]. (Well, okay, it could, since [a] is a monad, but it seems rather unlikely that this is the type that withFocused would expect as result).

You can find out what type it has by looking through the documentation:

Ok i figure it out. It was my fop.xconf file that was being ignored, i mean, i was with the default values when creating the pdf. So to fix it just edited the following files:

fop.xconf

I think you want to use group-adjacent and then you need to pass on the count of the group items and the current group index to fill the number-rows-spanned attribute and to block the output of the any second column-two cell in an adjacent group:

Based on the documentation for eXist's Conditional Combined Indexes feature you are trying to use here, it appears to me that this feature only support string comparisons (with an optional "numeric" mode). See https://exist-db.org/exist/apps/doc/newrangeindex#D3.21.18. In other words, your @type="xs:decimal" is not resulting in your attributes' values being cast to xs:decimal; effectively, instead, they are being indexed as xs:string.

Thus, for your query to work with the given data, change the predicate to [@value gt "5"].

Or, to force numeric comparisons, add numeric="yes" to the element in your index definitions, and then change your predicate to [@value gt "5.0"].

General Configuration Structure and Syntax Index configuration collection.xconf files are standard XML documents that have their elements and attributes defined by the eXist-db namespace http://exist-db.org/collection-config/1.0. The following example shows a configuration example:

We should clear up the errors first...

1. The class for the Whitespace Analyzer should be org.apache.lucene.analysis.core.WhitespaceAnalyzer.

Although it doesn't look like you reference the whitespace analyzer by its 'id' so, you could just remove it.

1. The config for your use of the StandardAnalyzer looks wrong to me. You have specified a stopwords parameter, but:
   1. its class is wrong, it should be org.apache.lucene.analysis.util. CharArraySet, and
   2. you have not given it any value(s).

If you just want the default stop words, you can omit the parameter entirely.

Once you have made those changes, you should try reindexing and monitor the logs again.

After that you should use the Monex app from the Dashboard in eXist 4.5.0 to examine the available indexes, to check that your data was indexed as you expected.

From the comment of @kevin-brown:

From what I see today, if I do this ($collection//foo | $collection//bar)[fn:contains(.,'string')] no index is used. But if I do this $collection//foo[fn:contains(.,'string')] | $collection//bar[fn:contains(.,'string')],the new-range index is used and optimization is full.

I can confirm that in certain formulation of the XQuery, eXist-db is not correctly optimising the query to make use of the range index. This is certainly a bug!

The Java Admin Client of eXist-db allows you to show a trace of the query:

1. ($collection//foo | $collection//bar)[fn:contains(., $string)] which Kevin reported did not use the index, produces the trace: