| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP5029E: Error 'schema_reference.4: Failed to read schema |
« View previous topic :: View next topic » |
| Author |
Message
|
| NiceGuy |
 Posted: Wed Nov 09, 2011 11:15 am Post subject: BIP5029E: Error 'schema_reference.4: Failed to read schema |
 |
|
Apprentice
Joined: 11 Jun 2009
Posts: 37
|
Hi Eveyone,
I'm creating a message set based on a wsdl, the wsdl has a few
xml schema files that are imported into it.
When I created the message set I get no errors based on the wsdl,
and have constructed the bar file accordingly with no errors either
.... the bar contains the message set and its subsequent message flow.
However ... though things appear fine, when I attempt to deploy the bar
file to the exectution group, I get the following error:
| Code: |
BIP5029E: Error 'schema_reference.4: Failed to read schema
document
The XMLNSC parser is preprocessing the XML Schemas for the message set and it has encountered an error. Check that the XML Schemas in the message set are valid.
The task was unsuccessful: The deployment was unsuccessful. |
I did check the XML Schema files with a third pary tool and all schema's
report valid.
I was wondering if anyone else had any ideas?
Thanks again |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Nov 09, 2011 12:21 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Firstly, if there was anything wrong with your WSDL or xsds then the toolkit should have informed you when you tried to build the BAR file ( or even before that ). So this sounds a product defect.
In case this helps you to work around the problem...it sounds like a problem with the schemaLocation attribute on one of the imports/includes in one of your xsds.
You could try unzipping the BAR file and then unzipping the xsdzip file that is inside it. That *should* leave you with a consistent and correct set of xsds that validate in any XML tool. I suggest that you also check ( in the unzipped xsds ) for unusual characters in the schemaLocation paths ( spaces, perhaps? ). |
|
| Back to top |
|
|
| NiceGuy |
| Posted: Fri Nov 11, 2011 11:47 am Post subject: |
|
|
Apprentice
Joined: 11 Jun 2009
Posts: 37
|
Hi Everyone,
Thanks Kimbert for the reply.
Just to conclude and close this message trail. It turns out the problem
was with the schemaLocation and included xsd files.
To clarify, the problem was simply with the filename length. The
filenames for a few of the wsdl's and xsd's were simply too long.
I changed the filenames to something meaningful but far shorter
and everything deployed as expected afterward.
Hope this helps someone else out 
Thanks Kimbert |
|
| 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
|
|
|
|
