Support custom injectors in resource to model mapping about neba

[DaniRey]

I think that's a nice idea. How would you control which annotations NEBA should record and provide information upon? I see two options - either it simply records all annotations available or it might be configured in the Spring context.
What do you think?

[huberchrigu]

The PostProcessor-like service should provide the annotations it is looking for I'd say. Also depends on the NEBA implementation, which I don't know in detail

[olaf-otto]

I do not think it is safe to make any assumptions what the desired behavior of a post processor is, and specifying what annotation(s) must apply to a model is likely to be insufficient in some situations. Remember that post processors may alter the entire model, e.g. return a proxy instread of the original model and so forth. Besides, it could be relatively cumbersome to specify the desired annotations - what if one is interested in a combination of annotations or wants to filter on specific annotation attributes?

However, I see two different solution approaches:

• No change. The applications must maintain a cache of the types they reflect on
• We provide the post processors with metadata by means of a public interface, and they can use that meta data instead of reflecting on the model.

The latter is my favorit solution, since it provides decent performance and a maximum of flexibility

[huberchrigu]

I will make a suggestion...

[olaf-otto]

I have re-named this issue. In this use case, Post-Processors are employed to achieve injecting custom values based on custom annotations. Thus, we are not talking about a post processor but about supporting custom injectors.

[olaf-otto]

Pull request: #27

[olaf-otto]

Implemented, merged, done!