Hi Jeff

The parameter type is the message type, in the fully qualified name format, e.g. {http://my.namespace.com}Order.

The parameter value is a relative path to the message value. In the older scenarios it had the option to specify messages either by value or as a file - but to simplify the model and make all exchanges consistent, it seemed better to externally reference the messages, allowing them to be independently validated/reused.

I probably need to change the labels to make it clearer.

Regards

Gary

No, I think the path is relative to the scenario file. So if the message (xml) file is in the same folder, then just use the file name. If in a sub-folder (e.g. messages) then it would be messages/PolicyRequest.xml.

Regards

Gary

I think it may be best if you can attach your Eclipse project so that I can see what has been specified. Its possible its an update issue - but the local part of the parameter Type field should be displayed in the brackets.

The Value field for the parameter, which references the xml file, is the sample message that is used for simulation.

Regards

Gary

Good idea - sounds like a feature request

Jeff DeLong wrote:

 

This would be easier if the tool would let you browse to the file and then set the Type and Value from there.

Agree - this would be good.

I have an xsd file with several types. I would like to be able to browse to this. Then select which type I want to use, and the value.

How would I do that now, being that all types are in one xsd file?

Hi Anton

Although this would technically be possible, I am not sure it would be very useful, as this would be an indirect way to identify the type, create a template message and then set the fields.

Possibly it would be better to use xml tools (not sure what is available) that may be able to bootstrap a XML document based on a schema (and selected type/element), and then use the approach suggested by Jeff to locate that XML document to populate the type and value fields.

Regards

Gary