You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Moritz Mädler <ma...@moritz-maedler.de> on 2010/07/07 15:00:57 UTC

Wrong mapping of Boolean

Hi,

after solving a problem w/ SSL-Endpointaddresses through installing a snapshot-version of axis2,
i now run into another problem: I have several problems w/ the simple type boolean. It is exposed in the
WSDL as xs:boolean but handing over a request containing true / false i get the following exception:

ERROR 2010-07-07 14:33:45,202 [http-8443-9] (RPCMessageReceiver.java:202) - For input string: "false"
java.lang.NumberFormatException: For input string: "false"
	at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
	at java.lang.Integer.parseInt(Integer.java:481)
	at java.lang.Integer.<init>(Integer.java:636)
	at org.apache.axis2.databinding.typemapping.SimpleTypeMapper.getSimpleTypeObject(SimpleTypeMapper.java:80)
	at org.apache.axis2.databinding.utils.BeanUtil.processObject(BeanUtil.java:740)
	at org.apache.axis2.databinding.utils.BeanUtil.ProcessElement(BeanUtil.java:673)
	at org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:582)
	at org.apache.axis2.rpc.receivers.RPCUtil.processRequest(RPCUtil.java:153)
	at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:199)
	at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:110)
	at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
	at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:178)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:173)
	at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:145)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
	at java.lang.Thread.run(Thread.java:636)



To avoid the problem i have to pass a 0 or 1 to the service. Using a auto-generated stub, which correctly creates the parameter as 
booleans I'm not able to set the necessary 0 or 1. I think this could be a bug as the problem was not present in the regular 1.5.1 release.

Is there a possibility for a quick fix?

Thanks alot!



---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org