MQSeries.net :: View topic - Soap Nodes Problem

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Soap Nodes Problem

Soap Nodes Problem

« View previous topic :: View next topic »

Author

Message

yadav.neeraj01

Posted: Thu Mar 27, 2014 1:35 am Post subject: Soap Nodes Problem

Apprentice

Joined: 23 Feb 2011
Posts: 49

Hi Experts,

I am getting an error when response is coming back from SOAP REPLY node.Please have a look and share your finding what could be the problem...i am not able to find even after trying a lot.....

Below is the exception tree list:-

Code:

ExceptionList
RecoverableException
      File:CHARACTER:F:\build\S700_P\src\DataFlowEngine\ImbDataFlowNode.cpp
      Line:INTEGER:1073
      Function:CHARACTER:ImbDataFlowNode::createExceptionList
      Type:CHARACTER:ComIbmSOAPExtractNode
      Name:CHARACTER:WS_Consumer#FCMComposite_1_1.gen/Operation1_MS_SOAPService_WS_Consumer#FCMComposite_1_2
      Label:CHARACTER:WS_Consumer.Operation1_MS_SOAPService.Extract
      Catalog:CHARACTER:BIPmsgs
      Severity:INTEGER:3
      Number:INTEGER:2230
      Text:CHARACTER:Node throwing exception
      ParserException
            File:CHARACTER:F:\build\S700_P\src\WebServices\WSLibrary\ImbSOAPParser.cpp
            Line:INTEGER:1966
            Function:CHARACTER:ImbSOAPParser::createSoapShapedTree
            Type:CHARACTER:
            Name:CHARACTER:
            Label:CHARACTER:
            Catalog:CHARACTER:BIPmsgs
            Severity:INTEGER:3
            Number:INTEGER:3614
            Text:CHARACTER:problem creating SOAP tree from bitstream
            ParserException
                  File:CHARACTER:F:\build\S700_P\src\MTI\MTIforBroker\GenXmlParser4\ImbXMLNSCParser.cpp
                  Line:INTEGER:893
                  Function:CHARACTER:ImbXMLNSCParser::parseFirstChild
                  Type:CHARACTER:
                  Name:CHARACTER:
                  Label:CHARACTER:
                  Catalog:CHARACTER:BIPmsgs
                  Severity:INTEGER:3
                  Number:INTEGER:5009
                  Text:CHARACTER:XML Parsing Errors have occurred
                  ParserException
                        File:CHARACTER:F:\build\S700_P\src\MTI\MTIforBroker\GenXmlParser4\ImbXMLNSCDocHandler.cpp
                        Line:INTEGER:616
                        Function:CHARACTER:ImbXMLNSCDocHandler::handleParseErrors
                        Type:CHARACTER:ComIbmMQInputNode
                        Name:CHARACTER:WS_Consumer#FCMComposite_1_2
                        Label:CHARACTER:WS_Consumer.MQ Input
                        Catalog:CHARACTER:BIPmsgs
                        Severity:INTEGER:3
                        Number:INTEGER:5025
                        Text:CHARACTER:A schema validation error has occurred while parsing the XML document
                        Insert
                              Type:INTEGER:2
                              Text:CHARACTER:5008
                        Insert
                              Type:INTEGER:2
                              Text:CHARACTER:2
                        Insert
                              Type:INTEGER:2
                              Text:CHARACTER:1
                        Insert
                              Type:INTEGER:2
                              Text:CHARACTER:144
                        Insert
                              Type:INTEGER:5
                              Text:CHARACTER:cvc-complex-type.2.4.e: Unexpected element. Element "PurchaseOrder" is not one of the choices.
                        Insert
                              Type:INTEGER:5
                              Text:CHARACTER:/XMLNSC/http://schemas.xmlsoap.org/soap/envelope/:Envelope/http://schemas.xmlsoap.org/soap/envelope/:Body

Simbu

Posted: Thu Mar 27, 2014 2:10 am Post subject:

Master

Joined: 17 Jun 2011
Posts: 289
Location: Tamil Nadu, India

Quote:

