Hi, some days ago I was also worry about how big is my Struts+Hibernate
project, and a plus... need to grow much more... then, I started to look for
solutions on the web.
I'm using MyEclipse, and it provides a enterprise application that really
looks interesting, I just started to read about that,
24 Feb 2009 14:56:30 -0600
> Subject: Re: Struts 2 Architecture - Best Practices...
> From: burtonrho...@gmail.com
> To: user@struts.apache.org
>
> Thank you for the replies. That is very helpful. Sounds like I will
> remove all dao into service layer.
>
> (Off topic:)
>
: Action --> Service --> JSPso that I can wrap my
> business objects instead of adding formatting functionality, etc directly to
> my nice b.o. pojos.
>
>
>
> That's just how I do it.
>
>
>
>> Date: Tue, 24 Feb 2009 07:42:50 -0600
>> Subject:
Action --> Service --> JSPso that I can wrap my business
objects instead of adding formatting functionality, etc directly to my nice
b.o. pojos.
That's just how I do it.
> Date: Tue, 24 Feb 2009 07:42:50 -0600
> Subject: Struts 2 Architecture - Best Practices...
> Fr
2009/2/24 Burton Rhodes :
> Also, would love to know any naming conventions or class organization
> structure you use (e.g. com.[company].action.*,.
> com.[company].service.*,. com.[company].entity.*,.
> com.[company].doa.*, etc) .
Maybe it will be better something like this:
com...model || domai
I am curious to know what structure many of you use to organize and
separate your struts apps. I can't seem to find a "standard" in this
regard. I started with a simple application, and of course, it has
grown to where more separation of logic layers is a must. Right now I
have Presentation Laye
6 matches
Mail list logo
