InputField type decimal and not handled exception problem

[Former Member]

Hello,

My problem is caused by InputField with type decimal (variable from R/3 - type DEC).

Not handled exception appears when I enter letter (something else than digit) in input field. This is in standard SAP WebDynpro codes (see listing below).

Some other types works fine and in case of wrong value, right standard error message for InputField is presented. But not in decimal type case.

I have already checked SAP Notes and posts in this forum - without results.

Maybe somebody already knows this problem and is able to advise me a solution?

I see only one solution - InputField type string and conversion from/to decimal. However this solution requires quite a lot of development in my case (quite complex application with many fields).

Best Regards,

Stanislaw

SAP NetWeaver Developer Studio Version: 2.0.13

J2EE Engine 6.40 patchlevel 89291.313

Detailed Exception Chain

java.lang.NullPointerException

at java.text.DecimalFormat.applyPattern(DecimalFormat.java:2055)

at java.text.DecimalFormat.applyPattern(DecimalFormat.java:1984)

at com.sap.dictionary.runtime.DdTypeNumber.setDecimalExample(DdTypeNumber.java:379)

at com.sap.dictionary.runtime.DdTypeNumber.parseDecimal(DdTypeNumber.java:111)

at com.sap.dictionary.runtime.DdTypeDecimal.parseDecimal(DdTypeDecimal.java:68)

at com.sap.dictionary.runtime.DdTypeDecimal.parse(DdTypeDecimal.java:59)

at com.sap.tc.webdynpro.clientserver.data.DataContainer.doParse(DataContainer.java:1344)

at com.sap.tc.webdynpro.clientserver.data.DataContainer.validatePendingUserInput(DataContainer.java:1254)

at com.sap.tc.webdynpro.clientserver.data.DataContainer.validatePendingUserInput(DataContainer.java:598)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.validate(ClientComponent.java:623)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.validate(ClientApplication.java:728)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.transportData(WebDynproMainTask.java:702)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:639)

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.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: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:159)

[Former Member]

Open an OSS message for the Java DDIC.

As a workaround you might try a calculated view context attribute where the set-method performs the parsing of the user input into a decimal number and sets the original attribute on success.

Armin

[Former Member]

Did you find a solution for this? We have had no problems with decimal format using service stacks 9, 11 and 13 but this exception started to appear in stack 15.