Hi Basil,
 
Following your explanation, I experimented and I replaced "<allowedIn
repeat="0-1" type="SpecParameter"/>" with "<allowedIn repeat="0-1"
type="ROSpec"/>".  With this change, somehow the code generator knows to
associate my custom parameters with the specParameterList within the
ROSpec.  This is just what I want (i.e., my custom parameters show up as
choices in addition to AISpec and RFSurveySpec).
 
Thank you!  I now have a working LTK Java library with Intermec
extensions although it appears that I will need to have 2 separate
Intermec extension definition files (one for Java and one for everything
else ... C, C#, etc.).
 
Regards,

Rob Buck



________________________________

From: Basil Gasser [mailto:[email protected]] 
Sent: Monday, August 10, 2009 1:54 PM
To: Buck, Rob D.; [email protected]
Cc: Christian Floerkemeier
Subject: Re: LTK Java and Custom Parameters


Hi Rob, 

That's acutally a really interesting case you created, not sure if we
have a bug here. I think you define your parameters correctly using
allowedIn, however, some of your parameters are defined as allowedIn for
an interface type. For example you have    <allowedIn repeat="0-1"
type="SpecParameter"/>
Now, SpecParameter is an interface implemented by AISpec, RFSurveySpec
and Custom (where Custom is again implemented by some of your types). I
assume that defining as allowed in SpecParameter what you actually
wanted is having it allowed in all implementing classes. 

Problem is that our Code Generator is not type aware in this case, hence
your parameter is not decoded in for example an AISpec (it would be in a
SpecParameter but since this is an interface this will also never
happen)
You can solve it for now by adding allowedIn statements for all
parameters you'd like. For example put
   <allowedIn repeat="0-1" type="AISpec"/>    <allowedIn repeat="0-1"
type="RFSurveySpec"/>
Instead. 

Does this make sense to you? At first glance it seems to be feasible to
make the allowedIn construct type aware but I'll have to think about it
a bit harder and also see if this is really desired.

Hope this makes things clearer.

Greets, Basil


Am 8/10/09 7:15 PM schrieb "Buck, Rob D." unter <[email protected]>:



        Hi Basil,
        
        My apology for the slow response ... I've been on vacation.  I
have attached the Intermec extensions XML definition and XSD files.  Can
you see a mistake that is causing Custom extensions to be handled
incorrectly?
        
        Thank you,
        Rob Buck
        
        This message is intended only for the named recipient. If you
are not the intended recipient, you are notified that disclosing,
copying, distributing or taking any action based on the contents of this
information is strictly prohibited.
        
        
        


This message is intended only for the named recipient. If you are not the 
intended recipient, you are notified that disclosing, copying, distributing or 
taking any action based on the contents of this information is strictly 
prohibited.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
llrp-toolkit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel

Reply via email to