Pino Contartese wrote:
> Hy all,
> while testing Helper classes in the module I considere the idea to change
> the default constructor into another one which take Entry object as
> parameter.The reasons are a lot ..at first
> EntryHelper take the summary informations by its Entry for each concrete
> implementation (ListHelper and EntityHelper) why have i to set this
> component every times?
>
> Waiting for your reply.
Hi Pino,
if I don't misunderstand you your proposal is to change the ListHelper
and EntityHelper classes to provide a constructor which sets the object
to be helped on. This is a good approach in my opinion but I wish to
provide some other option to your choice:
- a static class which will be very less memory consuming, but may be
not so helping as you have to pass the List or Entity on each method
- adding those methods directly onto the classes to avoid the
consumption for an additional object, so we can completely drop the
helper classes
Just to remember to other developers, the Helper classes were developed
to ease finding addresses of a specific type as we were not able to
solve the problem through introspection at the business level because of
the Hibernate proxy classes wrapping the addresses.
Can you provide some code examples about the benefit of the changes you
are proposing?
Thank you,
Roberto
|
