|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
[Solved] SET XML Attribute issue |
« View previous topic :: View next topic » |
Author |
Message
|
elvis_gn |
Posted: Wed Aug 24, 2005 4:05 am Post subject: [Solved] SET XML Attribute issue |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
Hi,
I am trying to set the XML attribute for a SAP IDoc.
There are many instances of attributes in many of the complex segments within the Idoc,few of the SET are working and few aren't....
The syntax of the code is common across all
SET Reference.(XML.Attribute)verb = 'Create';
The "verb" appears as elements in some cases...
I did a search and found that this seems to be a commom problem, but could not find one which solves mine....
I have tried
SET Reference.verb = 'Create';
SET Reference.(XML.Attribute)verb VALUE = 'Create';
SET Reference.(XML.Attribute)verb = FIELDVALUE('Create');
Please help....
Last edited by elvis_gn on Thu Aug 25, 2005 12:52 am; edited 1 time in total |
|
Back to top |
|
 |
elvis_gn |
Posted: Wed Aug 24, 2005 9:16 pm Post subject: |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
The problem, still persists, does anyone know why this is happening... |
|
Back to top |
|
 |
javaforvivek |
Posted: Thu Aug 25, 2005 12:43 am Post subject: |
|
|
 Master
Joined: 14 Jun 2002 Posts: 282 Location: Pune,India
|
Have you tried something like this?
Code: |
CREATE FIELD OutputRoot.XML.TestCase.description TYPE NameValue VALUE 'This is my TestCase' ;
|
This is from ESQL manual of WBIMB, under CREATE statement and it gives output like this:
<TestCase description = "This is my TestCase">
I dont know whether you want your output to be IDoc or a simply XML message. _________________ Vivek
------------------------------------------------------
...when you have eliminated the impossible, whatever remains, however improbable, must be the truth. |
|
Back to top |
|
 |
elvis_gn |
Posted: Thu Aug 25, 2005 12:51 am Post subject: |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
Thanks for the reply.
I finally found that the error was with the naming of the namespaces which I could only identify with XMLSpy....The tags will go haywire if just one alphabet is named incorrectly....Using the XML schema and validating the XML solved it.
Thanks a lot. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|