73492 - XSLTProcessor needs a way to have parameters initialized

Status: VERIFIED FIXED

(Core :: XSLT, enhancement, P5)

Description

[Sean Chitwood]

The XSLT processor lacks the capability to have parameters initialized brfore
processing. This capability is needed before work on bugs 70366 and 70369 can
continue.

Several solutions have been suggested on IRC:

1) an initialize method that takes either a NamedMap of the values or a
processorState

2) Creating more process methods that take either a NamedMap of values or a
processorState.

3) method that allows the getting and setting of parameters (Again via either a
NamedMap or ProcessorState) ie getParameters()/setParameters()

Comment 1

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

I'd suggest having an "addParameters(NamedMap* vars)" method.

Comment 2

[Keith Visco]

Should parameters be restricted to strings, or any "XPath Result" 
(see interface ExprResult), which also includes booleans, numbers and node-sets.

Comment 3

[Sean Chitwood]

I feel that the parameters should not be limited to strings, but include numbers
and boolean as well.

I can't see a good way of specifying nodesets through any of the methods for
initialization that have been suggested (ie commandline, javascript or
stylesheet pi)

However , initially, for ease of implementation it might be best to limit it to
strings.

Comment 4

[Axel Hecht]

blame sicking, all on his knees

Comment 5

[Arthur Smyles]

It would also be useful to be able to set a parameter using a processing
instruction. This way it would be possible to set the parameters without using
javascript on the browser.it could be something like

<?TransforMiiX param1="value" param2="value2" ?> 

Comment 6

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

fixed with the branch-landing

Comment 7

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

.

Comment 8

[Axel Hecht]

mass verifying