Hello:
It would be very nice if Wink can support Aspectj AOPs ,much like Spring
framework, out of the box where you can weave advices at runtime for cross
cutting concerns.
Currently, I believe the only way to do this is through writing customized user
handlers but the logic would apply across the board to all resources. The
granularity of applying some cross concern logic to specific resources or/and
resource methods are not there.
It is a common use case where you want to make sureĀ that for certain resources
a user has ,say, some role in database while for others you do not care.
Copying the same code all over those resources and resource methods is
cumbersome. Ideally, even a call back methods annotated with @PostCreate , much
like EJB3 call backs, where some logic is called right before a resource method
is invoked would go a long way as well.
However, the AOP support out of the box would eliminated most of issues with
@Before, @Around and @After AOP features.