On 15.03.2010 01:14, Howard Lewis Ship wrote:
> That's very odd, I can't think of a reason why any of the changes I
> made would change that behavior.
So, to be more precise:

Our application was build mainly using the approach proposed in
http://wiki.apache.org/tapestry/Tapstry5First_project_with_Tapestry5%2C_Spring_and_Hibernate

So according to that we have spring managed beans or services, for example
PersonManager interface and PersonManagerImpl class
PersonDao interface and PersonDaoImpl class
All database related logic is in Dao classes, Manager classes only
control business and transaction logic or simply get the results from
the Dao.

And recently we started to circumvent Spring and build services only
with Tapestry related tools so one such service is for example
EnrollmentService which is bound in AppModule like this:
  binder.bind(EnrollmentService.class, EnrollmentServiceImpl.class);

And it is used in the older spring service PersonDaoImple like this:
  @Inject
  @Autowired
  private EnrollmentService enrollmentService;

So what I described was the case in 5.1.0.5.

So when I switched from 5.1.0.5 to 5.2.0-SNAPSHOT in the pom.xml, I got
the message that it was not able to find the enrollmentService bean.
This was really strange and it was solved with deleteing @Autowired. Now
I don't really understand how does this function at all because the
enrollmentService is not configured in the spring xml.