«

Hello,

I am creating my first web application using Struts 1.3 and Hibernate
in Eclipse. Everything is going reasonably well so far and I have all
the setup complete and I am doing some of my basic functionality such
as login using (jsp -> actionform -> action). However I have a query
about 'best practice', when creating common methods for my users (such
as hashing passwords, checking whether a user exists, formatting
results etc) and where these should go, i.e whether I should create a
pojo for Users, whether this should implement/extend a pre-created
hibernate class (such as users.java, abstractUsers.java or
UsersDAO.java), or whether I should just store them in my Action
Classes and call the class whenever I need to use this method.

Many Thanks
Kate

wrote:
> I am creating my first web application using Struts 1.3 and Hibernate
> in Eclipse. Everything is going reasonably well so far and I have all
> the setup complete and I am doing some of my basic functionality such
> as login using (jsp -> actionform -> action). However I have a query
> about 'best practice', when creating common methods for my users (such
> as hashing passwords, checking whether a user exists, formatting
> results etc) and where these should go, i.e whether I should create a
> pojo for Users, whether this should implement/extend a pre-created
> hibernate class (such as users.java, abstractUsers.java or
> UsersDAO.java), or whether I should just store them in my Action
> Classes and call the class whenever I need to use this method.

In my world:

JSP - presentation layer
action - control layer
what you are talking about - business layer
Hibernate data classes - data access layer

I think you need something between you action classes and
your Hibernate data classes.

Arne