Thanks. Maybe I should AOPize the EntityEJB cache instead of AOPizing the entityEJB itself.
I am trying to manipulate some attributes of certain entityEJBs of a J2EE application in a way transparent to the J2EE application. For example, when a CreditCard entityEJB is created the first time, its credit card attribute is encrypted before being storing to database. When the credit card owner or other authorized user accesses the credit card info, the credit card attribute is decrypted. I am thinking of AOPizing the entityInstancePool or any cache used for entity EJBs. But I am not sure whether it's feasible or it will violate any spec. By the way, I check the latest JBoss source code and 3.0.x document trying to understand how the entity EJBs are initialized and put in the cache. I don't quite understand the process and classes used by EJB container. Can anyone give me a direction where to look? Thanks in advance. Ben. C. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835597#3835597 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3835597 ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
