Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multiple parameter ports does not work #120

Closed
josteinaj opened this issue Sep 2, 2013 · 1 comment
Closed

multiple parameter ports does not work #120

josteinaj opened this issue Sep 2, 2013 · 1 comment

Comments

@josteinaj
Copy link
Contributor

@josteinaj josteinaj commented Sep 2, 2013

<?xml version="1.0" encoding="UTF-8"?>
<p:declare-step xmlns:p="http://www.w3.org/ns/xproc" xmlns:c="http://www.w3.org/ns/xproc-step" version="1.0" xmlns:ex="http://example.net/">

    <p:output port="result"/>

    <p:declare-step name="step" type="ex:step">
        <p:input kind="parameter" port="p1" primary="true"/>
        <p:input kind="parameter" port="p2">
            <p:empty/>
        </p:input>
        <p:output port="result">
            <p:pipe port="result" step="parameters"/>
        </p:output>
        <p:parameters name="parameters">
            <p:input port="parameters">
                <p:pipe port="p1" step="step"/>
            </p:input>
        </p:parameters>
    </p:declare-step>

    <ex:step>
        <p:with-param name="param1" select="'param1'"/>
    </ex:step>

</p:declare-step>

The pipeline above gives the following console output in xmlcalabash-1.0.13-94:

jostein@jostein:/tmp$ calabash calabash-parameter-ports-1.xpl 
sep 02, 2013 1:56:45 PM com.xmlcalabash.util.DefaultXProcMessageListener error
SEVERE: calabash-parameter-ports-1.xpl:6:48:Attempt to set parameter w/o specifying a port (and there's more than one)
sep 02, 2013 1:56:45 PM com.xmlcalabash.drivers.Main error
SEVERE: com.xmlcalabash.core.XProcException: Attempt to set parameter w/o specifying a port (and there's more than one)

The step ex:step in the step has a primary parameter port, so the parameter should be automatically connected to that port.

In addition, it doesn't help to specify the port either. The same error is thrown.

ndw added a commit that referenced this issue Sep 22, 2013
ndw added a commit that referenced this issue Sep 22, 2013
@ndw
Copy link
Owner

@ndw ndw commented Sep 22, 2013

Fixed for the next release.

@ndw ndw closed this Sep 22, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.