Re: FYI Java Library crash

[Kevin Hawkins <yahoogroupskh@xxxxxxxxxxxxxx>]

This was the subject of a thread a little while back and we decided
that
case should not be significant in source (and target) addresses, which
assists in wildcard matching.  However some historic devices have
implemented case dependency here so we recommend that you preserve the
case of the address for any device that you wish to target with a
message , which will maximise compatibility.    Likewise class is not
case dependent but UID must always use uppercase hex.

Within the BSC schema there is no case dependency on the state body
parameter so ON, On , on and even oN are all the same.  However the the
case of the text or displaytext parmeters may well be conveying
important information so should be preserved (application dependent).

K


On 26/03/2010 21:45, Neil Wrightson wrote:
> Morning All,
>
> I did not think the xAP / BSC schema was case dependant.
> But it appears the Java xAPLib is having some issues.
>
> Please refer to the below.
>
>
> Regards,
>
> Neil Wrightson.
> N.W.Electronics
> ABN 76 768 513 867
> Embedded Controllers and Home Automation Products
> Web     : www.nwe.net.au
>
>
> -----Original Message-----
> From: Bob Jacobsen [mailto:jacobsen@xxxxxxx]
> Sent: Saturday, 27 March 2010 4:51 AM
> To: neilw@xxxxxxx
> Cc: Automation
> Subject: Re: Updated script
>
> The the attached xAPlib.jar should fix the problem with crashes when
> processing messages with mixed-case block names.
>
> The problem was that the xAP library was handling upper/lower case in
> different ways in different places.  Sometimes, case mattered, and
sometimes
> not.  This mirrors some comments on the xAP web pages.  I don't see
how this
> can actually work, in general, because two messages that differ in
case
> either are or are not the same.  The existing implementation considers
them
> the same in some ways, different in others, and gets very confused.
>
> What I've done is make case _not_ matter. We'll have to see whether
this
> does what's needed.
>
> Please replace the existing xAPlib.jar file with this one, and see if
we get
> further.
>
> Thanks.
>
> Bob
>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>
>



------------------------------------