on 10-27-2007 2:06 PM
Hi
We have a dump of an application developed in NWDS,which connects to MDM Repositories.The application used to run(1 Year back).Initially we got the error "a2i unresolved" which is fixed after we deleted the old JAR and added new compatible MDM4j.jar.
We still get the following errors, we are not able to understand why.
For PRJ_REQUEST_RESOURCE_INPUT-
java.lang.NullPointerException
java.lang.IllegalArgumentException: Table Client Projects does not exist.
at com.a2i.xcat.internal.SubTableCache.GetTableCache(Unknown Source)
at a2i.common.CatalogData.GetDistinctValues(Unknown Source)
at com.satyam.rf.co.CO_Request_Resource_Input.populateDropDown(CO_Request_Resource_Input.java:1413)
at com.satyam.rf.co.wdp.InternalCO_Request_Resource_Input.populateDropDown(InternalCO_Request_Resource_Input.java:313)
at com.satyam.rf.co.CO_Request_Resource_Input.initialise(CO_Request_Resource_Input.java:2211)
at com.satyam.rf.co.wdp.InternalCO_Request_Resource_Input.initialise(InternalCO_Request_Resource_Input.java:357)
at com.satyam.rf.co.CO_Request_Resource_Input.wdDoInit(CO_Request_Resource_Input.java:175)
at com.satyam.rf.co.wdp.InternalCO_Request_Resource_Input.wdDoInit(InternalCO_Request_Resource_Input.java:257)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:347)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:370)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
-
For PRJ_RESOURCE AVAIABILITY CHECK :
java.lang.NullPointerException
at com.satyam.rf.rac.view.VW_Skill_Matrix.wdDoInit(VW_Skill_Matrix.java:111)
at com.satyam.rf.rac.view.wdp.InternalVW_Skill_Matrix.wdDoInit(InternalVW_Skill_Matrix.java:192)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:274)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:555)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:135)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:392)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
But the tables 'skill matrices' and 'client projects' actually exist on the server.
Please Help.
Thanks in advance.
Swetha
Hi Swetha,
If you had developed this application a yr back, it is quite possible that you had put Table NAMES into the code. Current versions of APIs expect TABLE CODE as arguments instead of Names.
Most probably this would be the problem. Please check!.
Thanks,
Mausam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mausam/Walter
That application is not developed by me(I am new to the EP), the person who developed it is not accessible now.
The MDM server version is 5.5 SP04, and we also tried it with the code names with _(underscores) instead if spaces.It is being considered to upgrade it to SP05,but before that, I have to make this application run.
Along with the table not found exceptin , we aso get other errors which are :
Error getting values from the table :Authorization.error : a2i.core.StringException:Buildquery error
Error while reading records from the table Skills.Error :a2i.core.stringexception:Sort field Skill name not found in the table skills.
Thanks & Regards
Swetha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Swetha,
The exceptions you are getting further confirm that the hard-coded code names in your original application no longer conform to the code names as displayed in the MDM Console.
You will need to locate where the code names are being defined (eg. application source code, Portal Content Directory) and update them accordingly.
Regards,
Walter
Hi
Thank you for responding.I have tried checking that and we are using table codes only not the table names.Can u please tell me where can we find the API version of our code and how do we upgrade it to the current version.
Thanks and Regards
Swetha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
You don't say which version of MDM Server you are using, but I suggest cross-checking hard-coded CODE references in your WD code, to the codes in the MDM Console. Pay particular care to code names with spaces in them, since older repositories which are updated to 5.5 SP5 will now show underscores instead of spaces in the code names.
For example, if a code name was previously "Part Number", it will now be "Part_Number", and you need to update your WD application accordingly.
Walter
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.