Solved: Data type restriction on context nodes attributes

Hi every body!

I'm facing a problem working with a context node in a component controller that have an atribute of type java.io.Serializable. Whenever I try to access this atribute a got a nullPointerException.

Is there any restriction on the data types that i can use for an attribute?

Regards

Jose Arango

SAP Managed Tags:
UI Web Dynpro Java

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Hi Jose,

Refer to the following threads which might help you.

Thanks n Regards,

Jhansi Miryala

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Answers (2)

Hi,

try out the following code and let me know if you still get null pointer exception:

if(wdContext.nodeReqFind().size>0)

{

wdContext.currentReqFindElement().setId("<any string >");

}

regards,

amit bagati

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Amit:

Thanks for your response. What you are suggesting me would solve the problem and I won't get the nullPointerException, but how can I access this attribute? If whenever I try to access it I get the exception.

Regards

Jose Arango.

Hi jose

have you solved your issue??

in my case it works fine with your code. ie by accessing the element of node(cardinality 1,1) as wdContext.current<node_Name>Element().set<attribute_Name>(value);

also you can try it this way

wdContext.node<node_Name>.getElementAt(0).getAttributeValue('<attribute_Name>","value");

Deepak

Did you initialize that object?

nikhiL

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi nikhiL:

Yes, I have initialized the object. This is my scenario.

In my controller context i have these nodes and both have 1..1 cardinality.

Find

id (String)

ReqFind

Response

Return (java.io.Serializable)

id (java.io.Serializable)

type (java.lang.Class)

The ReqFind node is bind to an EJB model.

In the wdDoInit i have the following code.

CrudModel modelo = new CrudModel();

ReqFind req = new ReqFind(modelo);

wdContext.nodeReqFind().addElement(req);

wdContext.currentFindElement().setId("HW300");

wdContext.currentReqFindElement().setId(wdContext.currentFindElement().getId());

And when execute the app I got a nullPointerException where I set the id attribute for the ReqFind node.

Hi Jose,

Comment code line wdContext.currentFindElement().setId("HW300");

and try

wdContext.currentReqFindElement().setId("HW300");

instead of

wdContext.currentReqFindElement().setId(wdContext.currentFindElement().getId());

Regards,

Gopal

Hi Gopal:

I've alredy done that and got the same exception.

Regards,

Jose.

Hi Jose,

Can you display whole stack trace here in this thread?

Regards,

Gopal

Hi Gopal:

This is the detail error information.

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session ApplicationSession(name=com.sap.demo.course.courseapp.CourseApp, id=508a4d601dda11ddcac50002554f6621). The causing exception is nested. RID=5080b0701dda11dda0b80002554f6621

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:650)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:225)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:231)

at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:205)

at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)

at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)

at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)

at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)

at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:93)

at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:105)

at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)

at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:54)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)

at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)