In the Spring-enabled example below, the DAODataProvider object has an
entityClass property. When the user navigates to the DemoPage via the Back
button, the dataProvider and dataProvider.dao properties are available, but
dataProvider.entityClass is null. This is because dataProvider is a proxy
Hi Shu,
We essentially use option 2. Since we use Guice, @Component and @Scope are
unfamiliar to me. (DAODataProvider isn't created/managed by Spring, so why
specify a scope like that?) Aside from those, I don't see any undue
coupling... just an @Inject.
Our general rule is that @Inject'd