| Author |
Message
|
| deepeshk79 |
 Posted: Mon Dec 28, 2009 6:21 pm Post subject: |
 |
|
Apprentice
Joined: 25 Mar 2007
Posts: 45
Location: Los Angeles
|
Jeff,
As per fjb_saper,
| Quote: |
As for the syntax I thought you had to include it in () like "Type (XMLNSC.Element) "
|
Even if we have (), the error is still there.
Also in the link provided by Vitor, it says we can use XMLNSC.Element to point to elements within a Parent tag. Only XMLNSC.Field has a limitation as it can point only to CData or Text within an element. So I tried XMLNSC.Element but its giving me a deployment time error.
Thanks,
Deepesh |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Dec 28, 2009 6:21 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| deepeshk79 wrote: |
| Any thoughts? |
I think you should try reading things. Either the product documentation or my post earlier in this thread.
There's also some good advice in the New Posters section that might help you look less foolish in your future posts.
More foolish would of course be tricky. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| deepeshk79 |
| Posted: Mon Dec 28, 2009 6:32 pm Post subject: |
|
|
Apprentice
Joined: 25 Mar 2007
Posts: 45
Location: Los Angeles
|
Vitor I did read all the above posts in this thread and as per the link that you gave, it says we can use XMLNSC.Element to point to elements within a Parent tag. Only XMLNSC.Field has a limitation as it can point only to CData or Text within an element.
My question is when XMLNSC.Element is supported then why it does it fail here... fjb_saper said using () to correct the syntax... but it didnt work...!!! |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Dec 28, 2009 6:45 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| deepeshk79 wrote: |
| My question is when XMLNSC.Element is supported then why it does it fail here... |
For the reasons given in the link I posted. Have another read.
| deepeshk79 wrote: |
| fjb_saper said using () to correct the syntax... but it didnt work...!!! |
I'm not surprised.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Tue Dec 29, 2009 1:04 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| Vitor wrote: |
| deepeshk79 wrote: |
| My question is when XMLNSC.Element is supported then why it does it fail here... |
For the reasons given in the link I posted. Have another read. |
To be fair, the posted link doesn't actually explain why the MOVE statement fails with TYPE XMLNSC.Element.
However, the links for the MOVE statement and the FIELDTYPE function explain it better. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Dec 29, 2009 4:15 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I am corrected. When using the MOVE statement you cannot use XMLNSC.Element, you will have to differentiate between XMLNSC.Folder and XMLNSC.Field or even the different fieldtypes at the end of the tree branch...
I would have hoped that it allowed you something a little bit more generic. Apparently the setting of the XMLNSC.Element type is only allowed on the output. So I don't know/(haven't tried) if this (XMLNSC.Element) would work on a copied input tree (like in Environment or OutputRoot.XMLNSC...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| deepeshk79 |
| Posted: Thu Jan 07, 2010 9:34 am Post subject: |
|
|
Apprentice
Joined: 25 Mar 2007
Posts: 45
Location: Los Angeles
|
| Thanks rekarm01 and fjb_saper. The links that you provided has the details, the earlier link didnt talk about the MOVE statement failing with TYPE XMLNSC.Element. I think Vitor has a habit of reading too much than whats there in it |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Jan 08, 2010 1:56 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Apparently the setting of the XMLNSC.Element type is only allowed on the output |
XMLNSC.Element is a 'wildcard' field type. It can be used when querying *any* message tree ( so works on InputRoot, OutputRoot, Environment, LocalEnvironment ). It cannot be used to set the field type, because the SET statement would be ambiguous.
I'm not sure why it doesn't work for a MOVE statement - that sounds like something that ought to be fixed. |
|
| Back to top |
|
|
|
|
