|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
BIP0182E -- Problem in Creating BAR in WBIMB 5 FP6.0 |
« View previous topic :: View next topic » |
Author |
Message
|
srindies |
Posted: Thu Feb 02, 2006 6:27 am Post subject: BIP0182E -- Problem in Creating BAR in WBIMB 5 FP6.0 |
|
|
Apprentice
Joined: 06 Jan 2006 Posts: 28
|
Hi All,
I have been facing problem in creating a BAR file. I have used XML Schema for creating message set and has nested complex type in it. I searched in IBM and applied Fixpack 6.0, but still problem exists. I couldnt get much information from APAR List. Error message is similar to
BIP0182E -- Message Set Compilation Error
A exception was thrown while compiling the message set. The cause of the error was an exception of type "class.java.ArrayIndexOutOfBoundException" with message "-2". .....
APAR Link:
http://www-1.ibm.com/support/docview.wss?uid=swg1IC42638
Thanks & Regards,
Sridhar H |
|
Back to top |
|
 |
kimbert |
Posted: Thu Feb 02, 2006 7:54 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
From the URL you quoted...
Quote: |
Please note that just applying the fix to this
problem will not correct the BIP0182E error. The complex types
that have been affected by this defect need to be edited and
saved again... |
So...have you performed this re-editing step after upgrading to FP6? |
|
Back to top |
|
 |
srindies |
Posted: Fri Feb 03, 2006 10:15 pm Post subject: |
|
|
Apprentice
Joined: 06 Jan 2006 Posts: 28
|
Sorry for my delayed response Kimbert. I forgot to include in of the point earlier. I applied Fixpack 6 and started my development activity. So, I believe resave option may not work correctly. Since, I am a newbie, I couldnt get much info from IBM APAR. To point out clearly,
Quote: |
However, the Brokers Toolkit Message Editor takes into account
the fact that extension or restriction was selected and so still
stores the complex type as being an extension or restriction.
Since no complex type was specified the type of xsd:anyType
is used. This means that the current complex type becomes an
extension or restriction of xsd:anyType. A restriction of
xsd:anyType is allowed in XML schema, however it is not
possible to extend xsd:anyType. This is why, when the Message
Set is added to a bar file, the dictionary generation
routines reject this mxsd model with a BIP0182E. If the
corresponding mxsd file is examined directly in an XML
editor/viewer then the incorrect
<xsd:extension base="xsd:anyType">
should be seen. If this extension of xsd:anyType is not seen
then this particular error has not encountered. |
What are these restrictions and extension signifies??
Regards,
Sridhar H |
|
Back to top |
|
 |
srindies |
Posted: Sat Feb 04, 2006 7:50 am Post subject: |
|
|
Apprentice
Joined: 06 Jan 2006 Posts: 28
|
Thanks Kimbert, I have re-edited and solved this problem. I would be of great help if someone throws limelight on these restriction and extension property discussed here.
Regards,
Sridhar H |
|
Back to top |
|
 |
kimbert |
Posted: Mon Feb 06, 2006 2:09 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
|
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
|
|
|
|