the need for dao per entity class has gone away with transparent persistence, however there is still a "dao" that is a hibenate session, jpa entitymanager, cayenne context, or whatever.
also, some people still use dao to store finder/batch update methods. -igor On Thu, May 29, 2008 at 6:19 PM, Chris Colman <[EMAIL PROTECTED]> wrote: > Pardon my possible ignorance but didn't the need to use DAOs evaporate > once transparent persistence (eg., Hibernate, JDO) hit the streets a few > years back? > > I always thought the DAO architecture was what we used in the old days > in the absence of mature transparent persistence solutions when we had a > DAO per persistent class to help with the persistence of that class. Now > that persistence is effectively transparent (using Hibernate, JPOX > etc.,) aren't they now redundant? > >> >>> Have you tried with naming the dao to be injected explicitly? i.e. >> >>> >> >>> @SpringBean (name="ProtocolDAO") >> >>> private ProtocolDAO dao; >> >> >> >> Interesting. That seems to get me closer... >> >> >> >> org.springframework.beans.factory.BeanNotOfRequiredTypeException: > Bean >> >> named 'ProtocolDAO' must be of type >> >> [com.vzbi.ncs.argfrp.jpa.netconf.ProtocolDAO], but was actually of > type >> >> [$Proxy30] >> >> >> >> Checking google... > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
