[Dev] EI6.4.0 : Expected value type - 'null', but found - 'STRING'.

2019-06-12 Thread Bernard Paris 
Hi devs,

we have this error using DSS of EI.6.4.0.

[2019-06-12 15:17:23,236] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-1 
>> "POST /services/inscriptions-quid/inscriptions HTTP/1.1[\r][\n]"
[2019-06-12 15:17:23,237] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-1 
>> "Host: localhost:8280[\r][\n]"
[2019-06-12 15:17:23,237] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-1 
>> "User-Agent: curl/7.54.0[\r][\n]"
[2019-06-12 15:17:23,237] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-1 
>> "Accept: */*[\r][\n]"
[2019-06-12 15:17:23,237] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-1 
>> "Content-Type: application/json[\r][\n]"
[2019-06-12 15:17:23,237] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-1 
>> "Content-Length: 46[\r][\n]"
[2019-06-12 15:17:23,237] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-1 
>> "[\r][\n]"
[2019-06-12 15:17:23,238] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-1 
>> "{"_postinscription": {"id": "001122334466"}}"
[2019-06-12 15:17:23,271] [EI-Core] ERROR - GsonXMLStreamReader Value type miss 
match, Expected value type - 'null', but found - 'STRING'
[2019-06-12 15:17:23,273] [EI-Core] ERROR - ServerWorker Error processing POST 
request for : /services/inscriptions-quid/inscriptions. Error detail: Value 
type miss match, Expected value type - 'null', but found - 'STRING'. 
java.lang.IllegalArgumentException: Value type miss match, Expected value type 
- 'null', but found - 'STRING'
at 
org.apache.axis2.json.gson.GsonXMLStreamReader.nextValue(GsonXMLStreamReader.java:739)
at 
org.apache.axis2.json.gson.GsonXMLStreamReader.readValue(GsonXMLStreamReader.java:626)
at 
org.apache.axis2.json.gson.GsonXMLStreamReader.stateTransition(GsonXMLStreamReader.java:532)
at 
org.apache.axis2.json.gson.GsonXMLStreamReader.next(GsonXMLStreamReader.java:178)
at 
org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:681)
at 
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)
at 
org.apache.axiom.om.impl.llom.OMSerializableImpl.build(OMSerializableImpl.java:78)
at 
org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:722)
at 
org.apache.axiom.om.impl.llom.OMElementImpl.detach(OMElementImpl.java:700)
at 
org.apache.axiom.om.impl.llom.OMNodeImpl.setParent(OMNodeImpl.java:105)
at 
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:296)
at 
org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:212)
at 
org.apache.axiom.soap.impl.llom.SOAPBodyImpl.addChild(SOAPBodyImpl.java:231)
at 
org.apache.axis2.json.gson.JSONMessageHandler.invoke(JSONMessageHandler.java:84)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
at 
org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:337)
at 
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:383)
at 
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:151)
at 
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
[2019-06-12 15:17:23,297] [EI-Core] DEBUG - wire HTTP-Listener I/O dispatcher-1 
<< "HTTP/1.1 500 Internal Server Error[\r][\n]"


The POST query was:

$ curl -X POST -H 'Content-Type: application/json' 
"http://localhost:8280/services/inscriptions-quid/inscriptions; -d 
'{"_postinscription": {"id": "001122334466"}}'


And here is the dataservice query definition :


INSERT INTO inscriptions values ( now(), now() ,:id)





 




Putting this in $EI_HOME/conf/axis2/axis2.xml  solved this problem on my own 
dev environment  but we tested this config change on QA environment and see 
there are lot of side effects for esb services, so we do not want changing this 
file.  What could be done ?





Bernard



___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Why "Analytics Engine" and "Consent Information Controller" configurations are under "Resident Identity Provider"?

2019-06-12 Thread Isura Karunaratne 
Hi Johann,

On Wed, Jun 12, 2019 at 10:27 AM Johann Nallathamby  wrote:

> Hi Folks,
>
> I just noticed that IS analytics engine configuration is under resident
> IdP configurations. How do we consider an analytics engine configuration as
> an Identity Provider configuration?
>
> Resident IdP configurations are ideally any "configurations" that impact
> runtime interactions with service providers registered in IS, such as
> identity management services, authentication services, authorization
> services and attribute sharing services (not exhaustive).
>
> Analytics engine configuration is a server configuration which is similar
> to "Workflow Engine Profiles" configuration, which is under "Configure" tab
> already. Shouldn't analytics engine configuration also come under
> "Configure" tab?
>
> With respect to "Consent Information Controller" configurations, do the
> details that we configure have any relevance to the service providers? Are
> those values that we configure, exposed through an API for the service
> providers to consume? If that is not the case then I don't see any
> relevance to configure them under resident IdP configurations as well.
>

Identity Server supports consent management REST APIs. Applications can use
these APIs to manage user consents in the application side. Consents
receipts should contain the PII controller information.

Cheers,
Isura.

>
> Thanks & Regards,
> Johann.
>
> --
> *Johann Dilantha Nallathamby* | Associate Director/Solutions Architect |
> WSO2 Inc.
> (m) +94 (77) 7776950 | (w) +94 (11) 2145345 | (e) joh...@wso2.com
> [image: Signature.jpg]
>


-- 

*Isura Dilhara Karunaratne*
Technical Lead | WSO2 
*lean.enterprise.middleware*
Email: is...@wso2.com
Mob : +94 772 254 810
Blog : https://medium.com/@isurakarunaratne
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev