GitLab

With oc_endpoint_string_parse_path exposed to java there is
no longer a need to have the two parameter variant of the
stringToEndpoint method that uses an array to return input
parameters which is really unusual in Java.
Signed-off-by: George Nash <george.nash@intel.com>

Visual Studio and updated the preprocessor defines for each
project so they all match the iotivity-lite library build.

The CloudServer was using the old OC_IDD_FILE macro that was
only in the code for a very short while and was eventually
replaced with OC_IDD_API instead.

Anywhere that _CRT_NONSTDC_NO_WARNINGS was used I instead used
_CRT_SECURE_NO_DEPRECATE both of the predefine macros should
have the same effect. In older code (pre-VS2012)the first macro
was used. In newer code the second macro was used. Since the
effect should be the same rather than switch to a differnt macro
for different projects I have chosen to use the newer macro.

Rearanged the order the preprocessor defines are listed in. This
makes no difference on the build but does make a difference when
vewing the macros within the Visual Studio. By placing the
macros that differ between the Debug and Release build last
makes it possible to see most of the macros even when "All
Configurations" option is selected in the properties page.
Signed-off-by: George Nash <george.nash@intel.com>

Add a callback that is invoked when doxm "owned" value is
changed.

Add an API to query the current ownership status of a device.
Signed-off-by: George Nash <george.nash@intel.com>

This exposes oc_endpoint_string_parse_path to Java
under OCEndpointUtil.endpointStringParsePath

Ignore oc_ri_is_client_cb_valid this function is not
expected to be used in Java.

With oc_endpoint_string_parse_path exposed to Java we are
able to update the OCEndpointUtil.stringToEndpoint method so
it can take only one parameter. Since developers are already
using the stringToEndpoint method that takes two parameters
we need to still provide that method.

The stringToEndpoint that takes two parameters has a return
value in one of the parameters.  Although this works it is
very unsual in Java to use code this way. Now users can call
the single parameter version of stringToEndpoint and if they
need the path from that endpoint they can call
endpointStringParsePath using the same endpoint string. More
method call but much closer to what a Java developer would
expect.
Signed-off-by: George Nash <george.nash@intel.com>

Signed-off-by: George Nash <george.nash@intel.com>

When the project was moved from gerrit and jenkens there
were locations in the README files that the new paths
were not updated. This change updates those URLs.

Also improves a few other locations in the text.
Signed-off-by: George Nash <george.nash@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Exposed oc_cps_t enum as OCCloudProvisioningStatus. Removed
the `OC_CPS_` prefix from the enums when exposed to Java.

The OCDiscoveryAllHandler typemap was moved from oc_api.i to
the iotivity.swg file so it can be picked up in oc_cloud.i
oc_api.i, and oc_obt.i files. Had to move the typemap instead
of importing oc_api.i to avoid name conflicts.

The oc_cloud_discover_resources was exposed as
OCCloud.discoverResources.
Signed-off-by: George Nash <george.nash@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

The OCEndpointUtil.freeEndpoint method will free the memory associated with an
endpoint. If the Java code thinks that it is responsible for freeing the
memory it will also free the endpoint when the GC is run. This results in
freeing memory that was already freed and may be in use by other memory.

This updates the JNI code to check if Java thinks it is responsible for the
memory associated with the endpoint being freews.  If so it will update
the OCEndpoint in question so it no longer thinks its responsible for the
native memory associated with the OCEndpoint. I addition the copy of the
C pointer held in the OCEndpoint class is set to 0 (i.e. NULL) to avoid
having a floating pointer that could cause other problems.
Signed-off-by: George Nash <george.nash@intel.com>

Signed-off-by: George Nash <george.nash@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: George Nash <george.nash@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>

Signed-off-by: Kishen Maloor <kishen.maloor@intel.com>