Commit 42483dd5 authored by George Nash's avatar George Nash

Restrict how OCRole can be used in Java

This commit removes the default constructor generation for
the OCRole class. At this time the user must use
OCObt.addRoleId to create and add roles for the onboarding

This also prevents SWIG generating setter functions for role
and authority.  These should also be assigned using the
addRoleId method.

Change-Id: I396f5f45724d7f714c035866eece18f079dcd54c
Signed-off-by: George Nash's avatarGeorge Nash <>
parent 7f5dbb5f
...@@ -1488,6 +1488,10 @@ void jni_free_server_endpoints(oc_endpoint_t *endpoints) { ...@@ -1488,6 +1488,10 @@ void jni_free_server_endpoints(oc_endpoint_t *endpoints) {
%rename(closeSession) oc_close_session; %rename(closeSession) oc_close_session;
%rename(OCRole) oc_role_t; %rename(OCRole) oc_role_t;
%nodefaultctor oc_role_t;
%nodefaultdtor oc_role_t;
%immutable oc_role_t::role;
%immutable oc_role_t::authority;
%ignore oc_get_all_roles; %ignore oc_get_all_roles;
%rename(getAllRoles) jni_get_all_roles; %rename(getAllRoles) jni_get_all_roles;
%inline %{ %inline %{
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment