hi,
I hope you saw my answer on the mailing list: The problem with the schema could 
either be the xs:int that should be xs:Int or the schema can't be loaded 
because of firewall rules (or missing internet connection)

Regarding the other issue you had, when I do the following:
// message you sent me
String str = 
"00000100001111010000000000000000000000001101011001010100100000110010101010100001000000001111000000000000010001001000110100000000000000000000000000000000000000000000000000000000000000000000000000000011000010000110000110000001000000000000000110000110111001111000001000000000000001001000100010101100111000010001111110000110101101111000010000000000000001001000100010101100111000010010000101001100001100100000001111111111000000000000111000000000000000000110010100011010000000000000000000000000001110000000110010110101000000111111111100000000000011100000000000000000011001010001101000000000000000000000000000111001111101100000101000000000111100000000000001000100100011010000000000000000000000000000000000000000000000000000000000000000000000000000001010101110001101011000000100000000000000011000011011100101100000100000000000000100100010001010110011100001000111110111101000111001100001000000000000000100100010001010110011100001001000010111110001010110000000111111111100000000000011100000000000000000011001010001101000000000000000000000000000111000000010110101000000000011111111110000000000001110000000000000000001100101000110100000000000000000000000000011100111110101011101000000000011110000000000000100010010001101111000100000000010010000001001110110011100001100000000010111001000010000000000001011001000011110100000010000000000000001100001101101011010000010000000000000010010001000101011001110000100011111010111000101111010000100000000000000010010001000101011001110000100100001011100100101001100000011111111110000000000001110000000000000000001100101000110100000000000000000000000000011100000000010111110100000001111111111000000000000111000000000000000000110010100011010000000000000000000000000001110011110111110011000";
                LLRPBitList bits = new LLRPBitList(str);
                LLRPMessage message = 
LLRPMessageFactory.createLLRPMessage(bits);
                System.out.println(str.equals(message.toBinaryString()));
                RO_ACCESS_REPORT ro = null;
                try {
                        // ro = new RO_ACCESS_REPORT(message.encodeBinary());
                        ro = new RO_ACCESS_REPORT(message.encodeXML());
                        //System.out.println(ro.toXMLString());
                } catch (InvalidLLRPMessageException e) {
                        e.printStackTrace();
                }
                List<TagReportData> tagReportDataList = 
ro.getTagReportDataList();
                for (TagReportData tagReportData : tagReportDataList) {
                        for (Custom custom : tagReportData.getCustomList()) {
                                if (custom instanceof ImpinjPeakRSSI) {
                                        ImpinjPeakRSSI impinjPeakRSSI = new 
ImpinjPeakRSSI(custom);
                                        
System.out.println(impinjPeakRSSI.getRSSI());
                                }
                                if (custom instanceof ImpinjRFPhaseAngle) {
                                        ImpinjRFPhaseAngle impinjPhaseAngle = 
new ImpinjRFPhaseAngle(
                                                        custom);
                                        
System.out.println(impinjPhaseAngle.getPhaseAngle());
                                }
                        }
                }

I get the output:
true
3253
-2550
2896
-2700
762
-4200

so from my point of view everything is working fine, or am I missing something?

regards, 

Basil



On Jun 8, 2010, at 2:40 PM, Lorischider Honório Resplandes da Silva wrote:

> @Basil
> 
> The update that you did worked correctly! Thank you very much for your help.
> 
> I said earlier that an error occurred while trying to compile LTKJava with 
> the specifications Impinj.
> 
> What happens is that the messages were generated correctly but to test them, 
> an error occurs in the class LLRPMessage, more specifically the method 
> isValidXMLMessage. The error indicates that the messages can not be validated 
> and the schema Impinj.xsd and LLRP-1x0.xsd.
> 
> The error is exactly this:
> org.llrp.ltk.types.LLRPMessage - LTK Can Not Be XML message schema validated 
> Against org/llrp/ltk/llrp-1x0.xsd <? xml version = "1.0" encoding = "UTF-8"?>
> <xml message>
> because src-resolve.4.2: Error Resolving component 'xs: int'. It was detected 
> that 'xs: int' is in namespace 'http://www.w3.org/2001/XMLSchema', But 
> components from this namespace are not Referenceable from schema document 
> 'null'. If this is the incorrect namespace, Perhaps the prefix of 'xs: int' 
> Needs to Be Changed. If this is the correct namespace, then an appropriate 
> 'import' tag Should Be added to 'null'.
> 
> As I checked the messages were properly configured, simply commented this 
> method (keeping your return true). I know that this solution is not the most 
> appropriate.
> 
> Any solution for this?
> 
> thanks in advance, regards,
> ------------------------------------------------------------------------------
> 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

------------------------------------------------------------------------------
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

Reply via email to