That's not the only way it will work. You can use an aspect to weave
that behavior into your class also.
On Fri, Aug 22, 2008 at 8:26 AM, Markus <[EMAIL PROTECTED]> wrote:
>>Correct me if I'm wrong but the transactional weaving that you are
>>trying to advise will only work if Spring can see them
>Correct me if I'm wrong but the transactional weaving that you are
>trying to advise will only work if Spring can see them in its object
>factory (i.e. constructed within spring) - which I suspect is the
>case. Perhaps having spring managed service beans and proxy those in
>wicket using the @Sprin
How are you configuring Spring within Wicket?
Correct me if I'm wrong but the transactional weaving that you are
trying to advise will only work if Spring can see them in its object
factory (i.e. constructed within spring) - which I suspect is the
case. Perhaps having spring managed service beans
Hi all,
I am using Spring, Hibernate @ MySQL with InnoDB-Tables with a JDBC-Spy in
between and Wicket.
Deactivating the Spy changes nothing.
I am using following Dialect: org.hibernate.dialect.MySQL5InnoDBDialect.
My SpringConfig-Part:
