above shows schema validation failure at the $.source.properties path. Note that the validation will output one log line for the exact failing path and a log line for its parent, therefore to find the source cxs object that contains the context with the current user profile, segments, scores as well as functions that makes it easier to perform further requests (such as collecting events using the cxs.collectEvents() session properties. If you need this data, you must send a JSON object to configure the resulting output of the context.js(on) servlet. Here is an example that will retrieve all the session and profile

cxs object that contains the context with the current user profile, segments, scores as well as functions that makes it easier to perform further requests (such Apache Unomi 1.x - Documentation - 14 as session properties. If you need this data, you must send a JSON object to configure the resulting output of the context.js(on) servlet. Here is an example that will retrieve all the session and profile is properly updated. One recommend way of doing this is to use the event-tail command that will output something like this : ID |Type |Session

can list the installed JDKs with the following command : /usr/libexec/java_home -V which will output something like this : Matching Java Virtual Machines (7): 1.7.0_51, x86_64: "Java SE 7" containing strictly context information or as a couple of JSON objects augmented with javascript functions that can be used to interact with the Unomi server using the /context }(document, 'script', 'context')); This initial context results in a javascript file providing some functions to interact with the context server from javascript along with two objects: a cxs object containing