| Author |
Message
|
| ammu |
 Posted: Mon Jul 02, 2007 1:18 am Post subject: prob while creating mxsd from a wsdl file |
 |
|
Apprentice
Joined: 26 Apr 2007
Posts: 25
|
Hi i am trying to crate a msg def file from wsdl file. i have two querries.
1. How my final msg set should look? i.e., once i import the wsdl, two mxsd are created. One for soapenv and one for my actual msg. The soapenv.mxsd has some wildcard elements and wildcard attributes. Should i replace it with the elements ref from the other mxsd?
2. When the wsdl file is simple (without any import/include) i am able to create the mxsd file from it. But when the wsdl file contains the import/include stmt, i am unable to create the mxsd. (when import stmt is mentioned, then while create the mxsd it says the following error:
BIP0116E: unable to write to local fiel system.). How do i create the mxsd when the wsdl file has import/inclue stmts. |
|
| Back to top |
|
 |
| ammu |
| Posted: Mon Jul 02, 2007 2:27 am Post subject: Message sets for SOAP message modeling |
|
|
Apprentice
Joined: 26 Apr 2007
Posts: 25
|
Got the soln for my 1st querry:
Follow this link:
http://www.ibm.com/developerworks/ibm/library/i-merge12/index.html
(under Message sets for SOAP message modeling tab).
But still having problem with creating mxsd from the wsdl file which has import/include stmt.
The wsdl file is a valid one. I know am missing some point while creating the msg set. Can any one point me to a ref to create the mxsd.[/u] |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jul 02, 2007 3:11 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
There should be a log file created when you import the wsdl to create the message def... It might tell you why the import failed.
In general, you need to create mxsds from the import/include files as well.
So if your wsdl includes common.xsd and header.xsd or whatever, then you need to create message definition files from those as well as the wsdl itself.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jul 02, 2007 3:29 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| jefflowrey wrote: |
There should be a log file created when you import the wsdl to create the message def... It might tell you why the import failed.
In general, you need to create mxsds from the import/include files as well.
So if your wsdl includes common.xsd and header.xsd or whatever, then you need to create message definition files from those as well as the wsdl itself. |
If you do not want to import the dependencies and just want the import of the wsdl to do it all you MUST have the dependencies (import/include) in the directories relative to the location of the wsdl as specified in the wsdl's location description)
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ammu |
| Posted: Mon Jul 02, 2007 6:31 am Post subject: |
|
|
Apprentice
Joined: 26 Apr 2007
Posts: 25
|
Thanks Jeff & fjb,
got the ans.
The prob is in the wsdl file while importing the schema location is specified as "http:...". I am unable to import this wsdl.
When i copied the xsd to my local workarea, and specified that location in the wsdl it works fine.
Is this the way we need to specify the schema location?
But with schema location as "http.." why i am unable to import it. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jul 02, 2007 2:50 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
We don't use http:, we use urn: for the schema location.
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| recallsunny |
| Posted: Tue Jul 03, 2007 10:07 am Post subject: |
|
|
Disciple
Joined: 15 Jun 2005
Posts: 163
Location: Massachusetts
|
From IBM toolkit documentation: When an XML schema resides on a remote server
| Code: |
<purchaseOrder xmlns:="www.ibm.com"
xsi:schemaLocation="http://www.ibm.com po/xsd/PurchaseOrder.xsd "> |
Several functions in the XML editor, such as validation and content assist, require the availability of a DTD or an XML schema.
Normally, this case poses no problem, because the DTD or XML schema can be retrieved from the remote server. However, if you are behind a firewall, and do not have a SOCKSified system, the workbench currently does not provide a way for you to specify a socks server for retrieving a DTD or XML schema. If you are unable to SOCKSify your system, the workaround for this problem is to retrieve a copy of the DTD or XML schema (using a Web browser, for example) and save that copy on your local machine. Then, you can either place a local copy in the same project as your XML file, or use the XML Catalog to associate a public identifier with the DTD's (local) location.
In your case check if the machine has access to the URI (from behind the firewall) or download the file to local path as suggested above. |
|
| Back to top |
|
|
|
|
