Home

Welcome to the IoT Scenario Engine Project wiki (road map document)!

Json/Object Serialization/Deserialization issue No. 1

Issue: On POST, request becomes OPTIONS when setting headers.

Explanation & path to solution: Unlike simple requests (discussed above), "preflighted" requests first send an HTTP request by the OPTIONS method to the resource on the other domain, in order to determine whether the actual request is safe to send. Cross-site requests are preflighted like this since they may have implications to user data. In particular, a request is preflighted if:

It uses methods other than GET, HEAD or POST. Also, if POST is used to send request data with a Content-Type other than application/x-www-form-urlencoded, multipart/form-data, or text/plain, e.g. if the POST request sends an XML payload to the server using application/xml or text/xml, then the request is preflighted. It sets custom headers in the request (e.g. the request uses a header such as X-PINGOTHER)

---

DB connection in a web project includes Tomcat (and possibly Maven as well):

Issue: While using db connection to mysql server (w/ j5 oracle connector) - connector's class can't be loaded. Thus, its functionality is unavailable.

Explanation & path to solution:

• Project includes Tomcat, should have the jar file of the connector inside tomcat's lib path.
• Project having Maven and Tomcat, should have the J5 connector dependency in its pom file.
• Duplicates of jars can lead to project crash or thrown exceptions. make sure jar is included only in one place.

---

Json/Object Serialization/Deserialization issue No. 2

Issue: Partial serialization or no serialization at all(!)

Explanation & path to solution: Json serializers work with automatically generated setters and getters. Thus, syntax should be accurate such that serialization would work correctly. (There's use of getters setters. However, no use of ctors.)