Hi Igor and Eelco,
I studied wicket-seam code and i understand its injection pattern
pretty well. But i want to implement the seam integration by other
approach because there are some special things:
1. With SeamProxyTargetLocator is not possible to inject null values.
2. in
its possible, you just have to figure out how to do it :)
-igor
On Nov 18, 2007 5:23 AM, Frank Martínez [EMAIL PROTECTED] wrote:
Hi Igor and Eelco,
I studied wicket-seam code and i understand its injection pattern
pretty well. But i want to implement the seam integration by other
approach
Hi Igor and Eelco,
I studied wicket-seam code and i understand its injection pattern
pretty well. But i want to implement the seam integration by other
approach because there are some special things:
1. With SeamProxyTargetLocator is not possible to inject null values.
2. in
On Nov 16, 2007 5:22 AM, Frank Martínez [EMAIL PROTECTED] wrote:
Hi,
I am working with jboss seam by about one year, now i am developing a
wicket-seam integration based on wicket-seam-test.
Good to hear someone is working on it!
I will send it to the wicket developers when i finish it.
You
Hi,
I am working with jboss seam by about one year, now i am developing a
wicket-seam integration based on wicket-seam-test.
I will send it to the wicket developers when i finish it.
I am not expert on Wicket and i have some questions:
1. Are Wicket Components instantiated on every request?
2. In
On Nov 16, 2007 8:15 AM, Igor Vaynberg [EMAIL PROTECTED] wrote:
components are not instantiated on every request - they are only
instantiated when YOU instantiate them using the NEW operator...wicket
is unmanaged.
the problem with using onbeforerender is that some components need
access to
components are not instantiated on every request - they are only
instantiated when YOU instantiate them using the NEW operator...wicket
is unmanaged.
the problem with using onbeforerender is that some components need
access to resources from inside their constructors which is too early
to be
