Well, I found a surprise sitting in your build path
| | <?xml version="1.0" encoding="UTF-8"?> | <aop> | <!-- This is declaration file for annotation. We are using JDK1.4 now, | so an annotationc pre-compiler is needed for JBossAop. | See build.xml target annoc for details. | Idea is user will then need only to annotate like: | @@org.jboss.cache.aop.AopMarker | in his POJO. There will be no need of jboss-aop.xml from user's side. | Only extra step is annotation compiling. And in JDK1.5, this step | will not be needed since the implicit annotation support. | | For example, see either Address or Person. | --> | | <!-- If a POJO has AopMarker annotation, it will be asepctized. --> | <prepare expr="field(* @org.jboss.cache.aop.AopMarker->*)" /> | | <!-- | Supports inheritance and polymorphism. It can either be a concrete class | or an interface. All sub-classes or interface implementors will be instrumeneted. | --> | <prepare expr="field(* [EMAIL PROTECTED]>*)" /> | </aop> | Is this the correct way to deal with realizing classes or is the approach outlined in the documentation the correct way as the docs take an entirely different approach. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3885494#3885494 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3885494 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
