Sounds totally doable. Pointcuts would definitely be the way I'd use. You just need to consider how to apply the pointcuts: at compile time or runtime. If you do it at compile time, then just vary which aspect libraries are on the aspect path. If you do it at runtime, you'll have to use Spring w/some AspectJ config (you'll have to RTFM for exactly how).
-matthew On Tue, Oct 4, 2016 at 9:05 AM, Ramon Casha <rca...@gmail.com> wrote: > I have an application that needs to be deployed at several different > sites, and most sites demand some slight customisation here and there. > > Rather than have multiple versions of the same software, which would be a > maintenance nightmare, I was wondering whether AspectJ can be used. My idea > was, to define all the different places in which a customer might require a > customisation (pointcuts?), and then implement each site's customisations > as advice, with each site having a different set of advice - while the core > application code would remain always the same for everyone. > > Has anyone ever tried something like this? Is AspectJ a good way of doing > this? > > Ramon Casha > > _______________________________________________ > aspectj-users mailing list > aspectj-users@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/aspectj-users >
_______________________________________________ aspectj-users mailing list aspectj-users@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/aspectj-users
