Contributions
Re: Creation of SOAP message does not put elements in proper sequence of complex typ
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) .13 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.9KViews0likes0CommentsRe: Creation of SOAP message does not put elements in proper sequence of complex typ
Please see attached WSDL/schemas. You should be able to duplicate the issue by importing into SoapUI and using the form view to add forms. Then look at the generated XML in xml view. Let me know if i can be of further help.13 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.4KViews0likes0CommentsRe: Creation of SOAP message does not put elements in proper sequence of complex typ
We have also had this problem for almost a year. I tried the beta 4 version and the problem is still there. The symptoms are that adding elements in the form view does not add them in the schema order. You have to manually go to the xml view and cut and paste to get it in the correct order. This defeats the whole purpose of buying the Pro version for us, since it is being used by business users who don't know how to edit xml and want to use the form view. I'm not sure why there haven't been more reports of this, since it seems to be a pretty serious problem. Here is an example of the type of sequence that will not be conformed to: <xsd:element maxOccurs="1" minOccurs="1" name="TXCommonData" type="TXCommonType"/> <xsd:element maxOccurs="unbounded" minOccurs="0" name="Form05-102" type="TXFranchisePubInfoReportCType"/> <xsd:element maxOccurs="1" minOccurs="0" name="Form05-158A" type="TXFranchiseTaxReportACType"/> <xsd:element maxOccurs="1" minOccurs="0" name="Form05-158B" type="TXFranchiseTaxReportBCType"/> <xsd:element maxOccurs="1" minOccurs="0" name="Form05-160" type="TXCreditsSummaryScheduleCType"/> <xsd:element maxOccurs="1" minOccurs="0" name="Form05-163" type="TXFranchiseNoTaxDueReportCType"/> <xsd:element maxOccurs="1" minOccurs="0" name="Form05-164" type="TXFranchiseExtRequestCType"/> <xsd:element maxOccurs="unbounded" minOccurs="0" name="Form05-165" type="TXFranchiseExtAffilListCType"/> <xsd:element maxOccurs="unbounded" minOccurs="0" name="Form05-166" type="TXFranchiseAffiliatesScheCType"/> <xsd:element maxOccurs="unbounded" minOccurs="0" name="Form05-167" type="TXOwnershipInfoReportCType"/> <xsd:element maxOccurs="1" minOccurs="0" name="Form05-169" type="TXFranchiseTaxReportEZCType"/> <xsd:element maxOccurs="unbounded" minOccurs="0" name="Form05-175" type="TXFranchiseTieredParReprtCType"/> I've noticed also that the form view displays elements in the order according to the schema, not the order of the actual xml. So its confusing, because everything looks good in the form view, but when you look at the actual xml, it is out of order. This requires a technical person to go in and edit xml for many test cases.13 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.4KViews0likes0Comments