@DayS @yDelouis, i do not use our REST API, but this PR seems to be useful. It should be reviewed.

I reviewed this PR quickly and I have some comments :

• You should create a Handler for these two annotations : Header and Headers to be able to validate them. To be sure they are used on methods in an interface annotated with @rest.
• You should add a some tests in functional-tests so that we can check whether the generated code is right.

Another comment, not related directly to this PR :
The REST part of AA is becoming very messy. An annotation should be handled by the corresponding handler and only by it Here we have one handler handling at least 6 annotations.

@maltzj can you refactor your PR as @yDelouis suggested? Without those changes we cannot merge it. :(

@yDelouis What do you mean by becoming messy? I do not know the REST part of AA, but for me we have different handlers.

The method declareHttpHeaders in RestAnnotationHelper is 70 lines long for example and deals with @Accept, @Headers, @RequireCookie, @ RequiresAuthentication...
That makes annotations depend on each other which is never a good thing.

OK, i suspected that RestAnnotationHelper has something to do with it. If you think the problem is serious, open a new issue about refactoring the REST part.

@yDelouis can you refactor this PR?

After 4.0.

Refactored to #1470.