Type:INTEGER:5
Text:CHARACTER:cvc-complex-type.2.4.e: Unexpected element. Element "PurchaseOrder" is not one of the choices.
Insert
Type:INTEGER:5
Text:CHARACTER:/XMLNSC/http://schemas.xmlsoap.org/soap/envelope/:Envelope/http://schemas.xmlsoap.org/soap/envelope/:Body

The issue is with the soap message. Please see if soap message is as per the schema definition.

yadav.neeraj01

Posted: Thu Mar 27, 2014 2:39 am Post subject:

Apprentice

Joined: 23 Feb 2011
Posts: 49

Thanks for the fast reply.....but how can i see the response Soap message.....when message is coming from ReplyNode....directly error is coming... Below is that message

Code:

Message
Properties
      MessageSet:CHARACTER:MS_SOAP
      MessageType:CHARACTER:
      MessageFormat:CHARACTER:
      Encoding:INTEGER:546
      CodedCharSetId:INTEGER:1208
      Transactional:BOOLEAN:false
      Persistence:BOOLEAN:false

CreationTime:TIMESTAMP:java.util.GregorianCalendar[time=139564
2473905,areFieldsSet=true,areAllFieldsSet=false,lenient=true,zone=
sun.util.calendar.ZoneInfo[id="Asia/Calcutta",offset=19800000,dstS
avings=0,useDaylight=false,transitions=6,lastRule=null],firstDayOfW
eek=1,minimalDaysInFirstWeek=1,ERA=?,YEAR=2014,MONTH=2,WE
EK_OF_YEAR=?,WEEK_OF_MONTH=?,DAY_OF_MONTH=24,DAY_OF_YE
AR=?,DAY_OF_WEEK=?,DAY_OF_WEEK_IN_MONTH=?,AM_PM=0,HOUR
=11,HOUR_OF_DAY=11,MINUTE=57,SECOND=53,MILLISECOND=905,
ZONE_OFFSET=?,DST_OFFSET=?]
      ExpirationTime:INTEGER:-1
      Priority:INTEGER:0
      ReplyIdentifier:BLOB:[B@6c706c70
      ReplyProtocol:CHARACTER:MQ
      Topic:UNKNOWN:null
      ContentType:CHARACTER:text/xml;charset=utf-8
      IdentitySourceType:CHARACTER:
      IdentitySourceToken:CHARACTER:
      IdentitySourcePassword:CHARACTER:
      IdentitySourceIssuedBy:CHARACTER:
      IdentityMappedType:CHARACTER:
      IdentityMappedToken:CHARACTER:
      IdentityMappedPassword:CHARACTER:
      IdentityMappedIssuedBy:CHARACTER:
HTTPResponseHeader
      X-Original-HTTP-Status-Line:CHARACTER:HTTP/1.1 200 OK
      X-Original-HTTP-Status-Code:INTEGER:200
      Content-Type:CHARACTER:text/xml;charset=utf-8
      Content-Length:CHARACTER:1352
      Date:CHARACTER:Thu, 27 Mar 2014 10:37:41 GMT
      Server:CHARACTER:Apache-Coyote/1.1
SOAP
CHARACTER:problem creating SOAP tree from bitstream

harish.sun

Posted: Thu Mar 27, 2014 3:13 am Post subject:

Newbie

Joined: 29 Jul 2009
Posts: 9

This is the error your are getting: Unexpected element. Element "PurchaseOrder" is not one of the choices.

Make sure your SOAP schema can accept this element PurchaseOrder

Another thing to notice is your schema may expect other elements to be presented before the PurchaseOrder.

Can you post your SOAP schema.

yadav.neeraj01

Posted: Thu Mar 27, 2014 3:53 am Post subject:

Apprentice

Joined: 23 Feb 2011
Posts: 49

I am not sure if you are expecting this....if not let me know....

Code:

<?xml version="1.0" encoding="UTF-8"?><xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:group name="MIME_header_fields">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="Content-Type">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
   <xsd:attribute name="boundary" type="xsd:string"/>
   <xsd:attribute name="type" type="xsd:string"/>
   <xsd:attribute name="start" type="xsd:string"/>
   <xsd:attribute name="start-info" type="xsd:string"/>
   <xsd:attribute name="charset" type="xsd:string"/>
   </xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>

<xsd:element maxOccurs="1" minOccurs="0" name="Content-Transfer-Encoding">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="7bit"/>
<xsd:enumeration value="8bit"/>
<xsd:enumeration value="binary"/>
<xsd:enumeration value="quoted-printable"/>
<xsd:enumeration value="base64"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>

<xsd:element maxOccurs="1" minOccurs="0" name="Content-Id" type="xsd:string"/>
<xsd:element maxOccurs="1" minOccurs="0" name="Content-Description" type="xsd:string"/>
</xsd:sequence>
</xsd:group>

<xsd:complexType name="MIME_Headers_type">
<xsd:sequence>
<xsd:group ref="MIME_header_fields"/>
</xsd:sequence>
</xsd:complexType>

<xsd:complexType name="Attachment_type">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="MIME_Headers" type="MIME_Headers_type"/>
<xsd:element maxOccurs="1" minOccurs="1" name="Data" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>

<xsd:complexType name="SOAP_Msg_type">
<xsd:sequence>

<xsd:element maxOccurs="1" minOccurs="0" name="Context">
<xsd:complexType>
<xsd:sequence maxOccurs="1" minOccurs="1">

<xsd:element maxOccurs="1" minOccurs="0" name="SOAP_Version">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="1.1"/>
<xsd:enumeration value="1.2"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>

<xsd:element maxOccurs="1" minOccurs="0" name="Namespace">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>

<xsd:element maxOccurs="1" minOccurs="0" name="_XmlDeclaration">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
   <xsd:attribute name="Version" type="xsd:string"/>
   <xsd:attribute name="Encoding" type="xsd:string"/>
   </xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>

<xsd:element maxOccurs="1" minOccurs="0" name="XmlRoot">
<xsd:complexType>
<xsd:sequence maxOccurs="1" minOccurs="1">
<xsd:element maxOccurs="1" minOccurs="1" name="Envelope">
<xsd:complexType>
<xsd:sequence maxOccurs="1" minOccurs="0">
<xsd:element maxOccurs="1" minOccurs="0" name="Header" type="xsd:anyType"/>
<xsd:element maxOccurs="1" minOccurs="0" name="Body" type="xsd:anyType"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>

<xsd:element maxOccurs="1" minOccurs="0" name="MIME_Headers" type="MIME_Headers_type"/>
</xsd:sequence>

<xsd:attribute name="port" type="xsd:string"/>
<xsd:attribute name="portType" type="xsd:string"/>
<xsd:attribute name="portTypeNamespace" type="xsd:string"/>
<xsd:attribute name="operation" type="xsd:string"/>
<xsd:attribute name="operationType" type="xsd:string"/>
<xsd:attribute name="service" type="xsd:string"/>
<xsd:attribute name="serviceNamespace" type="xsd:string"/>
<xsd:attribute name="fileName" type="xsd:string"/>
</xsd:complexType>
</xsd:element>

<xsd:element maxOccurs="1" minOccurs="0" name="Header">
<xsd:complexType>
<xsd:sequence maxOccurs="unbounded">
<xsd:choice>
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<MRLocalGroup composition="message" content="open"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:choice>
</xsd:sequence>
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:complexType>
</xsd:element>

<xsd:element maxOccurs="1" minOccurs="1" name="Body">
<xsd:complexType>
<xsd:sequence maxOccurs="1">
<xsd:choice>
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<MRLocalGroup composition="message" content="openDefined"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:choice>
</xsd:sequence>
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:complexType>
</xsd:element>

<xsd:element maxOccurs="1" minOccurs="0" name="Attachment">
<xsd:complexType>
<xsd:sequence maxOccurs="unbounded" minOccurs="0">

<xsd:any namespace="##any" processContents="lax"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>

<xsd:element name="SOAP_Domain_Msg" type="SOAP_Msg_type">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<MRMessage messageDefinition="/0/SOAP_Domain_Msg;XSDElementDeclaration$MRObject"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:schema>

yadav.neeraj01

Posted: Sat Mar 29, 2014 10:51 am Post subject:

Apprentice

Joined: 23 Feb 2011
Posts: 49

Still not get the solution....

fjb_saper

Posted: Sat Mar 29, 2014 11:22 am Post subject:

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY

yadav.neeraj01 wrote:

Still not get the solution....

Congratulations! you've shown us about everything about the message but what we asked you for. Where is the message definition (and no we are not looking for the SOAP definition, we are looking for the make up of the SOAP:body. What is the name/namespace of the xmlroot, what are the elements allowed below it ?

_________________
MQ & Broker admin

yadav.neeraj01

Posted: Fri Apr 04, 2014 12:39 am Post subject:

Apprentice

Joined: 23 Feb 2011
Posts: 49

Code:

<?xml version="1.0" encoding="UTF-8"?><xsd:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/PurchaseOrderSchema.xsd" xmlns:tns="http://tempuri.org/PurchaseOrderSchema.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="PurchaseOrder" type="tns:PurchaseOrderType">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<MRMessage messageDefinition="/0/PurchaseOrder;XSDElementDeclaration$MRObject"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="PurchaseOrderType">
<xsd:sequence>
<xsd:element maxOccurs="2" name="ShipTo" type="tns:USAddress"/>
<xsd:element name="BillTo" type="tns:USAddress"/>
</xsd:sequence>
<xsd:attribute name="OrderDate" type="xsd:date"/>
</xsd:complexType>

<xsd:complexType name="USAddress">
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="street" type="xsd:string"/>
<xsd:element name="city" type="xsd:string"/>
<xsd:element name="state" type="xsd:string"/>
<xsd:element name="zip" type="xsd:integer"/>
</xsd:sequence>
<xsd:attribute fixed="US" name="country" type="xsd:NMTOKEN"/>
</xsd:complexType>
<xsd:element name="PurchaseOrderType" type="tns:PurchaseOrderType">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<MRMessage messageDefinition="/0/PurchaseOrderType;XSDElementDeclaration=1$MRObject"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="USAddress" type="tns:USAddress">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<MRMessage messageDefinition="/0/USAddress;XSDElementDeclaration=2$MRObject"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:schema>

If it helps to identify issue.......Reply with ur finding...

yadav.neeraj01

Posted: Sun Apr 13, 2014 10:19 pm Post subject:

Apprentice

Joined: 23 Feb 2011
Posts: 49

Plz help......

mqsiuser

Posted: Sun Apr 13, 2014 10:44 pm Post subject:

Yatiri

Joined: 15 Apr 2008
Posts: 637
Location: Germany

"just" use xml or json... imho schema validation is not important in the runtime

"Turn schema validation off" and let your code validate (this has been discussed before and can be seen with different view points)

harish.sun wrote:

Unexpected element. Element "PurchaseOrder" is not one of the choices.

Get/Extract the xml. It will start with "PurchaseOrder".

Get/Extract the xsd: It will not start with PurchaseOrder (Or it does, then also check namespaces!)

The xsd may be "included" in a wsdl file

Use a professional xml editor such as xmlspy or oxygen.

Find out why your xml (root element) does not match your schema definition (xsd)...

You can check for "well formedness" and "validate" against a schema from within these tools including (much more) hints on what is going wrong (than the broker runtime gives you). You can inspect, find and fix the error(s) there (with these tools): It is meant to be this way. A runtime is not a development enviroment !

If you fix the mistake (at the beginning of the file) likely/probably the whole thing works.

Make sure you validate (your xml) successfully against the schema (xsd) in the professional xml editing tool (before going back to broker)!
_________________
Just use REFERENCEs

Last edited by mqsiuser on Sun Apr 13, 2014 10:56 pm; edited 1 time in total

fjb_saper

Posted: Sun Apr 13, 2014 10:55 pm Post subject:

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY

your schema says

Quote:

but the last child of Soap:body is
<PurchaseOrder> and not <tns:PurchaseOrder> ??

also the .xsd indicates a location and should not be part of your namespace declaration...

Are you sure you are using the right namespace??

_________________
MQ & Broker admin

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Soap Nodes Problem

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Protected by Anti-Spam ACP