In general this kind of problem is a cross cutting concern. We have some tree of metadata that needs processing by a deployer aspect, but only some parts of the metadata are relevent to it.
This is usually done by a vistor pattern. But as we know, patterns are best implemented with aspects. 1) You avoid the boiler plate code 2) You don't need to know ahead of time where the pattern applies The only problem is that we are now applying an aspect to an aspect :-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864396#3864396 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864396 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
