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 API. Was this intended or is it a bug, because for the List type attributes ComponentContext lands up having a reference point right in the definition cached in the DefinitionFactory?
cheers, pdhoolia
