| Author |
Message
|
| sivaguru |
 Posted: Mon Sep 15, 2008 4:56 am Post subject: BIP5016E Error relating to NameSpace Declartion - Pls Help |
 |
|
Apprentice
Joined: 18 Jun 2008
Posts: 40
|
Hi,
Could any one pls help me out to identify the problem in the below code
Iam trying to add a namespace to the output xml and Iam getting the following error
Error:
--------
<detail>
<text>Exception. BIP2230E: Error detected whilst processing a message in node 'Test.Validate Input and Propogate'. : /build/S610_P/src/DataFlowEngine/ImbComputeNode.cpp: 464: ImbComputeNode::evaluate: ComIbmComputeNode: Test#FCMComposite_1_3BIP2488E: ('.Test_Compute.Main', '35.11') Error detected whilst executing the SQL statement ''PROPAGATE TO TERMINAL 'out3' FINALIZE DEFAULT DELETE DEFAULT;''. : /build/S610_P/src/DataFlowEngine/ImbRdl/ImbRdlStatementGroup.cpp: 602: SqlStatementGroup::execute: ComIbmComputeNode: Test#FCMComposite_1_3BIP2230E: Error detected whilst processing a message in node 'Test.Common_Error_Handler.HTTP Reply'. : /build/S610_P/src/WebServices/WSLibrary/ImbWSReplyNode.cpp: 744: ImbWSReplyNode::evaluate: ComIbmWSReplyNode: Test#FCMComposite_1_7.Common_Error_Handler#FCMComposite_1_5BIP5010E: XML Writing Errors have occurred. : /build/S610_P/src/MTI/MTIforBroker/GenXmlParser4/ImbXMLNSCParser.cpp: 673: ImbXMLNSCParser::refreshBitStreamFromElementsCommon: ComIbmWSInputNode: Test#FCMComposite_1_4BIP5016E: The item ''Messages'' of type ''folderType'' is not one of the expected types for a top level element at this point in the XML document. : /build/S610_P/src/MTI/MTIforBroker/GenXmlParser4/ImbXMLNSCWriter.cpp: 877: ImbXMLNSCWriter::writeMisc: : </text>
</detail>
Code:
---------
DECLARE Ns NAMESPACE 'http://www.test.org/b/message';
DECLARE xsi NAMESPACE 'http://www.w3.org/2001/XMLSchema-instance';
SET OutputRoot.XMLNSC.Ns:Messages.(XMLNSC.NamespaceDecl)xmlns = 'http://www.test.org/b/message';
SET OutputRoot.XMLNSC.Ns:Messages.(XMLNSC.NamespaceDecl)xmlns:xsi = 'http://www.w3.org/2001/XMLSchema-instance';
SET OutputRoot.XMLNSC.Ns:Messages.(XMLNSC.NamespaceDecl)xsi:schemaLocation = 'http://www.test.org/b/message ErrorSegment.xsd';
I suspect the error may be due to having the "Messages" in multiple occurance resulting in no top level element. But what I tried in the above code is to add 3 namespace at the rootelement "Messages"
Pls help me out to resolve the issue. Its of high importance.
|
|
| Back to top |
|
 |
| kimbert |
| Posted: Mon Sep 15, 2008 6:56 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
| Quote: |
| I suspect the error may be due to having the "Messages" in multiple occurance resulting in no top level element |
It may be. I suggest that you either
a) insert a Trace node or
b) connect the debugger
Look at the message tree just before the Output node, and the problem will probably be obvious. |
|
| Back to top |
|
|
| paranoid221 |
| Posted: Mon Sep 15, 2008 8:49 am Post subject: |
|
|
Centurion
Joined: 03 Apr 2006
Posts: 101
Location: USA
|
| Quote: |
SET OutputRoot.XMLNSC.Ns:Messages.(XMLNSC.NamespaceDecl)xsi:schemaLocation =
'http://www.test.org/b/message ErrorSegment.xsd';
|
Are you sure you need to have a space between 'message' and 'ErrorSegment' indicated above in BOLD??
_________________
LIFE is a series of complex calculations, somewhere multiplied by ZERO. |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Sep 15, 2008 10:54 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
The space is correct. But the (XMLNSC.NameSpaceDecl) is not.
This element is not a namespace declaration. It is a schemaLocation directive which happens to be in the ( previously and correctly declared ) xsi namespace. It should read
| Code: |
SET OutputRoot.XMLNSC.Ns:Messages.(XMLNSC.Attribute)xsi:schemaLocation =
'http://www.test.org/b/message ErrorSegment.xsd'; |
|
|
| Back to top |
|
|
| sivaguru |
| Posted: Mon Sep 15, 2008 7:21 pm Post subject: |
|
|
Apprentice
Joined: 18 Jun 2008
Posts: 40
|
Hi,
Thanks all for your inputs.
Mr.Kimbert the one specified inside the "<detail>" tag are trace log details.
So do I need to replace my code as
DECLARE Ns NAMESPACE 'http://www.test.org/b/message';
DECLARE xsi NAMESPACE 'http://www.w3.org/2001/XMLSchema-instance';
SET OutputRoot.XMLNSC.Ns:Messages.(XMLNSC.NamespaceDecl)xmlns = 'http://www.test.org/b/message';
SET OutputRoot.XMLNSC.Ns:Messages.(XMLNSC.NamespaceDecl)xmlns:xsi = 'http://www.w3.org/2001/XMLSchema-instance';
SET OutputRoot.XMLNSC.Ns:Messages.(XMLNSC.Attribute)xsi:schemaLocation =
'http://www.test.org/b/message ErrorSegment.xsd';
Meanwhile I just tried by having one namespace alone and ran the flow and I got the same error from the Trace log.
DECLARE Ns NAMESPACE 'http://www.test.org/b/message';
SET OutputRoot.XMLNSC.Ns:Messages.(XMLNSC.NamespaceDecl)xmlns = 'http://www.test.org/b/message';
CREATE FIELD OutputRoot.XMLNSC.Messages.RC TYPE NameValue VALUE '0';
So is there is any issue/pblm with respect to my declaration and definition of my first namespace itself.
Pls help me out.
|
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Sep 16, 2008 12:17 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
| Quote: |
| the one specified inside the "<detail>" tag are trace log details. |
I know it is. But I was talking about a node. The Trace node. It writes the message tree structure to a file or to user trace. The debugger can show you the message tree, but sometimes a Trace node is a better option.
| Quote: |
So is there is any issue/pblm with respect to my declaration and definition of my first namespace itself.
Pls help me out. |
I cannot see what you are doing wrong. Please insert a Trace node immediately before the output node, set the Pattern to '$Root" and the Destination to 'User Trace', and post the resulting output here. |
|
| Back to top |
|
|
|
|
