| Author |
Message
|
| Vitor |
 Posted: Wed Dec 08, 2010 1:47 pm Post subject: Using IBM supplied message causes Toolkit error |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
The platform:
Toolkit 6.1.0.5 on Windows
The requirement:
Take a Broker monitoring message, extract some values from it and write out an XML message containing them
The method:
1) Generate a message for the event by going New -> Message Definition From -> IBM supplied message, and for the user message by using New -> Message Definition from -> XML Schema
2) Start up a mapping node, set the event message as the source, the other as the target then drag & drop the half dozen fields I need
The problem:
Starting the Mapping editor gives me a box saying "An error has occured - look in the log". Looking in the log I see all this Java nonsense:
| Code: |
!ENTRY org.eclipse.jface 4 2 2010-12-08 16:30:18.593
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
!STACK 0
java.lang.NullPointerException
at com.ibm.etools.mapping.xsd.MXSDResourceHelper.hasMRMessageAnnotation(Unknown Source)
at com.ibm.etools.mapping.treehelper.mxsd.MXSDImageProvider.getXSDElementImage(Unknown Source)
at com.ibm.etools.mapping.treehelper.mxsd.MXSDImageProvider.getXSDElementImage(Unknown Source)
at com.ibm.etools.mapping.treehelper.mxsd.MXSDImageProvider.getImageDescriptor(Unknown Source)
at com.ibm.etools.mapping.treehelper.AbstractTreeNodeImageProvider.getDecoratedImageDescriptor(Unknown Source)
at com.ibm.etools.mapping.treenode.AbstractTreeNode.getDecoratedImageDescriptor(Unknown Source)
at com.ibm.etools.mapping.viewer.lines.TreeLabelProvider.getImage(Unknown Source)
at org.eclipse.jface.viewers.StructuredViewer.buildLabel(Unknown Source)
at org.eclipse.jface.viewers.TreeViewer.doUpdateItem(Unknown Source)
at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(Unknown Source)
...
...
etc
etc
|
Tried restarting the toolkit with -clean, rebooted the PC & attempted some moral building soundbites on the editor. All yields the same result.
Clearly I can obtain the same end result with a small piece of ESQL. But I'd like to know, if only for my own satisfaction, what I've missed in this exercise. Both message sets will display properly, appear to be valid & as I'd expect them and if the mapping editor is told to use the user message as source & target is happy as the proverbial pig in the proverbial stuff. It's only if I'm mapping to or from the IBM event message it gets cross.
Am I missing a plug in or something? Does the Java just hate me? Is this a message from a higher power that I should avoid Mapping nodes? Or an indication it's been a long day & I should have seen the obvious error?
Advices (and ridicule) welcomed.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Wed Dec 08, 2010 2:07 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| Quote: |
Is this a message from a higher power that I should avoid Mapping nodes?
|
In a word, YES (te-he)
  
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Dec 08, 2010 3:49 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Do you have the same problem at 6.1.0.8?
 |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Dec 08, 2010 4:37 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
Do you have the same problem at 6.1.0.8?
|
It will be months before I can tell. Assuming we just don't go straight to WMBv7. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Dec 09, 2010 8:26 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| Do you have the same problem at 6.1.0.8? |
No I don't, though it still burps if you add the MQMD to the source along with the event message. But nothing a Toolkit clean doesn't seem to have fixed.
All I need to do now is get the BAR file produced on my illicit 6.1.0.8 Toolkit deployed to the 6.1.0.5 broker.
That's going to work isn't it? At a technical if not political level? Just because the tooling's got a few unexpected features the bar file's ok unless it actually contains something that's not in the runtime at that level?
And this is just a mapping node & some message sets.
Time to fill out some forms and confess my sin.
Well, this sin
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Dec 09, 2010 8:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Vitor wrote: |
All I need to do now is get the BAR file produced on my illicit 6.1.0.8 Toolkit deployed to the 6.1.0.5 broker.
That's going to work isn't it? At a technical if not political level? |
Generally. |
|
| Back to top |
|
|
|
|
