I.e.,
public class FooDaoImpl
extends HibernateTemplate
implements FooDao // which extends HibernateOperations
{
// some custom Foo dao methods.
}
Perfecto and parsimonious.
bill
On 6/25/07, Massimo Lusetti <[EMAIL PROTECTED]> wrote:
On 6/26/07, Bill Holloway <[EMAIL PROTECTED]>
Thank you Massimo! That got it all solved.
bill
On 6/25/07, Massimo Lusetti <[EMAIL PROTECTED]> wrote:
On 6/26/07, Bill Holloway <[EMAIL PROTECTED]> wrote:
> I have the following DAO pattern:
>
> public class FooDaoImpl
> extends HibernateDaoSupport
> implements FooDao
> {
>
On Mon, Jun 25, 2007 at 06:02:16PM -0500, Bill Holloway wrote:
> I have the following DAO pattern:
>
> public class FooDaoImpl
> extends HibernateDaoSupport
> implements FooDao
> {
> // some custom Foo dao methods.
> }
>
> However, tapestry-ioc spring bean injection injects via inte
On 6/26/07, Bill Holloway <[EMAIL PROTECTED]> wrote:
I have the following DAO pattern:
public class FooDaoImpl
extends HibernateDaoSupport
implements FooDao
{
// some custom Foo dao methods.
}
However, tapestry-ioc spring bean injection injects via interface.
So, none of the
I have the following DAO pattern:
public class FooDaoImpl
extends HibernateDaoSupport
implements FooDao
{
// some custom Foo dao methods.
}
However, tapestry-ioc spring bean injection injects via interface.
So, none of the HibernateDaoSupport or HibernateTemplate methods like
s
