Author |
Message
|
fjb_saper |
Posted: Thu Feb 23, 2006 4:01 pm Post subject: Message Set definitions V 6.0 |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Has anybody encountered this?
Env = broker 6.0, Toolkit 6.0 + Fixpack.
In the toolkit when importing XSD files everything is fine and the dependencies and imports are resolved correctly.
But when creating a Message Definition file from scratch it will not allow me to import a message definition file .msxsd ( created by importing an xsd ) from a different namespace. The Message set is namespace aware.
If I try a non namespace aware message set the .xsd won't import.
I tried changing the message definition manually for the import but then it does not recognize the target namespace any more.
Thanks for your help
 _________________ MQ & Broker admin |
|
Back to top |
|
 |
kimbert |
Posted: Fri Feb 24, 2006 6:03 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Quote: |
it will not allow me to import a message definition file .msxsd ( created by importing an xsd ) from a different namespace. |
If you had said 'include' rather than 'import' I would not be surprised...
But you wouldn't do a thing like that, of course.  |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Feb 24, 2006 1:06 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
I did try both include and import. I used as well the map from the help to determine whether to use import or include.
On the include you get a red x : the file is in a different name space, so you have to use the import(as stated in the manual). And the import did not work at all....
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Feb 24, 2006 1:14 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Is there a namespace URI in the XML Physical properties of the message set?
If so, try creating a new message set and then import your files. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Feb 24, 2006 1:24 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
jefflowrey wrote: |
Is there a namespace URI in the XML Physical properties of the message set?
If so, try creating a new message set and then import your files. |
Jeff,
At this point my message definition file is empty. So there is none of this information. (XML Physical props).
The xsd I imported created types and has no messages. I just want to reuse those types in a message definition file.
Where I did add a message definition to the imported xsd I do not see any URI for the message. (XML Physical props) Would I need to add one?
Of course the type definitions generated by the imported xsds are all of complex type. Those are the ones I want to reuse and be able to define my message from them. As the message would not reside in the same ns as the building blocks I am trying to import the building blocks to the message definition file. This part fails for me.
I'm thinking PMR time ?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Feb 24, 2006 1:31 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
FJ - Not the message definition file, the message set file (.mset).
Check the Physical properties of your XML layer (likely called XML1).
Also, can you post the sequence of steps you are performing? _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Feb 24, 2006 2:19 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
OK
First the steps
Create Message set namespace aware.
Import file xsd from file system(3 times)
Create Message definition by importing xsd (3 times)
Create Message definition -- manual namespace comp.com/ns/schemas/test
Import any of the previous message definition files into the one just created.. This fails.
the .mset namespace uri (XML1 properties)
urn:comp.com/ns/schemas/CommonTypes
urn:comp.com/ns/schemas/MessageHeaders
urn:comp.com/ns/schemas/Listmgt
urn:comp.com/ns/schemas/test
Note that message headers which was imported from an xsd correctly references common types as import.
 _________________ MQ & Broker admin |
|
Back to top |
|
 |
|