| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Is there an upper limit to the total namespaces defined? |
« View previous topic :: View next topic » |
| Author |
Message
|
| rahoor |
 Posted: Mon Jul 06, 2009 10:40 am Post subject: Is there an upper limit to the total namespaces defined? |
 |
|
Apprentice
Joined: 21 Jul 2003
Posts: 34
|
Is there an upper limit to the total namespaces defined in a single message set?
Reason I ask:
Some of the defined name spaces in a single message set do not show up via the ctrl space short cut key when editing an ESQL compute node.
Hard coding the name spaces that are missing at the top of the module and referrring to them generates errors about the element reference not found during the ESQL save phase.
The ones that do show up appear to be the first three out of a total of seven namespaces defined in the tool kit. |
|
| Back to top |
|
 |
| kimbert |
| Posted: Mon Jul 06, 2009 1:09 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Some of the defined name spaces in a single message set do not show up via the ctrl space short cut key |
Please can you define 'defined' 
I'm not sure whether you are talking about the Namespaces table in the XML physical format, or just talking about a complex schema which uses 7 namespaces.
I would expect the ESQL code assist to use the logical information from the schema, not the namespaces listed in the XML physical format. |
|
| Back to top |
|
|
| rahoor |
| Posted: Tue Jul 07, 2009 5:27 pm Post subject: multiple name space question resolution |
|
|
Apprentice
Joined: 21 Jul 2003
Posts: 34
|
The problem was most likely that some of the elements in a complex type message where not selectable within ESQL
The complex type was defined in a different name space within the same message set.
Message definition was:
Given a message defined in Namespace 1 (NS1)
AMessage - ComplexTypeof1and2
---ElementA - of NS1:complexType1
---ElementB - of NS1:complexType2
-------NS2:simpleType
-------------NS2:elementy - string type
-------------NS2:elementz - string type
The resolution was to change the above to
AMessage - ComplexTypeof1and2
---ElementA - of NS1:complexType1
---ElementB - of NS1:complexType2
-------ElementC - of NS2:complexType
----------NS2:elementy - string type
----------NS2:elementz - string type
This allowed referencing to elementy, elementz from within the ESQL where as before this, they were not present after ctrl spacing after the NS2:ElementC.
Since these message definitions were created using XSDs into the broker, the issue may have been produced by:
+ The XSD used was imported out of sequence, ie NS2 should have been imported first before importing the NS1 XSD
+ The NS1 XSD itself was using syntax that the broker could not handle
In any event, this was not a limit on the total number of namespaces being used.
thank you for your reply |
|
| 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
|
|
|
|
