Author |
Message
|
venkat_chekka |
Posted: Tue Jun 30, 2009 1:06 pm Post subject: Unable to create Mapping node with WMBEvent Structure |
|
|
Apprentice
Joined: 14 Apr 2006 Posts: 37
|
Hi,
I am trying to create mapping node between WMBEvent as source and and database table as target.
WMBEvent is Message Broker Monitoring Event structure
I have created Message Defination file for WMBEvent from IBM Supplied Message xsd. When I am trying to add this message definition file as a source to the mapping node it is giving an error message and not getting added.(a dilog box is coming saying look at the log files for more information) have looked at .metadata/log but nothing found.
Could you please guide me regarding this?
Thanks,
Venkat Chekka. |
|
Back to top |
|
 |
Gaya3 |
Posted: Tue Jun 30, 2009 9:54 pm Post subject: Re: Unable to create Mapping node with WMBEvent Structure |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
venkat_chekka wrote: |
I have created Message Defination file for WMBEvent from IBM Supplied Message xsd. |
Let me know from where you got this, is it from IBM or from IBM links
please provide me the details _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
kimbert |
Posted: Wed Jul 01, 2009 4:43 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
It is supplied as part of the Monitoring sample. |
|
Back to top |
|
 |
venkat_chekka |
Posted: Wed Jul 01, 2009 4:55 am Post subject: |
|
|
Apprentice
Joined: 14 Apr 2006 Posts: 37
|
yes, I have created WMBEvent Message Definition file like this:
Right click on Message Definition>New>>Message Definition File From>>IBM Supplied Messages>> Message Broker Monitoring Event
I have created succussfully message definition file but getting problem while using this in mapping node.
Could you help me regarding this ASAP??
Thanks,
Venkat Chekka. |
|
Back to top |
|
 |
kimbert |
Posted: Wed Jul 01, 2009 5:04 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Here is what you have told us so far:
Quote: |
it is giving an error message and not getting added.(a dilog box is coming saying look at the log files for more information) |
It's fairly hard to help without knowing *exactly* what the error message said. |
|
Back to top |
|
 |
kishoreraju |
Posted: Wed Jul 01, 2009 6:09 am Post subject: |
|
|
Disciple
Joined: 30 Sep 2004 Posts: 156
|
Hi kimbert,
Thankx for your prompted response.
The below is the excetion information from eclipse log.
Code: |
!ENTRY org.eclipse.ui 4 0 2009-07-01 09:39:37.460
!MESSAGE Failed to execute runnable (java.lang.ClassCastException: com.ibm.etools.mapping.msg.impl.MsgSourceMapRootImpl incompatible with com.ibm.etools.model.gplang.Statement)
!STACK 0
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.ClassCastException: com.ibm.etools.mapping.msg.impl.MsgSourceMapRootImpl incompatible with com.ibm.etools.model.gplang.Statement)
at org.eclipse.swt.SWT.error(Unknown Source)
at org.eclipse.swt.SWT.error(Unknown Source)
at org.eclipse.swt.widgets.Synchronizer.contact admin(Unknown Source)
at org.eclipse.swt.widgets.Display.contact admin(Unknown Source)
at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
at org.eclipse.ui.internal.Workbench.runEventLoop(Unknown Source)
at org.eclipse.ui.internal.Workbench.runUI(Unknown Source)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Unknown Source)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(Unknown Source)
at org.eclipse.ui.internal.ide.IDEApplication.run(Unknown Source)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(Unknown Source)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Unknown Source)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.invokeFramework(Unknown Source)
at org.eclipse.core.launcher.Main.basicRun(Unknown Source)
at org.eclipse.core.launcher.Main.run(Unknown Source)
at org.eclipse.core.launcher.Main.main(Unknown Source)
Caused by: java.lang.ClassCastException: com.ibm.etools.mapping.msg.impl.MsgSourceMapRootImpl incompatible with com.ibm.etools.model.gplang.Statement
at com.ibm.etools.mft.debug.mapping.actions.ToggleBreakpointAdapter.statementFromSelection(Unknown Source)
at com.ibm.etools.mft.debug.mapping.actions.ToggleBreakpointAdapter.canToggleLineBreakpoints(Unknown Source)
at org.eclipse.debug.internal.ui.actions.breakpoints.RetargetToggleLineBreakpointAction.canPerformAction(Unknown Source)
at org.eclipse.debug.internal.ui.actions.RetargetAction$1.run(Unknown Source)
at org.eclipse.swt.widgets.RunnableLock.run(Unknown Source)
... 21 more |
|
|
Back to top |
|
 |
kishoreraju |
Posted: Wed Jul 01, 2009 6:22 am Post subject: |
|
|
Disciple
Joined: 30 Sep 2004 Posts: 156
|
Hi,
I tried this with message broker 6.1.0.3 and 6.1.0.4 but the result is same. is there any restrictions in mapping node with the strucutre of the message definition file(datatypes) or with the xsds.
you can find the WMBEvents.xsd in the below location
Code: |
\WMBT610\configuration\org.eclipse.osgi\bundles\946\1\.cp\ibm\nodes\event\WMBEvent.xsd . |
|
|
Back to top |
|
 |
kimbert |
Posted: Wed Jul 01, 2009 2:13 pm Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
That looks like a good case for a PMR.
However, before you go though that process, you might want to try the usual Eclipse tricks ( start with -clean option, rebuild the entire workspace )
Don't forget to remove the -clean option from your shortcut if you do try that - otherwise your toolkit will become *very* slow at starting up. |
|
Back to top |
|
 |
|