Hi,

In TreeCacheAop doc you state sth like this: "..Whenever there is state change 
('set*' interceptors)..All 'get*' operations.. "

I wonder if it is a good idea to restrict user of JBossCache to conform to some 
getters-setters standard. Maybe it would be better to intercept field access 
(read or write) using standard JBossAOP: get/set(field expression)?

You know there might be problems with "settle(..)" method for example, and 
maybe someone (I :) ) doesn't like accessing their private implementation 
through getters and setters..

I _think_ field access joinpoint would solve some problems..

How do you think? Maybe you have that in your plans for 1.2.

And one more thing: are you going to extract jbossCache as a concern, you 
know.. to provide jboss-aop.xml bindings for jbossCache, for users who will 
need some more advanced concern management?

Thanks in advance,
Tomasz Nazar


View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3854441#3854441

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3854441


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to