C and C++ don't parse XML yet, so they do not address this problem. Perl
will error. I believe .NET will error as well.
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Christian Floerkemeier
Sent: Wednesday, June 11, 2008 3:44 PM
To: 'LLRP Toolkit Development List'
Subject: Re: [ltk-d] Java conversion from XML to binary
Paul,
I assume you are refering to the case where a custom extension element
is used in an LTK-XML message that has not been defined in a
corresponding "extensionDef.xml" via the "allowedIn" construct. Is that
correct?
In LTKJava, such an LTK-XML message will currently get validated against
the schema due to the <xs:any ... in LLRP.xsd but since LTKJava does not
know about the extension, the content is never processed. I guess it
would be appropriate to generate at least a warning message. How are the
other implementations handling this issue?
- Christian
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Paul Dietrich
Sent: Mittwoch, 11. Juni 2008 18:12
To: LLRP Toolkit Development List
Subject: [ltk-d] Java conversion from XML to binary
I noticed that when I convert an XML message to binary, it
ignores the custom extension elements. Should this be the behavior or
should it error on the packet?
-------------------------------------------------------------------------
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
