Documentation

1. 01 VRaptor3 - One minute guide
2. 02 VRaptor3 - 10 minute guide
3. 03 Resources-Rest
4. 04 Components
5. 05 Converters
6. 06 Interceptors
7. 07 Validation
8. 08 View and Ajax
9. 09 Dependency injection
10. 10 Download and Upload
11. 11 Utility components
12. 12 Overriding Vraptor's behavior and conventions
13. 13 Spring, Joda Time and Hibernate
14. 14 Google App Engine
15. 15 Testing components and controllers
16. 16 Scala
17. 17 Optimizations
18. 18 VRaptor Scaffold
19. 19 Exception handling
20. 20 How to contribute to VRaptor
21. 21 Changelog
22. 22 Migrating from VRaptor2 to VRaptor3

17Optimizations

Commons Upload

If you don't upload files on your application, remove the commons upload jar from your classpath. It avoids the unnecessary load of the upload interceptor, and the request will run faster.

@Lazy annotation on Interceptors

If the accepts method from an interceptor doesn't depend on its internal state, you can annotate it with @Lazy:

@Intercepts
@Lazy
public class MyLazyInterceptor implements Interceptor {
    public MyLazyInterceptor(Dependency dependency) {
        this.dependency = dependency;
    }
    public boolean accepts(ResourceMethod method) {
        // depends only on method
        return method.containsAnnotation(Abc.class);
    }
    public void intercepts(...) {
        //...
    }
}

This way, VRaptor only instantiates the interceptor if the accepts method returns true. In order to do that, VRaptor will create a non-functional instance of your interceptor (null for all dependencies) and invokes the accept method on it, avoiding unnecessary Container calls. Using internal state can (and will) result in NullPointerException. Do not use @Lazy if the accepts method is trivial (just returns true).