Talk about future releases on the dev list got me thinking about the
future of parameters.
I find a common problem is that parameter names in a descriptor can be
misspelt. While the problem settles down once the code and descriptors
are stable, it still got me thinking about two things.
1. Could parameter names in a component descriptor be a
reference to a "public static final String" in the implementing class.
2. Secondly do we need a way of setting acceptable values for a
parameter? If these acceptable values are accessible both in the
descriptor and in the code, then it probably doesn't mater where they
are defined (i.e. desc or code). If I had a list or enumeration of
acceptable values available then my parameter validation starts getting
neater to write or possibly even disappears totally . Obviously this
could not be a mandatory thing, but there are situations where I see it
being very useful.
What do people think?
Tim
IMPORTANT: This email remains the property of the Australian Defence
Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT
1914. If you have received this email in error, you are requested to contact
the sender and delete the email.
