Subject: Re: [xsl] Getting non-existing, but supplied, parameters From: Abel Braaksma <abel.online@xxxxxxxxx> Date: Wed, 13 Sep 2006 00:48:42 +0200 |
Cheers, Abel
I will look into this.You might like to look at Andrew Welch's Kernow utility to see how it tackles this. (I can't remember how it does, but I remember the discussion about how it should).
https://sourceforge.net/projects/kernowforsaxon
There are two possible ways to do it: one is to analyze the sourceThese appear to me as ways to get the defined parameters for a given stylesheet. I conclude from this that a similar mechanism from within the stylesheet itself is non-existent?
stylesheet, the other is to call
((Controller)transformer).getBindery().getGlobalParameterMap()
I think it's better to prompt the user for parameters that are actuallyI totally agree, and we actually do so (three months back you helped me out on getting global params). But we have three situations when things can still go wrong:
defined in the stylesheet, rather than trapping the fact that they supplied
unwanted parameters after the event.
At present I don't think Saxon offers any interface that allows you accessI see. If anybody would know, it'd be you ;)
to all the parameters that were supplied, as distinct from those that were
declared.
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] Getting non-existing, but, Michael Kay | Thread | [xsl] replace() and efficiency: tro, David J Birnbaum |
RE: [xsl] Getting non-existing, but, Michael Kay | Date | [xsl] replace() and efficiency: tro, David J Birnbaum |
Month |