You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Leandro Rodrigo Saad Cruz <le...@ibnetwork.com.br> on 2001/05/04 21:51:51 UTC
[PROPOSAL] Add common interface to various managers
Hi all.
Every time I use torque to generate my classes I end up coding one
Manager to each OM class created.
I've been thinking if torque could generate all this managers too.
they would have an interface like this
XXXManager
{
/**
* all this methods could use an internal cache
* and we could syncronize it to the BackEnd using a Thread or
everytime a modification is made
*/
public List getXXXs();
public void addXXX(XXX);
public void removeXXX(XXX);
public void updateXXX(XXX);
public boolean xxxExist(XXX);
public boolean xxxExist(Criteria criteria);
...
}
I don't know if this is valid and if you have the same needs I have
(Coding Managers and ApplicationTools)
if you have different approaches please let me know.
--
Leandro Rodrigo Saad Cruz
InterBusiness Tecnolgia e Servicos
http://www.ibnetwork.com.br
telefone 4191-3638
Sao Paulo - SP - Brasil
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: [PROPOSAL] Add common interface to various managers
Posted by Leandro Rodrigo Saad Cruz <le...@ibnetwork.com.br>.
I'm not sure, but I think that there are some advantages if we could
count on the presence
of some managers around.
We could provide manager based insertions and deletions that cascade
through all related objects
controling transaction issues,talking to each other.
Another point, if you transfer the knowledge to the managers, you could
provide various cache and syncronization
to you service, something that om objects shouldn't be aware off.
I agree with you there are some objects that don't
require a specific manager, but you don't have to use them directly.
Eric Dobbs wrote:
>
> I would want to have some control over which generated classes
> include a Manager. We have been writing services to provide
> these management methods for the main objects in our model.
> But there are many support objects that don't warrant a
> managing service of their own.
>
> On Friday, May 4, 2001, at 01:51 PM, Leandro Rodrigo Saad Cruz wrote:
>
> > Hi all.
> > Every time I use torque to generate my classes I end up coding one
> > Manager to each OM class created.
> > I've been thinking if torque could generate all this managers too.
> > they would have an interface like this
> > XXXManager
> > {
> > /**
> > * all this methods could use an internal cache
> > * and we could syncronize it to the BackEnd using a Thread or
> > everytime a modification is made
> > */
> > public List getXXXs();
> > public void addXXX(XXX);
> > public void removeXXX(XXX);
> > public void updateXXX(XXX);
> > public boolean xxxExist(XXX);
> > public boolean xxxExist(Criteria criteria);
> > ...
> > }
> > I don't know if this is valid and if you have the same needs I have
> > (Coding Managers and ApplicationTools)
> > if you have different approaches please let me know.
> >
> > --
> > Leandro Rodrigo Saad Cruz
> >
> > InterBusiness Tecnolgia e Servicos
> > http://www.ibnetwork.com.br
> > telefone 4191-3638
> > Sao Paulo - SP - Brasil
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
--
Leandro Rodrigo Saad Cruz
InterBusiness Tecnolgia e Servicos
http://www.ibnetwork.com.br
telefone 4191-3638
Sao Paulo - SP - Brasil
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: [PROPOSAL] Add common interface to various managers
Posted by Eric Dobbs <er...@dobbse.net>.
I would want to have some control over which generated classes
include a Manager. We have been writing services to provide
these management methods for the main objects in our model.
But there are many support objects that don't warrant a
managing service of their own.
On Friday, May 4, 2001, at 01:51 PM, Leandro Rodrigo Saad Cruz wrote:
> Hi all.
> Every time I use torque to generate my classes I end up coding one
> Manager to each OM class created.
> I've been thinking if torque could generate all this managers too.
> they would have an interface like this
> XXXManager
> {
> /**
> * all this methods could use an internal cache
> * and we could syncronize it to the BackEnd using a Thread or
> everytime a modification is made
> */
> public List getXXXs();
> public void addXXX(XXX);
> public void removeXXX(XXX);
> public void updateXXX(XXX);
> public boolean xxxExist(XXX);
> public boolean xxxExist(Criteria criteria);
> ...
> }
> I don't know if this is valid and if you have the same needs I have
> (Coding Managers and ApplicationTools)
> if you have different approaches please let me know.
>
> --
> Leandro Rodrigo Saad Cruz
>
> InterBusiness Tecnolgia e Servicos
> http://www.ibnetwork.com.br
> telefone 4191-3638
> Sao Paulo - SP - Brasil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org