| Author |
Message
|
| gabrielkalb |
 Posted: Mon Apr 08, 2013 6:06 pm Post subject: v8 Mapping Error |
 |
|
Newbie
Joined: 27 Sep 2011
Posts: 7
|
Hi, i am using a mapping with an input MRM and a output XMLNSC.
I am geting this error:
ExceptionList
RecoverableException
File:CHARACTER:F:\build\S000_P\src\DataFlowEngine\ImbDataFlowNode.cpp
Line:INTEGER:1129
Function:CHARACTER:ImbDataFlowNode::createExceptionList
Type:CHARACTER:ComIbmMSLMappingNode
Name:CHARACTER:Mainflow#FCMComposite_1_5
Label:CHARACTER:Mainflow.Mapping
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Node throwing exception
RecoverableException
File:CHARACTER:F:\build\S000_P\src\DataFlowEngine\PluginInterface\com_ibm_broker_plugin_CMbService.cpp
Line:INTEGER:1860
Function:CHARACTER:ImbJavaExceptionUtils::throwableToNativeException
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:4367
Text:CHARACTER:Unhandled exception in plugin method.
Insert
Type:INTEGER:5
Text:CHARACTER:evaluate
Insert
Type:INTEGER:5
Text:CHARACTER:Mapping
Insert
Type:INTEGER:5
Text:CHARACTER:java.lang.NullPointerException
RecoverableException
File:CHARACTER:F:\build\S000_P\src\DataFlowEngine\PluginInterface\com_ibm_broker_plugin_CMbService.cpp
Line:INTEGER:1878
Function:CHARACTER:ImbJavaExceptionUtils::throwableToNativeException
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:4395
Text:CHARACTER:Unhandled exception in plugin method
Insert
Type:INTEGER:5
Text:CHARACTER:java.lang.NullPointerException
Insert
Type:INTEGER:5
Text:CHARACTER:com.ibm.broker.ct.schema.SchemaTableGenerator
Insert
Type:INTEGER:5
Text:CHARACTER:traverseSchema
Insert
Type:INTEGER:5
Text:CHARACTER:SchemaTableGenerator.java
Insert
Type:INTEGER:2
Text:CHARACTER:90
This is the basic mapping, but if i move any field i got the error.
 |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Apr 08, 2013 6:14 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I believe there might have been an APAR for that. Fix in 8.0.0.3? check it! 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| goffinf |
