I think you will need to debug this in order to get to the root of your
problem. I doubt that the number of properties is the root cause.
If there is something going wrong within Alljoyn, then running your app with
alljoyn debug logging enabled should display any errors there.
To do this, you need to use the debug version of the alljoyn libraries (.jar
and .so) and also set alljoyn debugging on your BusAttachment instance.
If you look at the Android sample apps (e.g. chat, raw) you will see examples
of enabling alljoyn debug logging on bus attachment.
For example:
/*
* If using the debug version of the AllJoyn libraries, tell
* them to write debug output to the OS log so we can see it
* using adb logcat. Turn on all of the debugging output from
* the Java language bindings (module ALLJOYN_JAVA).
*/
mBus.useOSLogging(true);
mBus.setDebugLevel("ALLJOYN_JAVA", 7);
I found the following notes describing its use….
The log level can be set for individual subsystems (e.g. “ALLJOYN_JAVA”) and/or
for “ALL" subsystems.
Log levels for specific subsystems override the setting for "ALL" subsystems.
For example if "ALL" is set to 7, but "ALLJOYN_JAVA" is set to 1, then detailed
log output will be generated for all subsystems except for "ALLJOYN_JAVA" which
will only generate high level log output. "ALL" defaults to 0 which is off, or
no log output.
The log output level is actually a bit field that controls what output is
generated. The bit fields are described as:
0x1: High level log prints (these log prints are not common)</li>
0x2: Normal log prints (these log prints are common)</li>
0x4: Function call tracing (these log prints are used sporadically)</li>
Typically, when enabling logging for a subsystem, the level would be set to 7
which enables High level log, normal log, and function call tracing.
Setting the level 0, forces log output to be off for the specified subsystem.
Regards,
Paul
On Mar 12, 2016, at 4:49 AM, Sajjan Raj, Ajit
<[email protected]> wrote:
> Hi Paul,
> Thanks for the clarification. I was trying to implement the LSF as a Service
> App and when I tried to implement the org.allseen.LSF.LampDetails interface
> the app crashes on launch, but when I reduced the the number of properties in
> the interface to <10 the app functions without any problems.
> Any comments on the same?
>
> Thanks and regards
> Ajit
>
> From: Paul Sigurdson <[email protected]>
> Sent: Friday, March 11, 2016 4:02 PM
> To: Sajjan Raj, Ajit
> Cc: [email protected]
> Subject: Re: [Allseen-core] Limit on number of Properties in the BusObject
>
> Not as such. Definitely not 10. There are Alljoyn interfaces defined in
> Android apps with > 10 properties.
>
> -Paul
>
> On Mar 10, 2016, at 8:58 AM, Sajjan Raj, Ajit
> <[email protected]> wrote:
>
>> Is there a Limit on the number of properties that a BusObject can hold ?
>> I was writing a Code for Android and my Interface has more than 10 different
>> properties. But as soon as the app is launched , it crashes.
>> When i reduce the number of properties to 10, the app runs perfectly fine.
>>
>> Thanks
>> Ajit
>>
>>
>> _______________________________________________
>> Allseen-core mailing list
>> [email protected]
>> https://lists.allseenalliance.org/mailman/listinfo/allseen-core
>
>
_______________________________________________
Allseen-core mailing list
[email protected]
https://lists.allseenalliance.org/mailman/listinfo/allseen-core
