Exception in initialize javax.naming.NameNotFoundException: Context:

Error:
Exception in initialize javax.naming.NameNotFoundException: Context: MachineNode07Cell/nodes/MachineNode07/servers/server1, name: com/dwl/base/requestHandler/beans/DWLServiceController: First component in name requestHandler/beans/DWLServiceController not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0
Error in testRequestMethod :java.lang.NullPointerException

The only reason for this error is your MDM is not properly deployed.
Solution:
Try Add/Remove MDM from WAS.

Exception occurred when processing the following attribute and object. Attrbiute = ComponentID; object =com.mycompany.XContract ,Wrong Number of Arguments.

Exception occurred when processing the following attribute and object.  Attrbiute = ComponentID; object =com.mycompany.XContract ,Wrong Number  of Arguments.

Easy fix:Remove the ComponentID from tcrmresponse_extension.dtd for the object mentioned in the error.

Once it is removed , you may get the same error with  Attrbiute = ObjectReferenceID & again with DWLStatus.

This will solve the problem.

Alternate

Please regenerate the code for module project you used for  any extensions & redeploy.

BTM ITxRTx Exception : Exception in Request Response Framework

The exception may occur while executing  Composite Service Transaction.
Solution:
Add your Composite Transaction project to the dependencies of
1)DWLCommonServicesEJB's MANIFEST.
2)Add  Base.jar , BTM.jar, CommonUtilities.jar, ConfigurationClient.jar, ConfigurationRepository.jar, CoreUtilities.jar, DWLCommonServices.jar, Logging.jar, ManagementCommon.jar, Services.jar,  icu4j.jar - ManagementAgent/lib

javaAccessorNotSet Exception in thread "main" java.lang.NoClassDefFoundError:

SEVERE:javaAccessorNotSet  Exception in thread "main" java.lang.NoClassDefFoundError: org.eclipse.core.runtime.CoreException
Solution:
Add C:\IBM\SDP70\runtimes\base_v61\runtimes\com.ibm.ws.webservices.thinclient_6.1.0.jar to the project

java.lang.StackOverFlow error

Stack Over flow error is commonly seen while generating the code  after performing some extension / additions.

Solution:
Remove the dependencaies from DWLCommonServices / DWLCommonServicesEJB & try generating the code.

java.lang.NoSuchMethodError: com/sun/xml/xsom/XSFacet.getValue()Ljava/lang/String;

One common error we used to get while setting up the MDM workspace.

Problem:

[Error_Shared_DatabaseProperties:] Error occurred when retrieving database

java.lang.NoSuchMethodError: com/sun/xml/xsom/XSFacet.getValue()Ljava/lang/String;

Solution:

You need to uninstall the runtime completely and reinstall it without the web services feature pack to fix the problem. (Simply uninstalling the feature pack may not work.)

Reference:

http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14290606;bcsi-ac-CEB65C2292F41211=1BD0A26D00000005MpqhV46kRGRgZy2AwTQSvDGb+EcJAAAABQAAABeIcACgjAAAAAAAAEQSAAA=

READERR 796: Search for the following failed: Party

I was trying to invoke a searchFSParty from my finder class .

TCRMFSPersonSearchBObj fspersonsearch=new TCRMFSPersonSearchBObj();
fspersonsearch.setLastName("tintumon");
try {
TCRMResponse tcrmReps=new TCRMFinancialFinder().searchFSParty(fspersonsearch);
TCRMPersonSearchResultBObj perSearchResult=(TCRMPersonSearchResultBObj)tcrmReps.getData();

} catch (Exception e1) {
// TODO Auto-generated catch block
e1.printStackTrace();
}

It was giving me ERROR - 10 READERR 796: Search for the following failed: Party
Same the case with TCRMCorePartyFinder.

But I am able to invoke a getContract()
new TCRMFinancialFinder().getContract(contractId, "1", "1", control);
successfuly inside the same class.

Solution:

The reason being  I had'nt set the control to fspersonsearch.

TCRMFSPersonSearchBObj fspersonsearch=new TCRMFSPersonSearchBObj();
fspersonsearch.setLastName("Darnell");
fspersonsearch.setControl(theBObj.getControl());
try {
TCRMResponse tcrmReps=new TCRMFinancialFinder().searchFSParty(fspersonsearch);
Vector perSearchResultVect=(Vector)tcrmReps.getData();
TCRMPersonSearchResultBObj perSearchResult= (TCRMPersonSearchResultBObj) perSearchResultVect.get(0);
System.out.println("Given name---"+perSearchResult.getGivenNameOne());

https://www.ibm.com/developerworks/forums/thread.jspa?threadID=336548&tstart=0

Error_Application_NotFindDeployment

Problem:
IST] 00000011 SystemOut     O ERROR     - Error_Application_NotFindDeployment
[8/10/10 11:54:12:043 IST] 00000011 SystemOut     O ERROR     - Exception_Application_NotFindDeployment
[8/10/10 11:54:12:043 IST] 00000011 SystemOut     O ERROR     - Error_Application_NotFindDeployment
[8/10/10 11:54:12:043 IST] 00000011 SystemOut     O ERROR     - Error_Application_NotFindDeployment
[8/10/10 11:54:12:043 IST] 00000011 SystemOut     O ERROR     - com.dwl.management.config.repository.ElementNotFoundException: Exception_Application_NotFindDeployment
[8/10/10 11:54:12:043 IST] 00000011 SystemOut     O INFO      - ###########################
[8/10/10 11:54:12:043 IST] 00000011 SystemOut     O INFO      - DWLServiceController : processRequest : total time in milliseconds 0
[8/10/10 11:54:12:043 IST] 00000011 SystemOut     O INFO      - ###########################
[8/10/10 11:54:12:089 IST] 00000011 SystemOut     O ERROR     - Error_Application_NotFindDeployment
[8/10/10 11:54:12:089 IST] 00000011 SystemOut     O ERROR     - Exception_Application_NotFindDeployment
[8/10/10 11:54:12:089 IST] 00000011 SystemOut     O ERROR     - Error_Application_NotFindDeployment
[8/10/10 11:54:12:089 IST] 00000011 SystemOut     O ERROR     - Error_Application_NotFindDeployment
Solution:
Check whether the deployment name in APPDEPLOYMENT table matches  the one in the bootstrap.properties.(Customer resources ->properties->config)

Cannot load security.xml file since the file is empty while starting RSA.

Solution:http://www-01.ibm.com/support/docview.wss?uid=swg1PK67688

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

Errors logged during code generation- Failed to generate code for interface

I had done an entity addition and was trying to generate code after a successful model validation.
( The same sort of  error I got during an extension.)

Errors logged during code generation
  Failed to generate code for interface com.mycompany.mdm.entityObject.EObjXSearchRequestData due to exception: com.ibm.pdq.tools.exception.GenerationException: Cannot resolve binding for method /**
 *
 *
 * Select XSearchRequest by parameters.
 * @generated
 */
@Select(sql=getEObjXSearchRequestSql) @EntityMapping(parameters=EObjXSearchRequestKeyField,results=EObjXSearchRequestAllFields) Iterator getEObjXSearchRequest(Long pkName);
.
  Possibly a classpath issue.

Solution:
Go to your module project ->properties -> java build path ->Libraries->remove the JRE system library & add it again .:)

!MESSAGE Could not publish to the server.

When I start my server & try publishing it  I got the following error.When I opened the application.xml of MDM(inside META-INF),it says an unexpected error occurred.



!MESSAGE Could not publish to the server.
!STACK 0
java.lang.NullPointerException
    at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource(Unknown Source)
    at org.eclipse.jem.internal.util.emf.workbench.ProjectResourceSetImpl.getResource(Unknown Source)
    at org.eclipse.wst.common.internal.emfworkbench.WorkbenchResourceHelper.getOrCreateResource(Unknown Source)
    at org.eclipse.wst.common.internal.emfworkbench.integration.EditModel.getResource(Unknown Source)
    at org.eclipse.wst.common.componentcore.internal.ArtifactEditModel.getResource(Unknown Source)
    at org.eclipse.jst.j2ee.componentcore.util.EARArtifactEdit.getDeploymentDescriptorResource(Unknown Source)
    at org.eclipse.jst.j2ee.componentcore.EnterpriseArtifactEdit.getDeploymentDescriptorRoot(Unknown Source)
    at org.eclipse.jst.j2ee.componentcore.util.EARArtifactEdit.getApplication(Unknown Source)
    at org.eclipse.jst.j2ee.internal.deployables.J2EEFlexProjDeployable.isNestedJ2EEModule(Unknown Source)
    at org.eclipse.jst.j2ee.internal.deployables.J2EEFlexProjDeployable.shouldIncludeUtilityComponent(Unknown Source)
    at org.eclipse.wst.web.internal.deployables.ComponentDeployable.addUtilMembers(Unknown Source)
    at org.eclipse.jst.j2ee.internal.deployables.J2EEFlexProjDeployable.members(Unknown Source)
    at org.eclipse.wst.server.core.internal.ModulePublishInfo.fillCache(Unknown Source)
    at org.eclipse.wst.server.core.internal.ModulePublishInfo.getDelta(Unknown Source)
    at org.eclipse.wst.server.core.internal.ServerPublishInfo.getDelta(Unknown Source)
    at org.eclipse.wst.server.core.internal.Server.getPublishedResourceDelta(Unknown Source)
    at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.getPublishedResourceDelta(Unknown Source)
    at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(Unknown Source)
    at org.eclipse.wst.server.core.internal.Server.doPublish(Unknown Source)
    at org.eclipse.wst.server.core.internal.Server.publish(Unknown Source)
    at org.eclipse.wst.server.core.internal.PublishServerJob.run(Unknown Source)
    at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)

