[jboss-jira] [JBoss JIRA] Commented: (JBAS-3858) Update tc6-cluster.aop to match the current configuration

[ http://jira.jboss.com/jira/browse/JBAS-3858?page=comments#action_12347064 ] Ben Wang commented on JBAS-3858: -------------------------------- OK, couple things need to happen here: 1. We should deprecate the org.jboss.web.tc5.session.AopMarker (and InstanceOfAopMarker). They are there for JDK1.4 annotation and annoc. And PojOCache 2.0 don't support JDK1.4 anymore. 2. Now that we use JDK5.0, I'd also propose we just use the annotations in PojoCache, e.g., org.jboss.cache.pojo.PojoCacheable (but please also be aware of that I may need to change the annotation name before this Friday, see http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986033#...). 3. Originally, we need Oberserver and Obervable pattern to subscribe to POJO field change event. We won't need that anymore since now PojoCache 2.0 provides PojoCacheListener event that can emit field changes. tc6 can subscribe to the event directly. 4. As a result, we would need tc6-cluster.aop to only consist of jboss-aop.xml. That jboss-aop.xml will be a copy of pojocache-aop.xml in the distro (similar to *-service.xml convention). Another question will then be how can a user run "aopc" to pre-process the POJO? He will need: 1. put the classes under all/lib in the classpath. Or maybe just jboss-cache.jar, pojocache.jar, and jboss-aop-jdk50.jar is enough, I haven't verified. 2. put tc6-cluster.aop (or equivalently, pojocache-aop.xml) in the classpath 3. User class lib (can also include additional 3rd party one as well) to generate the byte code weaving. Maybe we can provide a script to do that. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira