Hi! No problem. But it's essential for me to have "included" entities.
Say you have a product line and some already developed aspects, and want to include A, B, C concerns for configuration 1 of application, and only A and C for 2nd application. The only way, I think is to have two separate XML AOP files: config1-aop.xml and config2-aop.xml and manage concerns by including them using XML entities. Well, one could use some Ant's task to do this, but this is cleaner I think. So, this way it is possible to develop product lines with JBossAOP. See you, Tomasz Nazar View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3853254#3853254 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3853254 ------------------------------------------------------- This Newsletter Sponsored by: Macrovision For reliable Linux application installations, use the industry's leading setup authoring tool, InstallShield X. Learn more and evaluate today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
