You could use compile time weaving (binary weaving), that way the code that gets loaded will always be secured. If you allow the user to interfere with startup and deactivate loadtime weaving, there isn't much aspectj can do about that since it won't be getting called at all.
cheers, Andy On 25 October 2011 13:56, hmimou lbyad <[email protected]> wrote: > Hi, > > I know that i can use load time weaving to secure an eclipse product(eclipse > > application), for example put security checks (such as authentification) in my > > advice and use poincut to specify where to apply this checks. > > The weaving takes place when loading classes (from plugins) but if we > uninstall > > Equinox SDK feature (or stop weaving service ) we can't get the weaving and > the > > application will not be secured. > > > how can i always get the weaving ? > > There are something to add in order to be sure that the application is > usually secured? > > > any idea ? > > > thanks in advance . > _______________________________________________ > aspectj-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/aspectj-users > _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
