| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| DFDL library IBMdefined CobolDataDefinitionFormat.xsd |
« View previous topic :: View next topic » |
| Author |
Message
|
| j.f.sorge |
 Posted: Wed Oct 23, 2013 6:13 am Post subject: DFDL library IBMdefined CobolDataDefinitionFormat.xsd |
 |
|
Master
Joined: 27 Feb 2008
Posts: 218
|
I've got a library containing a DFDL message model for COBOL structure, so the editor added CobolDataDefinitionFormat.xsd into the IBMdefined folder. When deploying a second library which contains the same CobolDataDefinitionFormat.xsd (I compared both files within the WMBT) it failes with
| Code: |
| BIP5035E: The XMLNSC validator signalled that an error occurred at line 20 while validating a XML schema. The file being processed was IBMdefined/CobolDataDefinitionFormat.xsd in library XXX. The message from the XMLNSC validator is: sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'http://www.ibm.com/dfdl/CobolDataDefinitionFormat,PICX__string' |
So I decided to create a separate library which only contains the IBMdefined folder and added a project reference to that new project. I've modified the referencing xsd files as following
OLD
| Code: |
| <xsd:import namespace="http://www.ibm.com/dfdl/CobolDataDefinitionFormat" schemaLocation="IBMdefined/CobolDataDefinitionFormat.xsd"/> |
NEW
| Code: |
| <xsd:import namespace="http://www.ibm.com/dfdl/CobolDataDefinitionFormat" schemaLocation="../IBMdefined/IBMdefined/CobolDataDefinitionFormat.xsd"/> |
After that change the biuld via mqsicreatebar fails with the following error
| Code: |
Problem 0: Resource - /XXX/YYY.xsd; Error message - CTDX1100E : XSD: The maxLength facet is not permitted in a type based on 'http://www.ibm.com/dfdl/CobolDataDefinitionFormat#PICX__string'.
Problem 1: Resource - /XXX/YYY.xsd; Error message - CTDX1100E : XSD: Type reference 'http://www.ibm.com/dfdl/CobolDataDefinitionFormat#PICX__string' is unresolved. |
Did anyone had same issues with WMB(T) 8.0.0.1?
_________________
IBM Certified Solution Designer - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Oct 23, 2013 6:30 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
I recognise this error. You need IC94463 - or v8.0.0.3.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
| j.f.sorge |
| Posted: Wed Oct 23, 2013 6:36 am Post subject: |
|
|
Master
Joined: 27 Feb 2008
Posts: 218
|
| kimbert wrote: |
| I recognise this error. You need IC94463 - or v8.0.0.3. |
Thanks for your quick reply!
The APAR description does not really makes it clear to me whether it affects both WMBT and WMB runtime. As on one hand I'm having problem with runtime (and duplicate IBMdefined files) and on the other hand I'm getting into trouble with mqsicreatebar when building a bar for that two libraries.
[edit]
The last thing is that deploying from WMBT runs fine, so probably it is an error with the ANT deployment-routine. But that deployment will always add the second library containing the IBMdefined xsd into the bar with the other format. Therefore the existing version will always be overriden.
Finally the mqsicreatebar problem has been solved by adding a default "Data Format" into CobolDataDefinitionFormat.xsd by copying the values from "CobolDataFormat".
[/edit]
_________________
IBM Certified Solution Designer - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Oct 23, 2013 6:55 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
If you get the errors when the xsds are in a library, and the errors go away when you move them back into the application, then IC94463 is the answer.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
| j.f.sorge |
| Posted: Wed Oct 23, 2013 6:58 am Post subject: |
|
|
Master
Joined: 27 Feb 2008
Posts: 218
|
| kimbert wrote: |
| If you get the errors when the xsds are in a library, and the errors go away when you move them back into the application, then IC94463 is the answer. |
I'm sorry but I don't have any application here, just an old Message Broker Project. I'll test whether runtime will parse data successfully. Otherwise I'll contact the support in order to get a private path for the APAR mentioned.
_________________
IBM Certified Solution Designer - WebSphere MQ V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.0
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| 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
|
|
|
|
