Andreas Gudian

That sounds great! I'd say open the PR and we'll check it out more closely. Regarding your questions: 1. I'd say it is okay to not try to update the...

> The main problem with the @BeforeMapping callback with @MappingTarget is that there is no real result object to pass in until after the X.Builder.build() method is called (which is...

Using constructors for immutable beans is in the works already (the PR is dormant currently, we'll have to iron out some conceptual stuff), a more general support for builders is...

> After some edits to this post, this would be the outline of my idea: > > * usePlain could be Mapper#usesLegacyObjectFactory (legacy means, non-@ObjectFactory-annotated and non-'CDI'/'Spring'/'JSR330' annotated), but now:...

The type detection is one thing - but once "we" get #644 fixed, it should be almost no problem anymore... @sjaakd is working hard on the fix, and it's probably...

Oh, that seems to have fallen off the radar. I'd like to give it another look in the next weeks.

Would be interesting to know what the generated code is supposed to look like. Perhaps that can bring the discussion a bit forward... Right now I still don't have an...

OK, I get the use case and how you'd like to use the results. What I'm missing is how you want to pass the filter-information to the mapper and how...

The cool thing about Roaster is that it also has a nice API for creating an AST... which is something we might want to go for anyway... :)

Thanks for the thorough report! I think adding a method that has a query parameter „acl“ defined should do the trick to route that call to that other method. Would...