Subject: RE: [xsl] Using a custom URIResolver From: "M. David Peterson" <m.david@xxxxxxxxxx> Date: Mon, 5 Apr 2004 07:13:52 -0600 |
My assumption is that you are using .NET and this is custom URIResolver that you are referring to? Either way, it doesnt matter because the easiest way to solve your problem is to wrap the document() function within a boolean() function which will evaluate to true if the file exists and false if it does not. You can also wrap string() and concat() within the document() function to use a dynamically created reference to a file... for example boolean(document(string(concat('/foo/bar/', $foobar, '.xml')))) when used within a test attribute would evaluate to true if the string created by the concat() function existed in that location. Best of luck! <M:D/> -----Original Message----- From: Bjvrn Boxstart [mailto:Boxstart@xxxxxxxx] Sent: Monday, April 05, 2004 6:40 AM To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx Subject: [xsl] Using a custom URIResolver Hello all, I'm using a custom URIResolver in a transformation. This is because I'm using the document function to find related documents for the document that is currently being transformed. What I want is that only when the referenced file is not being found by the default URIResover, that my custom URI Resolver takes over and finds a template to be used for that single transformation. The problem that I have is that I first want the default URI Resolver to act and only when it's result is null or an exception, that my custom URI resolver takes over. Until now I can only find how to use the default URI resolver (in case my own URI resolver cannot resolve the reference) by using null as the return value of the resolve() method. Is there anybody who knows how to solve this problem or else what the code is for the default implementation of the default URI resolver so that I can modify it to let it act as I want it to? Thanks in advance! Best regards, Bjvrn Boxstart
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] Using a custom URIResolver, Björn Boxstart | Thread | RE: [xsl] Using a custom URIResolve, Michael Kay |
Re: [xsl] creating multiple namespa, Jeni Tennison | Date | [xsl] Unsubscribing you from XSL-Li, B Tommie Usdin |
Month |