| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| InputBody compiler warning |
« View previous topic :: View next topic » |
| Author |
Message
|
| goffinf |
 Posted: Sun May 14, 2006 3:53 am Post subject: InputBody compiler warning |
 |
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
WBIMB version 6 (windows and AIX)
When I (and my colleagues) use eSQL that contains the InputBody correlation name, such as :-
DECLARE payloadRoot REFERENCE TO InputBody.foo
and then build the project that contains it, we always get a 'warning' :-
Unresovable message field reference "InputBody.foo"
This does *not* stop the code from working successfully, but we would obviously prefer that the warning was not issued.
Does anyone know why this is so ??
If we substitute the code for :-
DECLARE payloadRoot REFERENCE TO InputRoot.XMLNSC.foo
or :-
DECLARE payloadRoot REFERENCE TO InputRoot.*[<].foo
no warning is issued, but again we would prefer in some cases to use the parser agnostic correlation name.
Cheers
Fraser. |
|
| Back to top |
|
 |
| tej |
| Posted: Thu Jul 13, 2006 5:35 am Post subject: |
|
|
Novice
Joined: 18 Nov 2002
Posts: 20
|
| I think InputBody was depricated. I don't see this in any of the V 6.0 document. I too got the same warning. I overcame the issue the same way you did. Thanks |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Thu Jul 13, 2006 5:47 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
|
| Back to top |
|
|
| tej |
| Posted: Thu Jul 13, 2006 6:02 am Post subject: |
|
|
Novice
Joined: 18 Nov 2002
Posts: 20
|
| I know even it shows warning, that piece will work. Is there any reason why it throws warning ? Thanks |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Thu Jul 13, 2006 6:35 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi tej,
| tej wrote: |
| I know even it shows warning, that piece will work. Is there any reason why it throws warning ? Thanks |
I think the link above and the one from that, explains why and how to prevent it(in some ways)
I repeat from that link, its indicative that the flow dosen't know what u've coded, and hence it could throw errors at runtime....so be warned.
Initially you will notice these things, now i don't even realize the marks exist 
Regards. |
|
| 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
|
|
|
|
