Hi Vojtech, The options and parameters need to be added in the transformation scenario - as we added the port bindings. The port names returned by getInputPorts and getOutputPorts are used in the XProc scenario to offer available ports to the user. We can similarly add methods to allow the engine to specify if there are some option or parameter names that we should offer to the user but the XProc scenarios need to be updated to allow that information and to allow the user to edit that when he defines the scenario. We will look into adding support for options and parameters to the XProc scenarios. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com Toman_Vojtech@emc.com wrote:
The same probably goes for parameters. Similar to options, parameters are QName/value pairs, but they are passed to the pipeline by using special types of input ports (so called parameter input ports).
In order to pass a parameter to a pipeline, you must be able to specify:
1. name of the parameter input port (if not specified, the primary parameter input port is used) 2. parameter name 3. parameter value
The simplest solution to me seems to change the XProcTransformerInterface.transform() method so that it allows specifying options and parameter input ports mappings. (Maybe adding methods getOptions() and getparameterInputPorts() will be necessary, too).
Regards, Vojtech
-- Vojtech Toman Principal Software Engineer EMC Corporation toman_vojtech@emc.com http://developer.emc.com/xmltech _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user