Carsten Ziegeler schrieb: > Deepal Jayasinghe wrote: >> Hi Carsten; >> >> I went through your patch and realized that , you are giving read only >> access to the properties . So if someone want to change the value of >> property (properties) then he wont be able to do that. I think we need >> to provide way to change them as well . >> > Hmm, but in this case has the MessageContext no control about what has > been changed, because it happens outside of its context. > > But I will come up with another patch which will handle put and remove > as well. > Ok, I look at a possible solution - but I think it's not worth the effort :) In order to be able to change the map, it's requrired to provide a map implementation which acts as a wrapepr around all the other maps. Simple operations like put,get,remove etc. are simple to implement - but complex ones, like values(), entrySet() etc. require a lot of code. We could use commons-collections and their CompositeMap for that - at least partically.
Before I implement this, I would like to know if adding a dependency to commons collections just for this simple feature is fine. Personally I think the getProperties() method should return an unmodifiable map. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
