[ 
https://issues.apache.org/jira/browse/XMLSCHEMA-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005779#comment-16005779
 ] 

Aron Olsen edited comment on XMLSCHEMA-49 at 5/11/17 1:51 AM:
--------------------------------------------------------------

A prime goal of my URI-resolver it of course, to it as independent of schemas 
in the "sky" as possible. May be, servers are down, and may be hinted 
schema-locations are simple wrong ;)


was (Author: aronxsd):
A prime goal of my URI-resolver it of course, to make as much independent of 
the "sky" as possible. May be, that servers are down, and may be that suggested 
schema-locations are simple wrong ;)

> URI resolver: How often is it invoked?
> --------------------------------------
>
>                 Key: XMLSCHEMA-49
>                 URL: https://issues.apache.org/jira/browse/XMLSCHEMA-49
>             Project: XmlSchema
>          Issue Type: Question
>    Affects Versions: 2.2.1
>            Reporter: Aron Olsen
>            Priority: Trivial
>             Fix For: 2.1.1
>
>
> Hi again,
> I have made an extension of your default URI-resolver in order to device a 
> scheme for making a caching one - maybe utiliizing a pre-loaded file-cache 
> which has to be mapped to URI's of incoming requests..
> I would like to make an URI resolver as independant of referenced 
> included/imported XSDs as possible (the ones in the sky). When dealing with 
> GML3, this can have tremendous performance benefits, as it consists of a very 
> large set of schema-files.
> I have watched how often URI-resolver is being invoked and it looks as it is 
> being invoked several times for the same XSD-reference. Is URI-resolver 
> invoked multiple times at the instant of a single schema reference or is it 
> only invoked once for each schema-reference detected by XmlSchema during 
> XmlSchema's unmarshalling/parsing of a single XSD?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to