Ok, just wanted to make sure before duplicating any work.
Anyway, using wicket-ioc and looking at wicket-guice, I implemented a small lib
(two classes, actually) performing CDI injection on Wicket components, wrapping
the reference returned from the CDI BeanManager in a proxy that is serializable
and re-injects all injection points using the BeanManager on deserialization.
This was indeed just a few hours' work ;-)
BUT I currently only handle the most frequent case
@Inject
private Foo foo;
Only field injection, no method, constructor or parameter injection, no
qualifiers or stereotypes. Getting all that right, including test cases, would
easily take a week or two, and the hardest part would not be the implementation
itself but understanding all the details of the CDI spec and fighting with
problems in the app server. (And I still think this serialization issue is
really a bug in Glassfish.)
At any rate, I'd be happy to share my code - would it make sense to create a
small subproject wicket-cdi, either in wicket or in wicketstuff? I think this
topic is of suffciently general interest, or at least will be, when more
projects move to Java EE 6.
Regards,
Harald
________________________________________
Von: Igor Vaynberg [[email protected]]
Gesendet: Freitag, 9. Juli 2010 20:03
An: [email protected]
Betreff: Re: AW: Serialization of injected EJBs
no, the module is for seam 2.1 which does not use weld.
-igor
On Fri, Jul 9, 2010 at 10:55 AM, Harald Wellmann
<[email protected]> wrote:
> And Seam uses CDI/Weld, right? So your module might solve my problems... Is
> it public?
>
> Regards,
> Harald
> ________________________________________
> Von: Igor Vaynberg [[email protected]]
> Gesendet: Freitag, 9. Juli 2010 18:06
> An: [email protected]
> Betreff: Re: AW: Serialization of injected EJBs
>
> well, i recently wrote a wicket-ioc module for seam and it took me a
> couple of hours :)
>
> -igor
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
