| Author |
Message
|
| santoshpanuganti |
 Posted: Thu Dec 11, 2008 7:24 am Post subject: Accessing Processing Instruction in MB |
 |
|
Newbie
Joined: 30 Nov 2008
Posts: 4
|
Hi,
Can any one tell me how to access PI in ESQL. My input is like this
<?xml version="1.0" encoding="utf-8" ?>
<XXXX>
<?ao-eventname PolicyValidate?>
<?ao-type fire?>
<?ao-userid {1234567890}?>
..........
And i want to access "ao-eventname" to check whether it is "PolicyValidate" or not??? Plz help me out guys....its very urgent.
Thanks in Advance. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Dec 11, 2008 7:29 am Post subject: Re: Accessing Processing Instruction in MB |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
|
| Back to top |
|
|
| santoshpanuganti |
| Posted: Thu Dec 11, 2008 7:32 am Post subject: |
|
|
Newbie
Joined: 30 Nov 2008
Posts: 4
|
Yes, i tried it but while deploying i am getting the syntax error..
[/quote] |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Dec 11, 2008 7:36 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| santoshpanuganti wrote: |
while deploying i am getting the syntax error..
|
What syntax error? 
I'm psychotic not psychic. I need to be told these things.
If your original post has been something like "Hi, trying to access a processing instruction, saw ... in the info centre, coded ........... and it said ............ when I deployed it so what should I do? It's urgent" then I wouldn't have wasted time pointing you at something you'd already seen!
Better postings with all the information gets you better responses.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Dec 11, 2008 7:38 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You haven't told us nearly enough to know why you're getting a syntax error.
The answer to your question about "how to access a processing instruction" is very dependant on *what* domain you are using.
You should *only* be using MRM-XML or XMLNSC, and really not even MRM-XML.
If you are properly using XMLNSC, then you should be using an XMLNSC named constant to access a PI field. But be aware that XMLNSC options may or may not pass PI fields to you, as it tries to retain only what it thinks is significant to the business use. So you may also have to adjust the XMLNSC options. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Dec 11, 2008 7:39 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
You might also wish to consider telling us what version of WMB you're using. Patched to what level.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| santoshpanuganti |
| Posted: Thu Dec 11, 2008 7:57 am Post subject: |
|
|
Newbie
Joined: 30 Nov 2008
Posts: 4
|
Ok, i confess that it was my mistake for not giving full details....
Broker Version is 6.1.0.2 & Toolkit is 6.1.0.3
Parser: XMLNS - MRM |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Dec 11, 2008 8:18 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| santoshpanuganti wrote: |
Ok, i confess that it was my mistake for not giving full details....
|
And the error you got on deploy says.......? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Dec 11, 2008 8:29 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| santoshpanuganti wrote: |
| Parser: XMLNS - MRM |
This is not a valid parser name.
It is the concatentation of names of two completely separate parsers, that behave in completely separate ways, and neither of which should actually be used when processing XML with Message Broker 6.1.
If you are trying to use XMLNS constants to access MRM-XML fields, then you will fail. If you are trying to use MRM constants to access XMLNS fields, then you will fail.
If you switch to using XMLNSC, and you use XMLNSC constants, then the odds of a) you being successful, b) your flow being performant and maintainable are both *vastly* increased. |
|
| Back to top |
|
|
| santoshpanuganti |
| Posted: Thu Dec 11, 2008 8:58 am Post subject: |
|
|
Newbie
Joined: 30 Nov 2008
Posts: 4
|
| Quote: |
| And the error you got on deploy says.......? |
The correlation name 'XMLNS.ao' is not valid.
| Quote: |
| This is not a valid parser name |
Ok, what about if i Declare a Variable of CHAR type & then try to parse XMLNS PI, will it work???
Like:
DECLARE PV CHAR;
SET PV = InputRoot.XMLNS.XXXX.(XMLNS.ProcessInstruction);
But still i am getting error.. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Dec 11, 2008 10:14 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| santoshpanuganti wrote: |
| Ok, what about if i Declare a Variable of CHAR type & then try to parse XMLNS PI, will it work??? |
Only if the parser can parse the document element.
| santoshpanuganti wrote: |
InputRoot.XMLNS.XXXX.(XMLNS.ProcessInstruction);
But still i am getting error.. |
Maybe if you tried InputRoot.XMLNS.(XMLNS.ProcessingInstruction)XXXX it might work better.......
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
