Repository navigation
Not possible to annotate subclasses of ArrayAdapter with @EBean #347
Description
Activity
I just played around a bit and came up with a patch eventually.
http://pastebin.com/HNJqGz8E
However the Validation is missing for this.Hi @dkunzler . I agree this can be a problem. We are still trying to figure out a way for
@EBeanto work properly on all levels (scopes, dependency injection, view injection), and maybe in the end we'll switch to an implementation that's quite different from the current one. But meanwhile, you just found a real problem and we need to fix it. Your solution seems quite appropriate.- added a commit that references this issue
on Oct 22, 2012 As a side note, I don't think
ArrayAdapters are much useful. I don't think they make things any easier, and for me extendingBaseAdapterprovides much more flexibility without requiring much extra code. If you look atArrayAdaptercode, you'll notice a lot of defending code to prevent bad usage of its API.Why do we not simply recopy all the constructors from super class and add a super(...) call for each one ?
Ok, because the lifecycle of that components are managed by AA. #SelfAnswer
It is not possible to annote custom subclasses of ArrayAdapter with @ebean since these need invoke a super constructor that contains a context as parameter.
Therefore it is not possible to create an empty constructor which is necessary to work with EBean.
Possible Solution:
Instead of insist on an empty constructor allow additionally a constructor taking a Context as parameter. If it is present call is with the context (The generated class has a Context in the constructor already, so it should be no problem to implement it.)