| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Attribute disappear in a REFERENCE |
« View previous topic :: View next topic » |
| Author |
Message
|
| TonyD |
 Posted: Tue Jun 26, 2007 7:47 pm Post subject: Attribute disappear in a REFERENCE |
 |
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
I have the following XML test message:
| Code: |
<EmployeeMessage operation="create">
<RequestHeader timestamp="2007-06-15T16:35:23" transactionIdentifier="123456"/>
<EmployeeDetails startDate="2007-06-07">
<FirstName>Fred</FirstName>
<LastName>Bloggs</LastName>
</EmployeeDetails>
</EmployeeMessage>
|
I want to pass it to an ESQL procedure so am declaring a REFERENCE to pass in the parameter list:
| Code: |
DECLARE inRef REFERENCE TO InputRoot.XMLNS;
|
However when I then try to do processing against the 'RequestHeader' attributes in the procedure I find that they are not present. When I use the flow debugger to step through the execution I can see that, following the above statement, 'inRef.EmployeeMessage.RequestHeader' is present but it's attributes have disappeared. However the attributes are still present for 'inRef.EmployeeMessage' (operation = create) and for 'inRef.EmpoyeeMessage.EmployeeDetails' (startDate = 2007-06-07).
All I could think is that it must be something to do with the fact that 'RequestHeader' has only child attributes, not child elements. I therefore added a child element 'HeaderType' of 'RequestHeader'. When I ran the above statement using the new message with the additional element 'inRef.Employee.RequestHeader' now had the attributes that were previously mssing as well the 'HeaderType' child element!
Before raisng a PMR to report this behaviour I thought I should check to see if there is any reason why the above might be expected? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Jun 27, 2007 2:07 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Can you please describe how you are accessing the attributes?
Did you ever contemplate walking the tree looking for the attributes? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| special_agent_Queue |
| Posted: Wed Jun 27, 2007 6:06 am Post subject: |
|
|
Centurion
Joined: 27 Jul 2006
Posts: 102
|
From experience, sometimes the debugger doesn't show attributes. Most of the time it is when there are no other child elements present for that particular field. Adding the HeaderType child element only forced the debugger to show them to you. This means that they were present before the HeaderType child element was added.
The debugger isn't quite reliable. If you see something in the debugger that looks wrong, AND it corresponds with something wrong in the output message, that's when you need to fix something.
Personally, I try to use trace nodes instead of using the debugger whenever I can. |
|
| 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
|
|
|
|
