Jump to content
We have recently updated our Privacy Statement, available here ×

Issues with REST service binding


Recommended Posts

Hi Team, We have a created REST generic service where it will accept a different type of XML, coming from different servers. we can not declare a specific schema. hence we have kept a input type as string and planning to map the XML and parse data with specific schemas later in the code. When we are trying to send a XML data as input we are getting a below error. {http://tns.tibco.com/bw/fault}ActivityOutputValidationFault: com.tibco.bx.core.faults.BxException: Activity output data validation error. The output data from activity [skudefinitionresponse/post] in process [skudefinitionresponse.Process], module [sKUDefinitionResponse] does not conform to the activity output schema. The attribute 'id' is not permitted on the element 'skudefinition' because the element has a simple type definition, '{http://www.w3.org/2001/XMLSchema}string'. The attribute 'updatetype' is not permitted on the element 'skudefinition' because the element has a simple type definition, '{http://www.w3.org/2001/XMLSchema}string'. The element "skudefinition" cannot have children because the type definition is a simple type. A non-absent element declaration or type definition is not known for the element product. The element "skudefinition" cannot have children because the type definition is a simple type. A non-absent element declaration or type definition is not known for the element product. Schema= {http://www.w3.org/2001/XMLSchema}string Data= Data being the name of the input string variable. First we tried with "application/xml" we got a above error and we changed it to "application/text" we are able to successfully run it. we tried using this Swagger, Postman client and some custom client application and result was same for all. The application which calling this tibco rest service doesnt have the capability to send data in "application/text" format. hence it has to send it in "application/xml" format. Please provide a solution for this one. Please Note : This behavior is observer for SOAP service also.

 

This is for TIBCO 6.3.4

Link to comment
Share on other sites

×
×
  • Create New...