on 07-03-2008 3:38 PM
Team,
I am getting the below error.
I am trying to use other DC as Used DC and calling one of the method of used DC.
When click on the button , where I am calling that method I am getting the below error.
Can one help?
com.sap.tc.webdynpro.progmodel.context.ContextException: DataNodeInfo(<unknown>): the controller has already been destroyed
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.getContextInternal(NodeInfo.java:273)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.createElement(NodeInfo.java:859)
at com.sap.tc.webdynpro.progmodel.context.Node.createElementInternal(Node.java:1348)
at com.sap.tc.webdynpro.progmodel.context.Node.doSupplyElements(Node.java:451)
at com.sap.tc.webdynpro.progmodel.context.Node.supplyElements(Node.java:403)
... 33 more
REgards,
Bala
check context mapping between current DC and other DCs are valid and not broken.
or post complete stack trace.
nikhil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nikhil,
Just to test it once again, I have just created another DC which is not having any context node at all.
Just a simple button with action on it to call the method of Used DC.
I followed the below prcedure.
) Added generalsearch DC from Inactive DCu2019s in DC Meta Data
2) In method searchKey of CompController
if(!wdThis.wdGetGeneralSearchComponentUsage().hasActiveComponent()){
wdThis.wdGetGeneralSearchComponentUsage().createComponent();
}
wdThis.wdGetGeneralSearchInterface().doSearchHelp_ss("Z_KOSTL",true,300,200);
3) Trying read result using another event handler method for general search and printing the resultant value.
I am getting that error.
Below is the complete stack trace.
com.sap.tc.webdynpro.progmodel.context.ContextException: DataNodeInfo(<unknown>): the controller has already been destroyed
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.getContextInternal(NodeInfo.java:273)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.createElement(NodeInfo.java:859)
at com.sap.tc.webdynpro.progmodel.context.Node.createElementInternal(Node.java:1348)
at com.sap.tc.webdynpro.progmodel.context.Node.doSupplyElements(Node.java:451)
at com.sap.tc.webdynpro.progmodel.context.Node.supplyElements(Node.java:403)
at com.sap.tc.webdynpro.progmodel.context.Node.getElementList(Node.java:346)
at com.sap.tc.webdynpro.progmodel.context.Node.getElements(Node.java:334)
at com.sap.tc.webdynpro.progmodel.context.Node.getElementAtInternal(Node.java:612)
at com.sap.tc.webdynpro.progmodel.context.Node.getCurrentElementInternal(Node.java:865)
at com.sap.tc.webdynpro.progmodel.context.Node.getCurrentElement(Node.java:872)
at com.capita.util.generalsearch.apps.wdp.IPrivateSearchView$IContextNode.currentContextElement(IPrivateSearchView.java:130)
at com.capita.util.generalsearch.apps.SearchView.onPlugFromStart(SearchView.java:600)
at com.capita.util.generalsearch.apps.wdp.InternalSearchView.wdInvokeEventHandler(InternalSearchView.java:297)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:857)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:359)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
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.doPost(DispatcherServlet.java:55)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Can you please help?
Regards,
Bala
HI Fazal,
I am getting the same old error.
I am removed it and created as manual.
The below is the code Which I wrote.
if(!wdThis.wdGetGeneralSearchComponentUsage().hasActiveComponent()){
wdThis.wdGetGeneralSearchComponentUsage().createComponent();
}
wdThis.wdGetGeneralSearchInterface().doSearchHelp_ss("ZH_BANKL",true,300,200);
Please help me, its urgent.
REgards,
Bala
hi,
try in this way
wdThis.wdGetGeneralSearchComponentUsage().deleteComponent();
wdThis.wdGetGeneralSearchComponentUsage().createComponent();
wdThis.wdGetGeneralSearchInterface().doSearchHelp_ss("ZH_BANKL",true,300,200);
remove the if condition loop .
before creating the component , first delete the component and create a new one .
try and initmate me on the same
thanks and regards
Hi,
What is dependancy type?
Design Time , Build Time ,Deploy Time , Run Time ?
Check if it is correct.
Regards,
Apurva
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi ,
if possible give some more inputs on ur requirements .
thanks and regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Fazal,
Thank you very much for your reply.
I am getting the same old error even after writing your suggested code.
My requirement is.
There is one common DC for searching Org Units.
Every one will use this DC for search Org Unit.
When I am trying use this DC, i am getting that error.
Othere people also using this DC, bu they are not getting any errors.
I am not doing any thing much in my DC also.
No Context, nothing.
I wrote simply one action on button and calling that method.
When click on it, it gives me the error.
Can you please help me on this ?
It's very urgent for me.
Regards,
Bala
HI Fazal,
Declaring public part and all done by other person who has developed that common DC.
I am just using it.
What do u mean by adding in dependencies?
In Dc meta data, in used DC's we add it.
and in Used WebDynpro Componets we add it.
I wrote one Event handler, to capture the value of return data, when I call that method.
And i am just printing it.
It is giving me that error.
Regards,
Bala
Hi
According to your stack trace, i think there is some problem with node name which you are creating.
In third line of trace i.e
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.createElement(NodeInfo.java:859)
i think you are creating an element of wrong node.Mean to say that you are creating element of node and by mistake you had given wrong name
just check it and do as specified by nikhil.
Mandeep Virk
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
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.