| Author |
Message
|
| sravan |
 Posted: Tue Jan 31, 2012 11:05 am Post subject: Message set issue. |
 |
|
Centurion
Joined: 02 Apr 2010
Posts: 104
Location: Charlotte
|
We are having common xsds with name space - "http://abc.com/emdsvc/types/common"
and service xsds with name space-
"http://abc.com/emdsvc/types/member"
While in MB version 6 the common xsds were refereed sucessfully and message definition is created.
In V7 It is failing with the error
src-resolve: Cannot resolve name 'Q1:SourceKey' to a(n) 'type definition' component.
where SourceKey is one of the common xsd referred from member name space xsd.
even in V6 it gave an error at xsd until the honor all schemas for xsds option was selected.
Please let me know about this.
_________________
skr_wmb |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Tue Jan 31, 2012 12:45 pm Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
The error seems like it's looking for an XSD import and not finding it. Make sure all your XSD files are located in the same directory as the WSDL or prime XSD.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jan 31, 2012 12:48 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Import the xsd dependencies into the workspace first, then import the xsds that make use of those dependencies.
Or just go ahead and make sure you've imported all of the relevant xsds before you start dealing with any project level errors.
And you might have to correct some include paths. |
|
| Back to top |
|
|
| sravan |
| Posted: Tue Jan 31, 2012 4:39 pm Post subject: |
|
|
Centurion
Joined: 02 Apr 2010
Posts: 104
Location: Charlotte
|
There are no new common xsds all were existing in V6.
When we migrated to V7 the new service xsd in the name space member is not able to create xsd using reference from common
_________________
skr_wmb |
|
| Back to top |
|
|
| ruchir123 |
| Posted: Tue Jan 31, 2012 10:29 pm Post subject: |
|
|
Acolyte
Joined: 04 Jan 2012
Posts: 58
|
I agree with lancelotlinc. It mostly comes when not able to find the import xsd file. It will be good if you check your xsd again.
I had same issue. For me also it was giving almost same erorr on V6.1. As i was using many xsd to create message set using WSDL. So it happens that it has created some messages in message set and for some it is giving error. Then i genrated xml schema with that messages having error in them. Then when it generated xml , in that xml i got the solution for my issue as i missed some part of import in xsd.
May be you can try can try out the same way. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Jan 31, 2012 10:46 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Have you tried EXPORTING the message set project from your V6.1 workspace and then IMPORTING it into your V7 workspace?
If this does not work then IMHO it is PMR time.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