Solution:
I dont know the exact reason for the error but the simple solution is to close & reopen the workspace :)

Composite transactions

BTM ITxRTx Exception : Exception in Request Response Framework
Solution:

1)Add your Composite Transaction project to the dependencies of DWLCommonServicesEJB's MANIFEST. 2)Add                                     Base.jar ,                              BTM.jar,              CommonUtilities.jar, ConfigurationClient.jar, ConfigurationRepository.jar, CoreUtilities.jar, DWLCommonServices.jar, Logging.jar, ManagementCommon.jar, Services.jar,                          icu4j.jar - ManagementAgent/lib

Problem occurred while publishing the server

Error messages were issued.     java.io.IOException: FATAL ERRORS encountered by WSDL2Java tool.     at com.ibm.ws.webservices.wsdl.Parser.generate(Unknown Source)     at com.ibm.ws.webservices.wsdl.Parser.generate(Unknown Source)     at com.ibm.ws.webservices.tools.wsad.WSDL2Java._execute(Unknown Source)     at com.ibm.ws.webservices.tools.wsad.WSDL2JavaBase.execute(Unknown Source)     at com.ibm.etools.webservice.command.adapter.CommandToCommand.execute(Unknown Source)     at com.ibm.ast.ws.v61.consumption.j2ee14.stub.WSDeployStub.execute(Unknown Source)     at sun.reflect.GeneratedMethodAccessor31.invoke(Unknown Source)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)     at java.lang.reflect.Method.invoke(Unknown Source)     at com.ibm.ast.ws.v61.consumption.j2ee14.command.AbstractEmitterAdapterCommand.execute(Unknown Source)     at com.ibm.ast.ws.deployer.WASV61DeploymentModule.generateDeploymentCode(Unknown Source)     at com.ibm.etools.webservice.deploy.core.AbstractDeploymentModule.deploy(Unknown Source)     at com.ibm.etools.webservice.deploy.core.AbstractDeploymentModule.deployWebservice(Unknown Source)     at com.ibm.etools.webservice.deploy.core.AbstractDeploymentModule.execute(Unknown Source)     at com.ibm.ast.ws.deployer.WASDeploymentModule.execute(Unknown Source)     at com.ibm.ast.ws.deployer.WASDeploy.execute(Unknown Source)     at com.ibm.ast.ws.deployer.WSDeployer.runWSDeploy(Unknown Source)     at com.ibm.ast.ws.deployer.WSDeployer.processModuleComponent(Unknown Source)     at com.ibm.ast.ws.deployer.WSDeployer.execute(Unknown Source)     at org.eclipse.jst.j2ee.internal.deploy.J2EEDeployOperation.deploy(Unknown Source)     at org.eclipse.jst.j2ee.internal.deploy.J2EEDeployOperation.execute(Unknown Source)     at com.ibm.etools.server.task.ejbdeploy.EJBDeployableTask$EJBTaskOperations.execute(Unknown Source)     at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.performTasks(Unknown Source)     at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(Unknown Source)     at org.eclipse.wst.server.core.internal.Server.doPublish(Unknown Source)     at org.eclipse.wst.server.core.internal.Server.publish(Unknown Source)     at org.eclipse.wst.server.core.internal.PublishServerJob.run(Unknown Source)     at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)   WSWS3574E: ---------- FATAL ERRORS ENCOUNTERED ----------   GENERATION OF ARTIFACTS HAS BEEN SUSPENDED.  See messages to follow for more details.   WSWS3528E: ---------- WSDL2Java VALIDATION ERROR ----------   Extension base mismatch between existing Bean and WSDL document.  Existing Bean class: "com.ibm.wcc.financial.service.to.FSPersonSearch"  Extends the following class: com.ibm.wcc.party.service.to.PersonSearch   However the following extension base  is specified in the WSDL document: com.ibm.wcc.party.service.to.PersonSearch   WSWS3528E: ---------- WSDL2Java VALIDATION ERROR ----------   Extension base mismatch between existing Bean and WSDL document.  Existing Bean class: "com.ibm.wcc.financial.service.to.ContractRoleLocationPrivPref"  Extends the following class: com.ibm.wcc.business.service.to.EntityPrivPref   However the following extension base  is specified in the WSDL document: com.ibm.wcc.business.service.to.EntityPrivPref   WSWS3528E: ---------- WSDL2Java VALIDATION ERROR ----------   Extension base mismatch between existing Bean and WSDL document.  Existing Bean class: "com.ibm.wcc.billing.service.to.BillingSummaryValue"  Extends the following class: com.ibm.wcc.business.service.to.MiscValue   However the following extension base  is specified in the WSDL document: com.ibm.wcc.business.service.to.MiscValue   WSWS3528E: ---------- WSDL2Java VALIDATION ERROR ----------   Extension base mismatch between existing Bean and WSDL document.  Existing Bean class: "com.ibm.wcc.financial.service.to.FSOrganizationSearch"  Extends the following class: com.ibm.wcc.party.service.to.OrganizationSearch   However the following extension base  is specified in the WSDL document: com.ibm.wcc.party.service.to.OrganizationSearch   WSWS3528E: ---------- WSDL2Java VALIDATION ERROR ----------   Extension base mismatch between existing Bean and WSDL document.  Existing Bean class: "com.ibm.wcc.financial.service.to.ContractValue"  Extends the following class: com.ibm.wcc.business.service.to.MiscValue   However the following extension base  is specified in the WSDL document: com.ibm.wcc.business.service.to.MiscValue  Solution: Check the J2EE Dependencies (see project Properties) for your WSEJB project and ensure that they  include all the WS projects which it depends on directly or indirectly - this is probably:  PartyWS, FinancialServicesWS, BusinessServicesWS, DWLBusinessServicesWS, DWLCommonServicesWS.  Then try the publish again.

