Creation of SOAP message does not put elements in proper sequence of complex typ

[SmartBear_Suppo]

Hi,

hmm.. the XML looks ok for my tests, probably I'm not adding what I should to provoke this.. can you give me more detailed instructions on what to add in which order?

Thanks in advance!

regards,

/Ole
eviware.com

[TEXAS_COMPTROLL_1]

Thanks for your response.

This problem isn't entirely consistent, we have found. It seems to come up when you already have valid XML and then try to add elements to it. But it doesn't happen in every scenario and we haven't come up with the scenarios that cause it.

You should see symptoms of this problem when you create a sample request. Try this exercise:
a) Create a sample request with mandatory elements and validate it. You should find that it is not valid due to not matching patterns (which is kind of expected and not a problem), but also you will see "Expected element 'Signatory@...before the end of the content in element Form05-169...' This means the XML generator had trouble figuring out what is mandatory from the schemas.

b) Now create a sample request with optional elements and validate it.
You should see items like:
Line 25: Expected element 'PreparerPersonName.. instead of PTIN.. here in element PaidPreparerInformation...'
This is a symptom of generating XML that is out of order. In order to fix this, you HAVE to edit XML. Problems with fields not matching patterns can be fixed in the form view.

To simulate the problem with our XML and schemas, try this:

1) Copy the attached XML to a sample request. It should already be valid according to the schemas.
Make sure you validate and format it from the XML view (Alt-V, alt-F)

2)Then go to the form view. Go down to Form05-102 and click 'Add' to add a new form.
Without doing anything else, go to the XML view and validate.
The XML should still be valid and you shouldn't see the new form yet. Somehow SoapUI knows this form was added though.

3) Now go back to the form view and click the validation checkbox. Two fields should be highlighted.
Put 333333333 in the FTIN field and TEST in the taxpayer name.

4) Go back to the XML view and validate. You should see one validation error:
line 123: Expected element 'TXCommonData... instead of 'Form05-102' ....
It should have put the 102 form ahead of the TXCommonData form (out of order)
.

[TEXAS_COMPTROLL_1]

Any updates or change of status on this issue?

thanks.

[papowell]

I have just rediscovered this problem. Still present in SOAPUI Pro 4.0.0.

This is a show stopper for us.

[SmartBear_Suppo]

Hi,

fix for this issue is available on the nightly build http://www.eviware.com/nightly-builds/s ... -SNAPSHOT/
Please give it a try and let us know if it works for you.

best regards
nebojsa
eviware.com

[TEXAS_COMPTROLL_1]

Thanks.

We are in the process of reviewing this solution and will post a reply.

--Dutch

[SmartBear_Suppo]

Hello,

We did not hear from you regarding bug you reported. We introduced the fix for it, but did not got
confirmation from you. We are assuming this is working for you now.

Thanks,
robert
/SmartBear

[ynorsa]

Hi,

I'm experiencing the same issue with ReadyAPI 1.8.0, and it's causing a lot of troubles.

Is it supposed to be working now?

I'm creating a new request from a WSDL file.

I'm filling in the elements directly in the "form" screen.

I submit the request.

When I look at the raw message that was sent, some elements (always the same!) are inverted (compared to the WSDL and to the form screen).

Thanks,

Yvan