I'm finding that the annotations in my custom parameter definitions are
not propagating into the corresponding generated Java code. I've
included one of my customParameterDefinition entries below. Is there a
convention for including documentation so that it will propagate into
the generated code?
<customParameterDefinition name="IntermecAISpecStopTrigger"
vendor="Intermec" subtype="28"
namespace="Intermec">
<annotation>
<documentation></documentation>
<description copyright="Copyright 2009, Intermec Technologies
Corporation">
<h:p>Intermec-specific AISpec stop trigger. This trigger can be
used in conjunction with the standard AISpecStop trigger. If this
IntermecAISpecStopTrigger is specified, and the standard
AISpecStopTrigger is type Null, only the IntermecAISpecStopTrigger will
be used. If the IntermecAISpecStopTrigger is specified and the standard
AISpecStopTrigger type is not Null, both triggers will be used, and the
first trigger condition to be met will stop the AISpec.</h:p>
</description>
</annotation>
<parameter repeat="0-N" type="Custom"/>
<allowedIn repeat="0-1" type="AISpec"/>
</customParameterDefinition>
Regards,
Rob
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
