IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

Error: namespace prefix ssdh not defined for element DocumentHeader

  • 1.  Error: namespace prefix ssdh not defined for element DocumentHeader

    Posted Wed July 21, 2010 11:02 AM

    Hi,
    I am doing a 7C8 and I have the required document type defined in documents/Payload. Now, when the model goes to “Send External Request Document” step, the step details shows that the “namespace prefix ssdh not defined for element SemiconductorProcessDataNotification”. I did check the NSDecls in TPA and confirmed that prefix was defined. The following is the error message taken from step details.

    Error Message →
    com.wm.app.tn.err.EXMLException: wm.tn.doc:recognize com.wm.app.tn.doc.BizDocTypeException Couldn’t get document bytes (0) com.wm.lang.flow.WattEvaluationException: com.wm.lang.xml.WMDocumentException: [ISC.0042.9328] Error: namespace prefix ssdh not defined for element DocumentHeader (1) com.wm.lang.flow.WattEvaluationException: com.wm.lang.xml.WMDocumentException: [ISC.0042.9328] Error: namespace prefix ssdh not defined for element DocumentHeader com.wm.lang.flow.WattEvaluationException: com.wm.lang.xml.WMDocumentException: [ISC.0042.9328] Error: namespace prefix ssdh not defined for element DocumentHeader com.wm.lang.flow.WattEvaluationException: com.wm.lang.xml.WMDocumentException: [ISC.0042.9328] Error: namespace prefix ssdh not defined for element DocumentHeader com.wm.lang.flow.WattEvaluationException: com.wm.lang.xml.WMDocumentException: [ISC.0042 com.wm.app.tn.err.EXMLException: wm.tn.doc:recognize com.wm.app.tn.doc.BizDocTypeException Couldn’t get document bytes (0) com.wm.lang.flow.WattEvaluationException: com.wm.lang.xml.WMDocumentException: [ISC.0042.9328] Error: namespace prefix ssdh not defined for element DocumentHeader (1) com.wm.lang.flow.WattEvaluationException: com.wm.lang.xml.WMDocumentException: [ISC.0042.9328] Error: namespace prefix ssdh not defined for element DocumentHeader com.wm.lang.flow.WattEvaluationException: com.wm.lang.xml.WMDocumentException: [ISC.0042.9328] Error: namespace prefix ssdh not defined for element DocumentHeader com.wm.lang.flow.WattEvaluationException: com.wm.lang.xml.WMDocumentException: [ISC.0042.9328] Error: namespace prefix ssdh not defined for element DocumentHeader com.wm.lang.flow.WattEvaluationException: com.wm.lang.xml.WMDocumentException: [ISC.0042.9328] Error: namespace prefix ssdh not defined for element DocumentHeader at com.wm.lang.xql.XqlQuery.getResults(XqlQuery.java:1389) at com.wm.lang.xql.XqlQuery.getString(XqlQuery.java:396) at com.wm.app.tn.doc.XMLDocType.getDocumentContent(XMLDocType.java:1882) at com.wm.app.tn.doc.XMLDocType.appendDocumentContent(XMLDocType.java:720) at com.wm.app.tn.doc.XMLDocType.createEnvelope(XMLDocType.java:544) at com.wm.app.tn.doc.BizDocTypeReg.recognizeAndCreate(BizDocTypeReg.java:528) at wm.tn.docimpl.recognize(docimpl.java:1003) at sun.reflect.GeneratedMethodAccessor157.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:403) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:631) at com.wm.app.b2b.server.util.tspace.ReservationProcessor.proces…


    #webMethods
    #Adapters-and-E-Standards
    #Integration-Server-and-ESB


  • 2.  RE: Error: namespace prefix ssdh not defined for element DocumentHeader

    Posted Tue September 21, 2010 07:02 PM

    Any responses to this question? I’m looking for a solution for similar problem


    #webMethods
    #Adapters-and-E-Standards
    #Integration-Server-and-ESB


  • 3.  RE: Error: namespace prefix ssdh not defined for element DocumentHeader

    Posted Wed February 13, 2013 07:06 PM

    Hi Folks,
    So any solution was identified for the above error ?


    #Integration-Server-and-ESB
    #Adapters-and-E-Standards
    #webMethods