Hi Timo Rantalaiho: > This is fine in normal UI layer pojo classes that you > construct with "new" operator in your own code during the > execution of the application. But in Spring-managed beans > you should get your dependencies in with the normal Spring > mechanisms (@Resource, autowiring or in XML as what you > posted). Wicket should not be used in them. > > By the way, I strongly recommend a domain-driven design, > with domain logic in the domain objects, instead of the > proceduralish / model2-actionish usecases. > > Best wishes, > Timo
omg, thanks for pushing me. I realy thaught SpringBean is a spring class, but it's a wicket class. Shame on me :-( Thanks for the clearification. I will go on with integration. Per --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
