Wicket with Spring declarative transaction?

You might be able to get this working using AspectJ load-time-weaving but that's a very complex solution for a simple problem.

You might be able to get this working using AspectJ load-time-weaving, but that's a very complex solution for a simple problem. If you need declarative transactions, then I suggest you move the transactional logic from the wicket component down into a Spring bean, and invoke the Spring bean from the wicket object. The Spring bean would have the transactional annotations, and would be proxied correctly by the Spring container.

Yeah, my fault. This simple solution is better. There is no need to exaggerate.

– nablik Jan 13 '10 at 8:16.

I have no experience with Wicket. But is your 'form class' (the one that contains method annotated with @Transactional) Spring managed code? I.e.

Who creates the instances of the class? If it's not, that Spring will not provide @Transactional support (neither will @Autowired work, etc).

Transactional may be used outside Spring container, for example on entity class But I did something wrong, and it doesn't work. – nablik Jan 13 '10 at 8:11 Are you refering to static.springsource. Org/spring/docs/2.0.

X/reference/…. Then yes - you are right, it would add @Transactional support for non-Spring managed code, but all of these classes still have to undergo some kind of processing by Spring (what they call spring-aspects. Jar).

– Grzegorz Oledzki Jan 13 '10 at 10:49 I'm trying to add aspectj processing, but it doesn't work. Any sugestions why? – nablik Jan 13 '10 at 13:03.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.