| Author |
Message
|
| dinsb4u |
 Posted: Fri Apr 04, 2008 6:55 am Post subject: Unresolvable MRM Field Reference |
 |
|
Novice
Joined: 12 Apr 2007
Posts: 10
|
Hi,
I am currently using the v6.0.2 version of the Message Broker Toolkit. I have defined an MRM parser and invoked the same through a Reset Content Descriptor Node in the flow. Immediately after this RCD node, I have a Compute Node, in which I have coded the following ESQL statement :-
DECLARE inCount INTEGER;
SET inCount = CARDINALITY (InputRoot.MRM.MyFields.*[]);
I get the following warning - 'Unresolvable Message Field Reference InputRoot.MRM.MyFields.*[]' which I wanted to avoid. The same piece of code worked fine in the v5 version of the Toolkit.
Could someone please guide me with the same? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Apr 04, 2008 7:25 am Post subject: Re: Unresolvable MRM Field Reference |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| dinsb4u wrote: |
| I get the following warning - |
Does it run when you deploy it? I wouldn't be surprised to discover it did.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| dinsb4u |
| Posted: Fri Apr 04, 2008 8:24 am Post subject: |
|
|
Novice
Joined: 12 Apr 2007
Posts: 10
|
It does run successfully, with the warning.  I just wanted to know if there is any coding way by which I could do away with those warning messages. I was thinking that my usage of Cardinality function on InputRoot.MRM.MyFields.*[], was the cause of warning. |
|
| Back to top |
|
|
| wbi_telecom |
| Posted: Fri Apr 04, 2008 8:48 am Post subject: |
|
|
Disciple
Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
|
In 6.0 the toolkit validates the message set structure against the ESQL inside the node. (it did not use to do that in 5.0) so you will get this warnings if you have not refereced your message set project OR if the ESQL in not adhering to the message set structure.
If both the conditions are true, try building the project.
Cheers, |
|
| Back to top |
|
|
| dinsb4u |
| Posted: Fri Apr 04, 2008 8:55 am Post subject: |
|
|
Novice
Joined: 12 Apr 2007
Posts: 10
|
I have referenced the message set project appropriately, and also 'cleaned' and re-built the project, but to no avail.  |
|
| Back to top |
|
|
| wbi_telecom |
| Posted: Fri Apr 04, 2008 9:06 am Post subject: |
|
|
Disciple
Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
|
Then it must be because of the '.*[]' at the end of the reference. If you really want this warning to go away , don't use cardinality . Use Lastmove instead.
Cheers, |
|
| Back to top |
|
|
|
|
