This is a known behavior ;-).
It is not a bug, it is an implementation choice (for efficiency, this
reduce the number of objects created ).
In the normal usage, you should only consult, add or remove attributes
from ComponentContext. You should not modify the attributes obtained
from the
This is a known behavior ;-).
pdhooliaI guessed so, that's why I asked rather than saying that it is
a bug. Returning a cloned definition or a cloned list everytime could be
heavy on performance. I agree. By the way it would be possible only to
modify the list items since String is itself
Hi,
Current implementation of ComponentContext is such that you can make
changes to it in such a manner that the base definition cached with the
DefinitionFactory will reflect those changes. In effect it is possible
to
cause global changes for all subsequent requests thru the
ComponentContext
