We have a java.util.date object in a WS response and it works fine if i am to call the connector created from its original WSDL provider. In this case i can see that the WS response comes formatted as a String (with ContentType DateTIme) of pattern
Issue is while we use a WSDL first provider,we are using a WSDL first Provider to implement a specification,below are the steps how i do it
We create a specification in IS and use it as a signature of empty
ServiceAand then create a regular WSDL provider and connector out of
We use this as a Interface and we will create different implementation of this interface by having our own custom
ServiceBwhich does the logic what we want . To do this we are creating a WSDL first provider using the WSDL URL from
Step1'sWSDL .The AutoGenerated service of this is calling
ServiceB. we could have Many services likes this having the same signature. this let us have any number of implementation of the service we created in
step1with the specification
So in our code we use the connector created in
_portof the WSDL provider created in
step2. the problem this way is with java.util.date Object fields in the response is not formatted as
yyyy-MM-dd'T'HH:mm:ssin WS response and hence it throws a soap fault saying the
[ISS.0088.9139]output parameters do not conform to targetOutputSignature errorcode=DT-001 pathName=<<PathToDateObjectFieldintheResponse>> errorMessage=[ISC.0082.9469] Value does not match patterns
Does that make sense ? if yes, Do you know why is it happening and how can i prevent it by keeping the field as java.util.date Object itself.
I am also trying to understand how IS does the above conversion highlighted as bold by default in direct WS calls. Any leads would be much appreciated. Thanks for your time!