On 12/28/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> lets not forget the important part, assuming the ejb thing works just like
> wicket-spring. things injected are actually proxies not beans themselves.
Yes Igor, I've used the same technique you adopted in the Wicket
Spring integration. Things
mailto:
[EMAIL PROTECTED] *Im Auftrag von *Johan
Compagner
*Gesendet:* Donnerstag, 28. Dezember 2006 18:15
*An:* wicket-user@lists.sourceforge.net
*Betreff:* Re: [Wicket-user] wicket-contrib-javaee moved to Wicket-Stuff
So both beans (statefull or stateless) are injected on every request?
On 12
8:14
An: wicket-user@lists.sourceforge.net
Betreff: Re: [Wicket-user] wicket-contrib-javaee moved to Wicket-Stuff
no, there is no difference
you do not want stateless or stateful beans to be directly referenced by
wicket components, or anything that will end up in httpsession
-igor
On 12/28/06, Korbinian Bac
Betreff: Re: [Wicket-user] wicket-contrib-javaee moved to Wicket-Stuff
So both beans (statefull or stateless) are injected on every request?
On 12/28/06, Korbinian Bachl <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> > wrote:
I believe there you have to differate:
a; stateless-
e: [Wicket-user] wicket-contrib-javaee moved to Wicket-Stuff
lets not forget the important part, assuming the ejb thing works just like
wicket-spring. things injected are actually proxies not beans themselves.
these proxies can be serialized safely - they do not have a hard link to the
underlying ejb
berg
*Gesendet:* Donnerstag, 28. Dezember 2006 17:37
*An:* wicket-user@lists.sourceforge.net
*Betreff:* Re: [Wicket-user] wicket-contrib-javaee moved to Wicket-Stuff
lets not forget the important part, assuming the ejb thing works just like
wicket-spring. things injected are actually proxies not beans t
PROTECTED] Im Auftrag von Igor
Vaynberg
Gesendet: Donnerstag, 28. Dezember 2006 17:37
An: wicket-user@lists.sourceforge.net
Betreff: Re: [Wicket-user] wicket-contrib-javaee moved to Wicket-Stuff
lets not forget the important part, assuming the ejb thing works just like
wicket-spring. things inje
lets not forget the important part, assuming the ejb thing works just like
wicket-spring. things injected are actually proxies not beans themselves.
these proxies can be serialized safely - they do not have a hard link to the
underlying ejb bean. if you do not do this and keep a reference to an ej
On 12/28/06, Korbinian Bachl <[EMAIL PROTECTED]> wrote:
> Hi Filippo,
>
> just browsed through it and its really nice work. Especially if someone
> wants to have EJB3 persitence but not to use EJB3 Stateless Session Beans to
> query it.
>
> However, the thing with the EjbAnnotation looks not so cle
MethodINeed();
Best Regards,
Korbinian
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Im Auftrag
> von Filippo Diotalevi
> Gesendet: Donnerstag, 28. Dezember 2006 12:32
> An: wicket-user@lists.sourceforge.net
> Betreff: [Wicket-us
Hi all,
just a quick post to say that this morning I've moved the
wicket-javaEE integration module to the wicket-stuff svn repository.
More details about this project are available at:
http://code.google.com/p/fdiotalevi/wiki/WicketJavaEEIntegration
The complete url to checkout the module is
http
11 matches
Mail list logo
