I've been thinking of a change to how component parameters work. Currently, the required attribute of the Parameter annotation indicates that a component parameter must be bound (either explicitly, or to a default). It makes no assurances that it is bound to a non-null value.
I'm considering changing that, so that there would be a null check for component parameters that are required, with an immediate failure if the value bound to a required parameter is null. The question is: is this a destabilizing change? Has anyone written components with required parameters that are allowed to be null? -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
