Jira issue: WP-9

Check if optional parameter 'parent' is set.
Jira issue: WP-9

Check if parent is set.
Activated run jasmine-node tests with maven

Jira-Issue: WP-253
removed node-gyp storage build from maven profile

Jira-Issue: WP-204
added node-gyp discovery build from maven profile

Jira-Issue: WP-204
Use valid error code for error results.

Use -31000 as application specific error code.
Create jsonrpc object in executeRPC.

This ensures that the unnecessary field serviceAddress isn't send
as part of the jsonrpc object. Instead createRPC will create a
preliminary jsonrpc object with serviceAddress property. The preliminary
object will be used to create the final jsonrpc object in executeRPC.
Remove unused objectRef parameter.

Removes the parameter from all method definitions in the api
implementations where it is not used.

Jira-issue: WP-180
Remove fromObjectRef parameter from JSON-RPC messages.

FromObjectRef was used to associate the RPC object and a callback object
on the request issueing side. Now there is no separate callback object and
instead, the RPC object itself is used to register methods on it that can
receive requests from the responding side. The id of the RPC object is
used to register it as a service. The request receiving side still gets
an objectRef parameter which is now an object looking like this:

objectRef = {
    rpcId: "some id",
    from: "address the request came from"
}

That object can be used with createRPC as before to call methods on the
caller object of the requesting side. Since it now also includes the from
address, the RPC handler doesn't have to save that internally, so the map
for that (objRefCacheTable) is removed. That map was getting bigger since
nothing could be removed from it. The JSON-RPC messages now have no
paramters outside the 2.0 specification.

Jira-issue: WP-180
Remove manual fromObjectRef creation, etc.

Since fromObjectRef is no longer needed on the request issueing side,
remove it. On the responding side use objectRef.rpcId where it is needed.

Jira-issue: WP-180
Update deviceorienation for fromObjectRef changes.

Since fromObjectRef is no longer needed on the request issueing side,
remove it. On the responding side use objectRef.rpcId where it is needed.

Jira-issue: WP-180
Update vehicle for fromObjectRef changes.

Since fromObjectRef is no longer needed on the request issueing side,
remove it. On the responding side use objectRef.rpcId where it is needed.

Jira-issue: WP-180
Merge pull request #175 from pshapovalov/update-maven-profiles

Update maven profiles (WP-204)
Merge pull request #176 from pshapovalov/activation-jasmine-tests

Activated run jasmine-node tests with maven (WP-253)
Merge pull request #177 from aldafu/WP-180-compliant-jsonrpc-objs

WP-180 compliant jsonrpc objs
Merge commit 'a26def176b7f0e95c0c23b457bb567948447d82b' into wp-213-xmpp
Started the integration work with front-end code

Jira issue: WP-213
Changed registerObject to check if parent is set before registering the service with the PZH.

Jira issue: WP-9
Merge pull request #178 from eelcocramer/wp-9

Changed registerObject to check if parent is set before registering the service with the PZH 
WP-9
Another missing check if parent member is set.

Jira-issue: WP-9