> I'm validating a document against using a schema (stored in the database),
> itself using dtds (stored in the eXist folder directly, without additional
> configuration done).
> The "validate" command used on the resource using the eXist client
> succesfully validate the document, whereas the validateResource() used in my
> java application keeps returning me a validation error.
It probably makes a difference if you connect to a remote or local db.
I don't know the implementation very well (I didn't write it), but it
looks like the final validation step is always done on the client
side. So if your schema imports external resources, those might be
resolved relatively to the server, not the client.
However, this is just a guess. We plan to rewrite the service now that
jaxp and xerces offer better schema support. The current
implementation has not been maintained or improved for a while.
On 9/7/05, LE SAUX Louis-Marie RD-ILAB-LON
<[hidden email]> wrote:
> I currently experience troubles with the validateResource() function, used
> through the XML:BD:API (using eXist-snapshot-20050805).
> Any ideas or suggestion concerning this issue ?
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________
Exist-open mailing list
[hidden email] https://lists.sourceforge.net/lists/listinfo/exist-open