setter for Navigator is not available in ContextSupport Class

[UsharaniMarappan]

No description provided.

[elharo]

Can you elaborate? I.e. what is the problem you're trying to solve here?

[UsharaniMarappan]

The problem is we cannot use ContextSupport in JEE environment to let container manage the object creation via @Inject and set the attributes later in the code.
If you see ContextSupport class, there are four attributes functionContext, namespaceContext, variableContext and navigator. There is a default constructor and a specific constructor with all the four attributes. I am using default constructor in a JEE environment as I want container to manage the object creation rather than using new keyword. There is a setter for the first three attributes and setter is missing for navigator.
Is there any reason that navigator should not be used when ContextSupport is created via default constructor?

[elharo]

OK, that's plausible. I'm going to need to dig a little deeper and think about this. Adding mutability is not something we can take lightly.

[elharo]

I wonder if there's anywhere we use the no-args ContextSupport constructor? It doesn't seem very useful without this setter.

[UsharaniMarappan]

yes, no-arg constructor is not useful without this setter.
I hope you are not planning to remove this constructor as this is required to use in JEE env.

[UsharaniMarappan]

Adding a setter for navigator should not impact mutability of this class as that class already holds three setters.

[UsharaniMarappan]

Regarding unit test, I dont see any value for a setter. Anyway, if you insist I can write.