I had made entries about getContractByXXX in tcrm _extension.properties.I had done clean build,add/remove MDM many times.But still I am getting the following error.

com.dwl.base.exception.DWLBaseException: Exception_DWLTxnBP_Exception: The request cannot be processed by the application. Additional error message = Exception_Shared_NoProperty: The property is not defined in the properties file. Property = getContractByXXX

The error message you have indicates that the property "getContractByXXX" was not found. You should add it to tcrm_extension.properties. If you have already done that - and checked the spelling is correct, and have restarted the server - then that would imply the server is not loading the properties files from the right location.


Go in to the WAS admin console, select the server, on the right hand side of the panel find Java and Process Management - Process Definition. On the next page, select Java Virtual Machine. You can edit the classpath if it is not correct.

References/Links:
IBM MDM WorkBench Forum1
IBM MDM WorkBench Forum2

Errors logged during code generation

I had done an extension on Contract table & during the code generation the following errors are logged.

Errors logged during code generation

Failed to generate code for interface com.XXX.mdm.entityObject.EObjXContractExtData due to exception: com.ibm.pdq.tools.exception.GenerationException: Cannot resolve binding for method /**
 *
 *
 * Select XContract by parameters.
 * @generated
 */
@Select(sql=getEObjXContractExtSql) @EntityMapping(parameters=EObjXContractExtKeyField,results=EObjXContractExtAllFields) Iterator getEObjXContractExt(Long pkName);
.
  Possibly a classpath issue.

 
Remove the JRE System library & add it.

Validate the model & regenerate the code.

Appendable Cannot be resolved to a type

This is one error which I encountered immediately after setting up Development environment.
Error:
Appendable Cannot be resolved to a type.I got in projects like BusinessServices,Party etc.

Resolution:

Go to the buildpath of the project which is having this error.
Libraries tab->Remove the JRE system library.

Then click Add Library

Select JRE system library ,Next ->Workspace default finish.

Do the same for each project which is having this compile error.