Re: [Wicket-user] wicket-contrib-javaee moved to Wicket-Stuff

2006-12-28 Thread Filippo Diotalevi
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

Re: [Wicket-user] wicket-contrib-javaee moved to Wicket-Stuff

2006-12-28 Thread Johan Compagner
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

Re: [Wicket-user] wicket-contrib-javaee moved to Wicket-Stuff

2006-12-28 Thread Korbinian Bachl
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

Re: [Wicket-user] wicket-contrib-javaee moved to Wicket-Stuff

2006-12-28 Thread Korbinian Bachl
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-

Re: [Wicket-user] wicket-contrib-javaee moved to Wicket-Stuff

2006-12-28 Thread Johan Compagner
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

Re: [Wicket-user] wicket-contrib-javaee moved to Wicket-Stuff

2006-12-28 Thread Igor Vaynberg
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

Re: [Wicket-user] wicket-contrib-javaee moved to Wicket-Stuff

2006-12-28 Thread Korbinian Bachl
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

Re: [Wicket-user] wicket-contrib-javaee moved to Wicket-Stuff

2006-12-28 Thread Igor Vaynberg
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

Re: [Wicket-user] wicket-contrib-javaee moved to Wicket-Stuff

2006-12-28 Thread Filippo Diotalevi
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

Re: [Wicket-user] wicket-contrib-javaee moved to Wicket-Stuff

2006-12-28 Thread Korbinian Bachl
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 clear to me - i mean, every IDE has J5EE support and so in Neatbeans fo