I need to inject a custom IRequestCycleProcessor into my wicket
application. Since there is currently no way of doing this, I needed to
modify the current code base.
To avoid an API change, rather than injecting this into the constructor,
I used a setter that can be used once the ApplicationFactory is
constructed. In any case, probably in most cases the default
IRequestCycleProcessor will be used, so probably a setter is more
appropriate anyway.
So, this change will not change the API. The only downside is that I
needed to add another interface to the public API package:
public interface RequestCycleProcessorFactory
{
IRequestCycleProcessor newRequestCycleProcessor();
}
This could possibly be avoided by passing in the actual instance of the
custom IRequestCycleProcessor (haven't verified), but I prefer to use a
factory.
I will be committing these changes in a few short minutes. If there are
any objections to the above changes, please holler.
Cheers,
David
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
