Anjana, I appreciate your help. 
I will try your options. Thanks.

Jorge.

-----Mensaje original-----
De: [email protected] [mailto:[email protected]] En
nombre de Anjana Fernando
Enviado el: sábado, 29 de enero de 2011 0:28
Para: [email protected]
Asunto: Re: [Carbon-dev] DS Fault Message: Error in
'CallQuery.extractParams', cannot find Param

Hi Jorge,

I understand your requirement. Now I see the WSDL may be confusing for you,
since it does have minOccurs="0" to say its optional. This is there because,
we've an option to give default values [1], in a data service query. That
is, if the operation is not passing in the value to a data service query, if
a default value is specific, it will be assigned at the parameter into the
query. When specifying null as the default value to a field, please use
"#{NULL}" as the value. So the ultimate idea is, in data services
perspective, if an input mapping is specified in the data service query, it
should somehow get a value to it, by either directly from the operation or a
default value.

The other option you can follow is, when sending the actual SOAP request, it
will have the elements which contain the parameters, but it will be
signalled as a null value, by using xsi:nil="true"
attribute (nillable="true" is there in the WSDL), so DSS can handle that as
well. So you've to do that properly from the service client you use. And
maybe verify the message using something like tcpmon. For more info on
xsi:nil attribute, refer to [2].

[1]
http://wso2.org/project/solutions/data-services/java/2.5.0/docs/default_vals
.html
[2] http://www.ibm.com/developerworks/xml/library/ws-tip-null.html

Cheers,
Anjana. 


_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to