argh, the list is still broken - so i have to post from nabble. how can they
ban gmail accounts? shtoopid!
On 10/2/06, Geoff hendrey [EMAIL PROTECTED] wrote:
OK, yes I needed to have maven 2.
Couple things though.
1) the src path is wrong in pom.xml (I will change that)
how do
the children of the component are not available yet.
the linkage between component and its parent is the first thing created by
the call to super().
only the class and id are available because it would be dangerous to give
you access to anything else because the child is still being
if you want to use straight jdbc that should be easy. what you need is a
connection pool - there is one in apache commons.
you store the connection pool reference in your Application subclass.
whether you create it there or pull it out of jndi is up to you.
then you subclass requestcycle and do
you missed this:
public SomeModel() {
InjectorHolder.getInjector().inject(this);
}
-Igor
Leszek Gawron-2 wrote:
Joni Freeman wrote:
Yes, it works. I use it in many places.
Joni
I have just checked:
public class GlobalNewsListModel extends LoadableDetachableModel {
this is nice.
what i do like about it
* you can inject anything anywhere
what i dont like is
* post constructor injection like youve mentioned - delegate or not it still
sucks, a different pointcut is needed
* you have to keep your variables transient - very easy mistake to make,
otherwise big
in life, but especially in programming, you cant have something for nothing
:)
-Igor
Leszek Gawron wrote:
igor.vaynberg wrote:
you missed this:
public SomeModel() {
InjectorHolder.getInjector().inject(this);
}
hmmm .. another thread local/singleton ... nice
is it possible to change calendar.js and include an include_only_once logic?
-Igor
Pierre-Yves Saumont wrote:
Hello Matej,
I eventually found the updated file. (I was looking for the calendar.js
file, and not for wicket-ajax.js). It doesn't change anything. I still
have a too much
* you have to keep your variables transient - very easy mistake to make,
otherwise big boo boo might happen if the dependency is serializable and
you
wont know until much later
Why would you want your services serializable?
because some services you are not in control of, they come from
