| Author |
Message
|
| klabran |
 Posted: Thu Jun 15, 2006 8:30 am Post subject: XML MRM Message missing tags in Mapping |
 |
|
Master
Joined: 19 Feb 2004
Posts: 259
Location: Flagstaff AZ
|
I have a complex XML schema that I created an MRM message with by importing the schema.
In the MRM I notice several tags that are defined in extension schema files that the main schema uses but many of these tags are in curly braces.
EX: j:CitationSubject is of j:SubjectType which is of {PersonType}.
All tags that are in tags that have the {} don't show up
when I go into a mapping node.
I don't know why this is happening or how to fix this?
Any help would be appreciated.
Thanks,
Kevin
Last edited by klabran on Fri Jun 16, 2006 6:48 am; edited 2 times in total |
|
| Back to top |
|
 |
| klabran |
| Posted: Fri Jun 16, 2006 6:46 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 259
Location: Flagstaff AZ
|
Yikes! 
It's good to see I have a unique problem.  |
|
| Back to top |
|
|
| mqmaniac |
| Posted: Fri Jun 16, 2006 7:37 am Post subject: |
|
|
Master
Joined: 27 Dec 2005
Posts: 201
|
I do not think Its Unique..
Just No One understood the Exactly what you are looking for..
Pls Elaborate!!!!!! |
|
| Back to top |
|
|
| klabran |
| Posted: Fri Jun 16, 2006 8:09 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 259
Location: Flagstaff AZ
|
A picture (or two) is worth a thousand words. 
Sorry for the lack of formatting or anything.
http://www.coconino.az.gov/cji.aspx?id=4019
I have two images. The first is of the MRM of the schema. Note the schema is correct but showing curly braces around many of the types that are in jxdm.mxsd.
The second image is of the mapping node. I have set the target to be my message in the first image. Note that any of the tags belonging to a tag with a curly brace around it in the first image do not show up in the mapping node.
How do I correct this? |
|
| Back to top |
|
|
| mqmaniac |
| Posted: Fri Jun 16, 2006 10:30 am Post subject: |
|
|
Master
Joined: 27 Dec 2005
Posts: 201
|
| What Properties did you select for .mxsd File? |
|
| Back to top |
|
|
| klabran |
| Posted: Fri Jun 16, 2006 12:15 pm Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 259
Location: Flagstaff AZ
|
| I have alot of mxsd files.... Which one(s) are you interested in and what properties? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Jun 17, 2006 4:33 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
To make sure that the message set works properly....(V6)
- place all your xsd and wsdl files under the message set in a relative path so that they can be accessed through the relative location as described in the import statements
- make sure the definition only contain relative paths
- import the wsdl file
- a word of caution... It is sometimes reasonable to create a specific xsd containing the makeup of all the messages used. The wsdl import only imports the information needed for the current priority/ setup./ port. (binding)
If your wsdl includes multiple bindings you might want to go back to the xsd containing all the message definitions and reimport it, thus adding the messages for all bindings.
- you do not need a wsdl to use the xsd import facility. But be cautious... Start from bottom up and make sure you do not miss any of the building blocks.
- If you build some files manually (mxsd) check the imports and the referencing definitions by opening the file in text mode and looking at the xml. Usually I have to modify a little bit by hand. The consequence might be that a type {acct:GLAccount} might no longer be recognized...
Go to that complex type pull up the list of types and select the right one. This usually fixes it
I realize by the look of it that this might not work well for you as the sheer number of xsds involved in your messages might be a little bit overwhelming. However you should have a number of modelers that can supply you with the correct xsds / wsdl and all you would have to do then is to import them into your message set (remember the relative path thing)
From what I remember it won't let you import the wsdl (strict settings) if you are missing some building blocks (xsd files)
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Jun 17, 2006 4:38 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Last but not least (I'm sure you already found out) sometimes a "Project -- clean -- selected project" works wonders on the message set.
And finally if something changed in your message set you might have to edit / change your map.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| klabran |
| Posted: Mon Jun 19, 2006 9:19 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 259
Location: Flagstaff AZ
|
| Quote: |
place all your xsd and wsdl files under the message set in a relative path so that they can be accessed through the relative location as described in the import statements |
Did that already.
| Quote: |
make sure the definition only contain relative paths
|
Did that already.
| Quote: |
import the wsdl file
|
Don't have any wsdl files
| Quote: |
a word of caution... It is sometimes reasonable to create a specific xsd containing the makeup of all the messages used. The wsdl import only imports the information needed for the current priority/ setup./ port. (binding)
If your wsdl includes multiple bindings you might want to go back to the xsd containing all the message definitions and reimport it, thus adding the messages for all bindings.
|
My xsd only has one message and I have no wsdl.
| Quote: |
you do not need a wsdl to use the xsd import facility. But be cautious... Start from bottom up and make sure you do not miss any of the building blocks.
|
Learned that already since I don't have any wsdl files.
| Quote: |
If you build some files manually (mxsd) check the imports and the referencing definitions by opening the file in text mode and looking at the xml. Usually I have to modify a little bit by hand. The consequence might be that a type {acct:GLAccount} might no longer be recognized...
Go to that complex type pull up the list of types and select the right one. This usually fixes it
|
Didn't build any manually. Everything was brought in via import utility.
| Quote: |
I realize by the look of it that this might not work well for you as the sheer number of xsds involved in your messages might be a little bit overwhelming. However you should have a number of modelers that can supply you with the correct xsds / wsdl and all you would have to do then is to import them into your message set (remember the relative path thing)
|
Ya, overwhelming to say the least and the toolkits performance is overly underwhelming with this message. It's fast becoming useless to try it this way for me.
Modelers? My xsd are correct (well-formed and valid). I use xml spy for my xml adventures.
At this point I am very disappointed in the performance of the toolkit for this. It takes 4 minutes on my machine to save any change in the mapping node for this message. I have 2GB of RAM but it's pegging the CPU @ 100%. I have messed with the heap size but it didn't do anything. The CPU usage appears to be the bottleneck. I told it to clean up the project and it took over 20 minutes to perform the operation.
*Sigh*
Thanks,
Kevin |
|
| Back to top |
|
|
| klabran |
| Posted: Thu Jul 06, 2006 8:25 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 259
Location: Flagstaff AZ
|
Well I am glad to report the missing tags and horrible performance have been fixed.
How did I fix this?
Upgraded to the WMB 6 toolkit.
Yeeeeeehaaaaaaa!!!!
  |
|
| Back to top |
|
|
|
|
