You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Robert Bräutigam <br...@gmail.com> on 2015/06/23 14:32:16 UTC

JayWire DI with Wicket

Hi all,

for those who might be interested in a explicit (non-reflection-based),
no-magic, constructor parameter based DI framework for Wicket and Java 8:

https://github.com/vanillasource/jaywire

short wicket howto in wiki here:

https://github.com/vanillasource/jaywire/wiki/Integration-Apache-Wicket

Why another DI framework: I just wanted to write code as I normally would,
with "required dependencies" through constructors, etc. without reflection,
code generation or classpath scanning.

Wicket specifics: It replaces the PageFactory to be able to supply
(stateles) page objects that are explicitly created with "new", with all
dependencies supplied at construction.

State: It is working, but of course experimental at this point. I'm hoping
it will be interesting for enough people to get useful feedback maybe :)

Cheers,
Robert.

Re: JayWire DI with Wicket

Posted by Martin Grigorov <mg...@apache.org>.
Hi,

Thanks for sharing!
I'll take a look in the coming days!

Martin Grigorov
Freelancer. Available for hire!
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Tue, Jun 23, 2015 at 3:32 PM, Robert Bräutigam <
brautigam.robert.gyula@gmail.com> wrote:

> Hi all,
>
> for those who might be interested in a explicit (non-reflection-based),
> no-magic, constructor parameter based DI framework for Wicket and Java 8:
>
> https://github.com/vanillasource/jaywire
>
> short wicket howto in wiki here:
>
> https://github.com/vanillasource/jaywire/wiki/Integration-Apache-Wicket
>
> Why another DI framework: I just wanted to write code as I normally would,
> with "required dependencies" through constructors, etc. without reflection,
> code generation or classpath scanning.
>
> Wicket specifics: It replaces the PageFactory to be able to supply
> (stateles) page objects that are explicitly created with "new", with all
> dependencies supplied at construction.
>
> State: It is working, but of course experimental at this point. I'm hoping
> it will be interesting for enough people to get useful feedback maybe :)
>
> Cheers,
> Robert.
>