Finally an update in that matter.
The problem is (was) that custom parameters were decoded incorrectly in
certain cases because the allowedIn constraint wasn't correctly resolved
which led to incorrect mapping.
I opened a bug in the tracker (3013123 Custom Parameter decoded
incorrectly<https://sourceforge.net/tracker/?func=detail&aid=3013123&group_id=194882&atid=951209>),
fixed the issue and closed it.
As the problem is related to custom parameters, those using the regular
libary without extensions aren't affected.
For those using custom extensions, update the templates
(javaParameterTemplate.vm) and regenerate your code.
@Lorischider Can you please confirm that the problem is solved
thanks and regards,
Basil
On Thu, May 27, 2010 at 2:20 PM, Lorischider Honório Resplandes da Silva <
[email protected]> wrote:
> Hi,
>
> I added the capture of wireshark. As was said earlier, I can receive the
> RO_ACCESS_REPORT by the plugin LLRP Commader and message arrives correctly
> (which got me thinking that the problem was in decoding the message). I
> added this response and ROspec that I use.
>
> Kind regards,
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> llrp-toolkit-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
>
>
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
llrp-toolkit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
