> Injecting a null value feels odd. What do you think about providing
> something like:
>
> public interface NullableSymbol {
While I understand the sentiment, what do you gain? You still have to do the
null check to use the value.
Specify required=false tells you to expect null.
I suppose that
On Fri, Sep 16, 2011 at 4:28 PM, Josh Canfield wrote:
> > So what gets injected if the symbol isn't defined? tapestry-ioc
> > already throws an exception if a symbol does not exist.
>
> I would expect null if it's not required and not present.
>
Injecting a null value feels odd. What do you thin
