RE: Struts 2 Architecture - Best Practices...

2009-02-26 Thread Mileidys Gonzalez Prieto
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,

RE: Struts 2 Architecture - Best Practices...

2009-02-24 Thread Andy
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:) >

Re: Struts 2 Architecture - Best Practices...

2009-02-24 Thread Burton Rhodes
Thank you for the replies. That is very helpful. Sounds like I will remove all dao into service layer. (Off topic:) Why might you switch back to jdbc as opposed to hibernate. What obstacles are you facing there? On 2/24/09, Andy wrote: > > Right now I am using Struts2, Spring, and Hibernate. A

RE: Struts 2 Architecture - Best Practices...

2009-02-24 Thread Andy
Right now I am using Struts2, Spring, and Hibernate. Although the Spring JdbcTemplate is looking better all the time. I follow this: Action --> Service --> Dao Yes it is more code, but the benefits are in testibility, componentization, and maintenance. I even have this: Action -->

Re: Struts 2 Architecture - Best Practices...

2009-02-24 Thread Lukasz Lenart
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