com.dwl.base.requestHandler.exception.RequestParserException: [Exception_myErrorHandler_SAXParseError:] The parsing of the XML failed at the following position

I had did an extension on the grouping table to add XMyExtId .
When I ran the addGrouping trasaction with the extended field I got the following response.

Parser DWLTransaction failed. The format of the message is not correct or an application error occurred.
com.dwl.base.requestHandler.exception.RequestParserException: [Exception_myErrorHandler_SAXParseError:] The parsing of the XML failed at the following position. XML = org.xml.sax.SAXParseException: Element type "XMyExtId" must not be declared more than once.; line number = 64; column number = 34


The reason being I had already done an entity addition which is having the attribute XMyExtId .Even if entries for grouping extension goes to DWLrequest_extesnion.dtd & repsonse ,during the parsing it still looks at the trcrmrequest_extsnsion.dtd(I dont know the reason for that) whcih is having the entry XMyExtId for my addition  I did earlier.

Solution:

Just rename the attribute XMyExtId you used for extension or else you can utilize the old deceleration for XMyExtId by commenting out the current one.

javax.naming.NamingException:

This one is not a pure MDM error but a simple EJB error.I was trying to create a HelloWorld EJB & run it.

Jul 15, 2010 12:30:26 PM com.ibm.ws.util.ImplFactory

WARNING: WSVR0073W

Exception in thread "P=225643:O=0:CT" javax.naming.NamingException: Failed to initialize the ORB [Root exception is org.omg.CORBA.INITIALIZE: Unable to init plugins  vmcid: IBM  minor code: 504  completed: No]

      at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:318)

      at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:392)

      at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:117)

      at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:712)

      at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:171)

      at javax.naming.InitialContext.lookup(InitialContext.java:363)

      at com.ust.client.ClientEJB.main(ClientEJB.java:13)

Caused by: org.omg.CORBA.INITIALIZE: Unable to init plugins  vmcid: IBM  minor code: 504  completed: No

      at com.ibm.rmi.corba.PluginRegistry.initPlugin(PluginRegistry.java:229)

      at com.ibm.rmi.corba.PluginRegistry.initPlugins(PluginRegistry.java:210)

      at com.ibm.rmi.corba.PluginRegistry.initPlugins(PluginRegistry.java:216)

      at com.ibm.rmi.corba.ORB.initializePlugins(ORB.java:571)

      at com.ibm.rmi.corba.ORB.orbParameters(ORB.java:1319)

      at com.ibm.rmi.corba.ORB.set_parameters(ORB.java:1206)

      at com.ibm.CORBA.iiop.ORB.set_parameters(ORB.java:1662)

      at org.omg.CORBA.ORB.init(ORB.java:364)

      at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:86)

      at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)

      at com.ibm.ejs.oa.EJSClientORBImpl.(EJSClientORBImpl.java:83)

      at com.ibm.ejs.oa.EJSClientORBImpl.(EJSClientORBImpl.java:59)

      at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:102)

      at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:309)

      ... 6 more

Caused by: java.lang.NoClassDefFoundError: Invalid Implementation Key, com.ibm.CORBA.iiop.WLMPlugin

      at com.ibm.ws.util.ImplFactory.loadClassFromKey(ImplFactory.java:363)

      at com.ibm.ws.util.ImplFactory.loadClassFromKey(ImplFactory.java:354)

      at com.ibm.ws.wlm.Factory$2.run(Factory.java:98)

      at java.security.AccessController.doPrivileged(AccessController.java:241)

      at com.ibm.ws.wlm.Factory.loadClass(Factory.java:96)

      at com.ibm.ws.wlm.client.WLMClient.init(WLMClient.java:130)

      at com.ibm.rmi.corba.PluginRegistry.initPlugin(PluginRegistry.java:224)

      ... 19 more

Solution:

Add com.ibm.ws.webservices.thinclient_6.1.0.jar & com.ibm.ws.admin.client_6.1.0.jar to your client project & run again .

StackOverflowError during code generation in MDM Workbench

I had created a new module project ,did some extensions on it & was trying to generate code.
I got java.lang.StackOverflowError during the code generation.

 Solution:

I had added my module project in the J2EE module dependencies for DWLCommonServices project.Just uncheck that generate the code again.

First component in name DWLServiceController not found.

com/dwl/base/requestHandler/beans/DWLServiceController: First component in name DWLServiceController not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]

Solution:
You MDM is not deployed properly & started.Restart it from admin console.

Multiple ConfigurationWarning exceptions encountered

Exception stacktrace as found in the SystemErr.log:

SystemErr     R com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.exception.ConfigurationWarning: Multiple ConfigurationWarning exceptions encountered
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:509)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:149)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:408)
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:187)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:133)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:387)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:53)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219)
at java.lang.Thread.run(Thread.java:570)
Caused by: com.ibm.ws.exception.ConfigurationWarning: Multiple ConfigurationWarning exceptions encountered
at com.ibm.ws.runtime.component.ApplicationMgrImpl.initializeApplications(ApplicationMgrImpl.java:699)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.initializeApplications(ApplicationMgrImpl.java:565)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:507)
... 17 more
Caused by: com.ibm.ws.exception.ConfigurationWarning: Module not found
at 




Solution:


Stop your WAS.
From Add/Remove Projects remove your MDM project.
Publish the server so that it uninstall-ed the application.
During publish also you may get the same error, don't bother about that.


Make sure from admin console MDM is removed.


Stop the server again.
Do a  clean build.
Add/Remove add the MDM project.
Restart/Publish the server.Hopefully it will work. :)

The WSDL2Java emitter has found relative namespace

[6/30/10 15:30:55:903 IST] 0000000e SystemErr     R WSWS3457W: Warning:
 The WSDL2Java emitter has found relative namespace www.mycompany.com/xmdmcustomsearchframework/port in the
 WSDL, and cannot transform it to an absolute namespace.

Solution:
Try putting an http:// in front of the Webservice name space URI in the module project.

Exception_DWLDocumentHandlerHelper_CannotCreateInstance:

I am doing a person extension called XPerson. I am getting the below error.
the tcrm_extension has the following entry

XPersonBObjExt = com.comp.test.component

com.dwl.base.requestHandler.exception.RequestParserException: Exception_DWLDocumentHandlerHelper_CannotCreateInstance: The object cannot be created with the following parameters. XML element name = XPersonBObjExt; class = XPersonBObjExt


Solution:
I had taken it from developer works but this is an erro that we used to get frequently.


The error message you are getting indicates that the XPersonBObjExt class could not be instantiated. The most likely causes are:

• the tcrm_extension.properties file that you edited is not being loaded by the server because it is not on the server classpath(Check in admin console-classpath)Application servers > server1 > Process Definition > Java Virtual Machine
• Look in class path u r properties file is there in the correct path.
• 
  
• the package name you put in tcrm_extension.properties is incorrect
• the class does not exist - check the .class file exists
• the class is not deployed - check that the module containing the class is included in the MDM application and the MDM application has been published to the server
• the class is not loadable by the request-response framework - check that the module that contains it is in the J2EE dependencies of PartyEJB or DWLCommonServicesEJB