Just to let you know that we resolved the issue with the schema loading and
also the use of extension parameters in standard LLRP messages. See
LTK/LTKJava/CHANGELOG.txt for details.
- Christian
PS: We also added another example to the wiki:
http://llrp-toolkit.wiki.sourceforge.net/LTKJava+Example+Code
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Christian Floerkemeier
Sent: Dienstag, 17. Juni 2008 16:30
To: 'LLRP Toolkit Development List'
Subject: Re: [ltk-d] java LTK bugs
Paul,
my mistake. I did not run an cvs update before I built locally this morning.
I thus missed a recent commit that introduced a bug. Will fix it in a few
minutes.
- Christian
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Christian Floerkemeier
Sent: Dienstag, 17. Juni 2008 15:53
To: 'LLRP Toolkit Development List'
Subject: Re: [ltk-d] java LTK bugs
Paul,
One cause for the problem you are noticing could be that the LLRP schema
cannot be loaded when an extension message is used. this is because imported
schemas are loaded via the path specified in the xsd import schemaLocation
attribute in LTKJava. In the extension file I am using (Impinj.xsd) the LLRP
namespaces is imported and the schemaLocation of the LLRP xsd is a URL. The
LLRP schema is thus retrieved from www.llrp.org. If the network connection
is disabled or the firewall blocks it, then the validation of the message
will fail with the following message:
With network connection enabled:
C:\Dokumente und Einstellungen\floerkem\Desktop>java -jar
LTKJava_with_dep_0_1_1
-SNAPSHOT.jar -x -f IMPINJENABLEEXTENSIONS.xml
07 FF 00 00 00 13 00 00 00 02 00 00 65 1A 15 00 00 00 00
C:\Dokumente und Einstellungen\floerkem\Desktop>java -jar
LTKJava_with_dep_0_1_1
-SNAPSHOT.jar -x -f START_ROSPEC.xml
04 16 00 00 00 0E 00 00 00 08 00 00 00 01
Switched off network connection:
C:\Dokumente und Einstellungen\floerkem\Desktop>java -jar
LTKJava_with_dep_0_1_1
-SNAPSHOT.jar -x -f IMPINJENABLEEXTENSIONS.xml
0 [main] WARN org.llrp.ltk.types.LLRPMessage - LTK XML message can not be
valid
ated against schema org/llrp/ltk/Impinj.xsd<?xml version="1.0"
encoding="UTF-8"?
>
<Impinj:IMPINJ_ENABLE_EXTENSIONS
xmlns:Impinj="http://developer.impinj.com/ltk/s
chema/encoding/xml/1.0"
xmlns:llrp="http://www.llrp.org/ltk/schema/core/encoding
/xml/1.0" Version="1" MessageID="2" />
because src-resolve: Cannot resolve the name 'llrp:hexWord' to a(n) 'type
defini
tion' component.
LLRP Message is not valid IMPINJENABLEEXTENSIONS.xml
LTK XML message can not be validated against schema
org/llrp/ltk/Impinj.xsd<?xml
version="1.0" encoding="UTF-8"?>
<Impinj:IMPINJ_ENABLE_EXTENSIONS
xmlns:Impinj="http://developer.impinj.com/ltk/s
chema/encoding/xml/1.0"
xmlns:llrp="http://www.llrp.org/ltk/schema/core/encoding
/xml/1.0" Version="1" MessageID="2" />
because src-resolve: Cannot resolve the name 'llrp:hexWord' to a(n) 'type
defini
tion' component.
C:\Dokumente und Einstellungen\floerkem\Desktop>java -jar LTK
-SNAPSHOT.jar -x -f START_ROSPEC.xml
04 16 00 00 00 0E 00 00 00 08 00 00 00 01
I am not sure whether this is the cause of your problem though. Could you
send me your LTKJava jar and the test message so I can try on my test setups
here?
- Christian
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul
Dietrich
Sent: Dienstag, 17. Juni 2008 13:58
To: Christian Floerkemeier; LLRP Toolkit Development List
Subject: Re: [ltk-d] java LTK bugs
Christian,
Thanks for the quick response. Im cc-ing the development list so others
can benefit from this exercise.
I think you understand my problem, except Im not using netbeans to invoke
the converter. Im using a command line like you give in the example wiki.
Just to re-iterate. Heres my steps:
I build the jar with dep using netbeans. I verified that this jar does
contain Impinj.xsd, llrp-1x0.xsd, and all of the extension classes. (BTW,
your build process is excellent and very straightforward. I appreciate the
work you have done to make this automated).
When I execute the jar from a command line using a classpath of.
Java jar jarfile.jar x f myllrppacket.xml
It complains that it cant find the two files (it needs Impinj.xsd only if
there is an Impinj extension. It appears to need llrp-1x0.xsd only if there
is an LLRP parameter within an Impinj extension. If I add these two files
to target/org
the program runs successfully.
Paul
_____
From: Christian Floerkemeier [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2008 10:47 AM
To: Paul Dietrich
Subject: RE: java LTK bugs
> One minor issue: I tried to execute this and it needed Impinj.xsd and
llrp-1x0-def.xml to be extracted from the jar file into the path org/
to
work.
Hmm, not sure why this is not working at your end. There is a copy task in
the ant file that copies the Impinj.xsd from the path specified in the
build.xml to org/llrp/ltk/Impinj.xsd where it is loaded as a resource.I am
not sure I understand 100% where the problem occurs in your setup but it
seems that you can correctly build LTKJava with the Impinj extensions (using
ant package) and Impinj.xsdand LLRP.xsd are found in the org/llrp/ltk
package of the jar, but when you invoke LLRPConverter in Netbeans with the
corresponding command line arguments it complains about a missing schema. Is
that correct?
- Christian
_____
From: Paul Dietrich [mailto:[EMAIL PROTECTED]
Sent: Dienstag, 17. Juni 2008 12:47
To: Christian Floerkemeier
Subject: RE: java LTK bugs
Christian,
Thanks for the fix. One minor issue: I tried to execute this and it needed
Impinj.xsd and llrp-1x0-def.xml to be extracted from the jar file into the
path org/
to work.
Also, the extension messages do now work (if I do the above), but as you say
below, custom extensions within LLRP messages are still not coming through
from XML to binary.
Paul
_____
From: Christian Floerkemeier [mailto:[EMAIL PROTECTED]
Sent: Monday, June 16, 2008 6:35 PM
To: Paul Dietrich
Subject: RE: java LTK bugs
Great. Thanks. I haven't been able to determine why your and Casey's setup
requires the logging and mine and Basil's does not. In any case, I added the
dependency to the README and wiki doc.
I resolved the LTK extension issue, but I spotted another bug in the code
that causes problems with extension parameters in LTK-XML standard LLRP
messages. I will ask Basil to fix that issue in the next few days.
- Christian
_____
From: Paul Dietrich [mailto:[EMAIL PROTECTED]
Sent: Montag, 16. Juni 2008 13:30
To: Christian Floerkemeier; Basil Gasser
Subject: RE: java LTK bugs
Thanks Christian,
I put a snapshot of my libraries in the Java Wiki (by coincidence) as I was
writing some docs for java novices like myself.
http://llrp-toolkit.wiki.sourceforge.net/Building+LTKJava+in+Netbeans
Both Casey and I confirmed that commons logging was required in our Netbeans
development environment.
_____
From: Christian Floerkemeier [mailto:[EMAIL PROTECTED]
Sent: Monday, June 16, 2008 10:18 AM
To: Paul Dietrich; 'Basil Gasser'
Subject: RE: java LTK bugs
Thanks. I fixed the extension path issue in generator.properties. I am
currently not using the commons logging API in my setup. I suspect that I am
using slightly different versions of some of the other libraries. Can you
send me a directory listing of the lib directory so I can see the versions
you are using? I will add the commons logging anyway.
Will look at the command line tool issue this evening.
- Christian
_____
From: Paul Dietrich [mailto:[EMAIL PROTECTED]
Sent: Montag, 16. Juni 2008 12:43
To: Christian Floerkemeier; Basil Gasser
Subject: java LTK bugs
FYI. I filed three new bugs in tracker. Two are minor dealing with
dependencies and some extra stuff in the build scripts.
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
llrp-toolkit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
