Cemal --
Thanks, the trace indeed looks familiar. I will try the suggestion to
make Bean2 an interface. I will also try to distill a test from this
problem.
Will let you know.
Thanks,
-- Sasha
jWeekend wrote:
Sasha,
Does the trace at the end of this note, in my PS, look familiar?
Now try
this isnt really wicket-specific. this is just something you need to
be aware of when dealing with IOC containers. if you wanted to eg have
transactional methods on this bean you would run into the same problem
as spring would try to create a proxy of your class to manage
transactions (unless you
Igor and all --
I also had this problem when using default constructor and
initialization by properties.
OTOH I have Hibernate DAO classes using transactions, and they work fine.
Good news, the problem went away when I broke the Bean1-Bean2 chain
because of application reasons. If/when the