| Posted: Tue Apr 09, 2013 12:05 am Post subject: |
|
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
8.0.0.3 ?
I thought we had just had 8.0.0.2 on the 31st March ? |
|
| Back to top |
|
|
| gabrielkalb |
| Posted: Tue Apr 09, 2013 4:31 am Post subject: |
|
|
Newbie
Joined: 27 Sep 2011
Posts: 7
|
Hi,
I updated my Broker to Fix 8.0.0.2, but now i cant import any XSD!
In version 8.0.0.0 i need to change the file name of xsd from XSD to xsd. (Yes, when is in UPPER case broker dont import). But now, broker dont import any XSD.
I need to import a lot of XSD of this link:
http://www.bcb.gov.br/pom/spb/Down/ftp/prod/XSDDOCV307.zip
And in Broker v6.1 i never had any problems to import then. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Apr 09, 2013 4:45 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/index.jsp?topic=%2Fcom.ibm.etools.mft.doc%2Fad30560_.htm
Some manual editing may be required. Please read the InfoCentre articles.
| Quote: |
| The required SOAP .xsds files are added to the application or library |
| Quote: |
| The broker model handles this document as expected, but in SOAP encoding array, elements are also allowed to use the type-elements from the SOAP encoding namespace. |
| Quote: |
| To handle this case, you must manually edit the broker model that is created by importing the WSDL, unless it is acceptable to have the parser treat it as a self-defined element. |
Wizard importers are helpers, not solutions. You are the developer, you are required to generate the solution.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Apr 09, 2013 4:50 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| gabrielkalb |
| Posted: Tue Apr 09, 2013 4:51 am Post subject: |
|
|
Newbie
Joined: 27 Sep 2011
Posts: 7
|
I am not import a WSDL, i am not working with SOAP.
Is a simple flow, i receive a MQ request from mainframe, and need to transform this request to XML, and send to a external application by MQ.
But this XML have a XSD made by this external application.
In Broker v8.0.0.0 and Broker v6.1 i dont have problems to import this XSDs. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Apr 09, 2013 4:55 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| gabrielkalb wrote: |
| I am not import a WSDL, i am not working with SOAP. Is a simple flow, i receive a MQ request from mainframe, and need to transform this request to XML, and send to a external application by MQ. But this XML have a XSD made by this external application. In Broker v8.0.0.0 and Broker v6.1 i dont have problems to import this XSDs. |
You have options.
You can use V6.1.
You can make 8.0.0.x work properly.
You can open a PMR.
In spite of the fact you are not using SOAP, the general principle still applies: Wizard importers are helpers not solutions. The developer must edit the files to create the solution.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Apr 09, 2013 5:07 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
the mapping doesn't appear to actually map anything, other than the properties.
There do not appear to be any lines connecting the message trees.
It's not at all clear what the issue with "importing xsds" is.
Best bet is to avoid the ongoing nattering that will continue to happen in this thread, and just open a PMR. |
|
| Back to top |
|
|
| gabrielkalb |
| Posted: Tue Apr 09, 2013 5:09 am Post subject: |
|
|
Newbie
Joined: 27 Sep 2011
Posts: 7
|
Hi,
Really? Use v6.1? Why IBM release v8 if we can not use it?
How i will make v8 work properly? Is exactly what im asking!
Edit a XSD????
But read what is a XSD(You can find it in Wikipedia):
"XSD can be used to express a set of rules to which an XML document must conform in order to be considered 'valid' according to that schema."
So why i will edit the rules of my client? |
|
| Back to top |
|
|
| marcelhun |
| Posted: Tue Apr 09, 2013 5:11 am Post subject: |
|
|
Novice
Joined: 09 Apr 2013
Posts: 11
|
Sorry Mr lancelotlinc.
But your response is not properly correct.
Back over to Broker 6.1 is not the best answer.
Why should he downgrade a version just to fix a XSD issue ?
But you're right to open a PMR 'cause it seems a bug of version 8. |
|
| Back to top |
|
|
| gabrielkalb |
| Posted: Tue Apr 09, 2013 5:12 am Post subject: |
|
|
Newbie
Joined: 27 Sep 2011
Posts: 7
|
mqjeff
| Quote: |
the mapping doesn't appear to actually map anything, other than the properties.
There do not appear to be any lines connecting the message trees. |
Like i said:
| Quote: |
| his is the basic mapping, but if i move any field i got the error. |
And...
| Quote: |
It's not at all clear what the issue with "importing xsds" is. |
Exactly! Its not clear! WMB v8 just dont import! |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Apr 09, 2013 5:13 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Again, you appear to have presented two separate problems:
1) a map that doesn't map anything, and also causes some kind of runtime error (I suspect there may be a causative link between those two!)
2) some kind of nebulous problem with importing an XSD into Toolkit.
Again, I recommend you review both of these again yourself, and with some kind of local colleague, and then open a PMR.
I recommend you cease paying attention to this thread and most of the comments that will continue to pile up, as it clearly will spend a lot of time thrashing around about things that don't actually mean anything. |
|
| Back to top |
|
|
| gabrielkalb |
| Posted: Tue Apr 09, 2013 5:25 am Post subject: |
|
|
Newbie
Joined: 27 Sep 2011
Posts: 7
|
| Quote: |
Again, you appear to have presented two separate problems:
1) a map that doesn't map anything, and also causes some kind of runtime error (I suspect there may be a causative link between those two!)
2) some kind of nebulous problem with importing an XSD into Toolkit. |
1) Like i said, when i map anything i got the error, and the image is just to show my map.
2) yes, very nebulous , i agree.
And i see that the only solution is open a PMR, and dont migrate to v8.
Thanks to all. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Apr 09, 2013 5:34 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| marcelhun wrote: |
Sorry Mr lancelotlinc.
But your response is not properly correct.
Back over to Broker 6.1 is not the best answer.
Why should he downgrade a version just to fix a XSD issue ?
But you're right to open a PMR 'cause it seems a bug of version 8. |
My good humor sometimes gets lost in my sarcasm. The 6.1 reference was more asperituos than serious.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
|
|
