Description Tim Buss 2007-09-28 17:18:46 EDT

If a namepace is set on the SOAP element of an EventNotice message it is not forwarded to the service flow.  Such extra namespaces generally are used by extension data and are not seen byteh event manager.  For example here the namespace withteh prefix xsd: is used in the extension data to define the type="xsd:string" attributes but of the namespace si not forwarded the definition of xsd: will be missing and the ServiceFlow may have difficulty.

<?xml version='1.0' encoding='UTF-8' standalone='no' ?>
<SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns="http://www.eclipse.org/alf/schema/EventBase/1" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <SOAP-ENV:Body>
    <ns:EventNotice>
      <EventNotice>
.......
        <s:Extension xmlns:s="http://www.eclipse.org/alf/schema/EventBase/1">
          <s:ItemId xsi:type="xsd:string">00029</s:ItemId>
          <s:ItemId_TableRecId xsi:type="xsd:string">1002:23</s:ItemId_TableRecId>
          <s:oneUnnamed xsi:type="xsd:string"></s:oneUnnamed>
          <s:Unnamed2 xsi:type="xsd:string"></s:Unnamed2>
          <s:threeUnnamed3 xsi:type="xsd:string"></s:threeUnnamed3>
          <s:Unnamed4 xsi:type="xsd:int">0</s:Unnamed4>
        </s:Extension>
      </EventNotice>
    </ns:EventNotice>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>