Hi,

In my application I'd like to push an object into the environment for which
null is a valid state. Currently the implementation peeks for the result,
sees null and throws an exception which says the class is missing from the
environment.

The null value is added to the stack so the resulting exception lists my
class as one of the available items in the environment.

My workaround currently is to just use environment.peek where I want to grab
the object, which is working fine both when the object is there and when it
is null.

So, my question is should we be able to use @Environmental with null values?


Thanks,
Josh

Reply via email to