OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-iic message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [ebxml-iic] Proposed extension to include document processing in IIC framework


The proposal is to extend the <FileURI> semantics in <PutMessage><SetPayload>. If the file's extension is a stylesheet, then the test driver will obtain the stylesheet from the URI and transform a message in the MessageStore and then set the payload of the current PutMessage to the resulting xml.

<PutMessage>
    <SetPayload>
        <FileURI>Purchase2Confirmation.xsl</FileURI>
    </SetPayload>
</PutMessage>


Doing this would allow the test driver to create a response message that contains run time data, not static default data from base files. This would also eliminate the extensive use of <SetParameter> that would be needed to simulate the same behavior. Using static base xml files is still an option since the proposed change is an extension.
 
Using stylesheets would also allow the test driver to create mutated and malformed response messages based on the incoming message. However, a <ModifyPayload> instruction with XUpdate support can also be added to the framework to accomplish the task of modifying a payload after it is has been imported.

<PutMessage>
    <SetPayload>
        <FileURI>ConfirmationBase.xml</FileURI>
    </SetPayload>
    <ModifyPayload>
        <XUpdate>xupdatemutationfile.xml</XUpdate>
        <UseParameter>
            <Name>MyParam</Name>
            <Value>Xpath to change or static value</Value>
        </UseParameter>
    </ModiyPayload>
</PutMessage>


The XUpdate or UseParameter operation would be performed after the SetPayload instruction.




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]