Error While Calling Webservices Using Flists That Contain Timestamps

(Doc ID 1317094.1)

Last updated on SEPTEMBER 19, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.4.0.0.0 [Release 7.4.0]
Information in this document applies to any platform.
Checked for relevance on 25-Nov-2013

Symptoms

Whenever we are using timestamps in flists, there will be a parsing error like in the following, while calling opcodes:

<SEARCH_inputFlist>
<ARGS elem="1">
<CREATED_T>0</CREATED_T>
</ARGS>
<FLAGS>256</FLAGS>
<POID>0.0.0.1 /search -1 0</POID>
<RESULTS/>
<TEMPLATE>select X from /account where F1 = V1 </TEMPLATE>
</SEARCH_inputFlist>
AxisFault
faultCode: {http://xml.apache.org/axis/}Server.userException
faultSubcode:
faultString: javax.xml.rpc.soap.SOAPFaultException: java.text.ParseException: Unparseable date: "0"
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:javax.xml.rpc.soap.SOAPFaultException: java.text.ParseException: Unparseable date: "0"
at com.portal.webservices.OpcodeCaller.opcodeWithFlags(OpcodeCaller.java:292)


A workaround is to use the following date format:

<SEARCH_inputFlist>
<ARGS elem="1">
<CREATED_T>1970-01-01T00:00:00Z</CREATED_T>
</ARGS>
<FLAGS>256</FLAGS>
<POID>0.0.0.1 /search -1 0</POID>
<RESULTS/>
<TEMPLATE>select X from /account where F1 = V1 </TEMPLATE>
</SEARCH_inputFlist>


This format is not described in the documentation.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms