| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Base type resolving issue in MRM XML Message set |
« View previous topic :: View next topic » |
| Author |
Message
|
| satya2481 |
 Posted: Thu Dec 25, 2008 11:18 pm Post subject: Base type resolving issue in MRM XML Message set |
 |
|
Disciple
Joined: 26 Apr 2007
Posts: 170
Location: Bengaluru
|
Hi All,
I am using WMB Toolkit V6.1 Fix pack 3. I am creating a message set from the XML schema files. OAGIS standards are used to create the schema and they are zipped in a file. I have followed below steps to create the entire message defintion.
1. Unzip the file which contained all the OAGIS and custom schemas
2. Check the dependencies on the schemas and import one by one from Bottom up approache.
3. I have tried to use the "mqsicreatemsgdefs" toolkit command to craete the message definitions but it didnt succeed to create the defintions by resolving the dependent schemas automaticallly
4. Now I have left with 2 issues
a. Unable to resolve the basetype for one of the complex element. I have manually tried to locate the derived base type and tried to add but whene I click on the OK button after selecting the basetype the toolkit shows progress and will not complete.
b. Unable to locate one of the element references.
The schema looks good in the XMLSpy tool.
I am facing another issue in my message flow.
1. We are using Java compute node in our interfaces.
Has any one faced these issues. I would like to know what MB Java API I should use to create a default namespace in the output message.
Where can I get all the MB Java API documentation. I have checked in the IBM V6.1 Information center, Document list etc bu no luck. If anyone provide me the link it would be of great help.
Thank you in advance
Satya
_________________
IBM Certified Solution Developer WebSphere Message Broker V6.0
IBM Certified System Administrator WebSphere MQ V6.0 |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Dec 26, 2008 4:11 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| satya2481 wrote: |
Where can I get all the MB Java API documentation. I have checked in the IBM V6.1 Information center, Document list etc bu no luck. If anyone provide me the link it would be of great help.
|
You might want to have a look here and here
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| satya2481 |
| Posted: Fri Dec 26, 2008 8:07 am Post subject: |
|
|
Disciple
Joined: 26 Apr 2007
Posts: 170
Location: Bengaluru
|
Hi,
Thank you for your reply. I have gone through these links. But I am actually searching for all the MB Java APIs. Some thing similar to Sun java API documentation.
I need to create an out going message MRM XML Domain. The output message should contain the Default namespace, I would like to know how to create this default namespace using Java in Message broker JCNode. Apart from this I want to know how to create the Encoding part in the output XML message <?xml version="1.0" encoding="UTF-8"?>
Thank You
Satya
_________________
IBM Certified Solution Developer WebSphere Message Broker V6.0
IBM Certified System Administrator WebSphere MQ V6.0 |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Fri Dec 26, 2008 4:20 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
The Javadocs for the WMB Java API are here.
But it's the MRM parser, not the Java API, that normally handles the XML and namespace declarations, using the given message set definitions, and message headers.
You might consider using the XMLNSC parser instead.
| satya2481 wrote: |
- Unzip the file which contained all the OAGIS and custom schemas
- Check the dependencies on the schemas and import one by one from Bottom up approach.
- I have tried to use the "mqsicreatemsgdefs" toolkit command to create the message definitions but it didn't succeed to create the definitions by resolving the dependent schemas automatically
- Now I have left with 2 issues:
- Unable to resolve the basetype for one of the complex element. I have manually tried to locate the derived base type and tried to add but when I click on the OK button after selecting the basetype the toolkit shows progress and will not complete.
- Unable to locate one of the element references.
|
Why are you using the "mqsicreatemsgdefs" from the command-line, instead of using the toolkit? Can you be more specific about how it "didn't succeed"? Did the command generate any errors? If so, what were they?
For both the unresolved base type, and the "unable to locate" element reference, did you check that they are actually defined in the XML schemas? Did you check that they were imported into your message definitions? Does the toolkit indicate any errors in the message set project?
When you tried to add the derived basetype, and said that the toolkit "will not complete", what does that mean? Does the toolkit generate an error, or does it hang, or does it just take a really long time before you kill it? Are there any error messages generated in the <workspace>/.metadata/.log file? |
|
| Back to top |
|
|
| satya2481 |
| Posted: Fri Dec 26, 2008 11:32 pm Post subject: |
|
|
Disciple
Joined: 26 Apr 2007
Posts: 170
Location: Bengaluru
|
Hi rekrm01,
Thank you for your reply...
I have to parse the message against the MRM - XML message set with content and value validation. I am trying to create the message set in MRM - XML Physical format.
The main reason why I am using "mqsicreatemsgdefs" toolkit command is that it checks the dependent schemas and creates the message definition automatically. I have read about this in one of the article.
When I create the message defintion from the toolkit it is not able to resolve the dependent schemas, I will have to manually import one by one schemas. Same thing happens even when I use the mqsicreatemsgdefs command.
In the toolkit I have followed bottom up approach to create the message definition.
Below are the exact errors i am getting in the toolkit.
1. Element reference 'http://www.openapplications.org/oagis/9#Sync' cannot be resolved
2. Type 'SyncPurchaseOrderType' has an unresolved base type 'http://www.openapplications.org/oagis/9#BusinessObjectDocumentType'
I dont know how to resolve the issue No 1. But issue 2 I have tried to resolve. According the error message when I have checked the "SyncPurchaseOrderType" properties --> BaseType there is no basetype BuinessObjectDocumentType referenced. I have tried to add it manually. By selecting more option. It opened a new window "Type Selection", I can see and browse the BusinessObjectDocumentType under the list. But when I select this and click on OK button the toolkit will show a progress and then it will not come out. It says "Adding Message definition" and will not progress... no errors also.
I getting below message in the <WMBWorkspace>/.metadata/.log file
| Code: |
!ENTRY org.eclipse.ui 4 4 2008-12-27 13:00:36.875
!MESSAGE Unhandled event loop exception
!ENTRY org.eclipse.ui 4 0 2008-12-27 13:00:36.875
!MESSAGE The default prefix should represented as null rather than as a zero length String
!STACK 0
java.lang.IllegalArgumentException: The default prefix should represented as null rather than as a zero length String
at org.eclipse.xsd.impl.XSDSchemaImpl$1.put(Unknown Source)
at com.ibm.etools.msg.editor.actions.dialogs.NamedComponentSelectionDialog.addImportOrInclude(Unknown Source)
at com.ibm.etools.msg.editor.actions.dialogs.NamedComponentSelectionDialog.okPressed(Unknown Source)
at org.eclipse.jface.dialogs.Dialog.buttonPressed(Unknown Source)
at org.eclipse.ui.dialogs.TwoPaneElementSelector.handleDefaultSelected(Unknown Source)
at org.eclipse.ui.dialogs.AbstractElementListSelectionDialog$1.widgetDefaultSelected(Unknown Source)
at org.eclipse.swt.widgets.TypedListener.handleEvent(Unknown Source)
at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)
at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
at org.eclipse.jface.window.Window.runEventLoop(Unknown Source)
at org.eclipse.jface.window.Window.open(Unknown Source)
at org.eclipse.ui.dialogs.AbstractElementListSelectionDialog.open(Unknown Source)
at com.ibm.etools.msg.editor.actions.dialogs.NamedComponentSelectionDialog.open(Unknown Source)
at com.ibm.etools.msg.editor.properties.editors.custom.TypeSelectionFieldEditor.widgetSelected(Unknown Source)
at org.eclipse.swt.widgets.TypedListener.handleEvent(Unknown Source)
at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Display.runDeferredEvents(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)
!ENTRY org.eclipse.ui 4 4 2008-12-27 13:00:39.578
!MESSAGE Unhandled event loop exception
!ENTRY org.eclipse.ui 4 0 2008-12-27 13:00:39.578
!MESSAGE The default prefix should represented as null rather than as a zero length String
!STACK 0
java.lang.IllegalArgumentException: The default prefix should represented as null rather than as a zero length String
at org.eclipse.xsd.impl.XSDSchemaImpl$1.put(Unknown Source)
at com.ibm.etools.msg.editor.actions.dialogs.NamedComponentSelectionDialog.addImportOrInclude(Unknown Source)
at com.ibm.etools.msg.editor.actions.dialogs.NamedComponentSelectionDialog.okPressed(Unknown Source)
at org.eclipse.jface.dialogs.Dialog.buttonPressed(Unknown Source)
at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Unknown Source)
at org.eclipse.swt.widgets.TypedListener.handleEvent(Unknown Source)
at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)
at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
at org.eclipse.jface.window.Window.runEventLoop(Unknown Source)
at org.eclipse.jface.window.Window.open(Unknown Source)
at org.eclipse.ui.dialogs.AbstractElementListSelectionDialog.open(Unknown Source)
at com.ibm.etools.msg.editor.actions.dialogs.NamedComponentSelectionDialog.open(Unknown Source)
at com.ibm.etools.msg.editor.properties.editors.custom.TypeSelectionFieldEditor.widgetSelected(Unknown Source)
at org.eclipse.swt.widgets.TypedListener.handleEvent(Unknown Source)
at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
at org.eclipse.swt.widgets.Display.runDeferredEvents(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)
|
Your suggessions on how to resolve this error are much appreciated.
Thank You
Satya
_________________
IBM Certified Solution Developer WebSphere Message Broker V6.0
IBM Certified System Administrator WebSphere MQ V6.0 |
|
| Back to top |
|
|
| satya2481 |
| Posted: Sat Dec 27, 2008 6:38 am Post subject: Issue with the Base type resolving resolved |
|
|
Disciple
Joined: 26 Apr 2007
Posts: 170
Location: Bengaluru
|
Hi All,
The Issue with the message set resolved. 
I have followed below steps to resolve the above mentioned issues with the message definition.
1. Check the namespace prefix used in the schema for the elements which are giving an issue. In my case it was "oa".
2. Check whether this namespace prefix is listed and present in the messageset.mset --> Properties --> Namespace Declarations.
In my case the namespace URI was present but no prefix, I have added it manually.
3. Click on the *.mxsd file which is giving an issue. My case SyncPurchaseOrder.mxsd
4. Right click and go to properties (You can select the properties tab directly). Click on the "Imports" and select Add Import link in the Details section. Browse and select the schema where in the base type is defined.
5. Check whether the issues are resolved automatically or not. If not try to browse the base type and add it manually.
Thank you very much to all of you.
Regards
Satya
_________________
IBM Certified Solution Developer WebSphere Message Broker V6.0
IBM Certified System Administrator WebSphere MQ V6.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
|
|
|
|
