Aku, Note that if there is no other service with a service interface like your Session service, then you don't need the <set-service> element in the two service implementations of your DAO services. The Session service should be autowired.
Regards, --knut On 11/15/05, Alexandr Kundirenko <[EMAIL PROTECTED]> wrote: > Hello All, > > I have many DAOs each of them accepts the same Session service: > > <service-point id="PersonDao" interface="forms.IDao"> > <invoke-factory model="singleton"> > <construct class="ForumDao"> > <set-service property="session" service-id="Session"/> > <set-object property="persistentClass" value="class:model.Person" /> > </construct> > </invoke-factory> > </service-point> > > <service-point id="AddressDao" interface="forms.IDao"> > <invoke-factory model="singleton"> > <construct class="AddressDao"> > <set-service property="session" service-id="Session"/> > <set-object property="persistentClass" value="class:model.Address" /> > </construct> > </invoke-factory> > </service-point> > > Is it possible to create some "base" service-point definition with > Session injection and extend all my DAOs from it? > (Analogue for Spring "parent" attribute) > > -- > aku > > > --------------------------------------------------------------------- > 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]
