|
In my experience, apps that start out with 1 page and 1 bean tend to
end up being much more complex. So even in that case I would recommend
adding Spring en Hibernate to the mix, especially because of the KISS
principal: Removing messy JDBC code and introducing IoC on all levels simplifies a project tremendously. Jurgen Alexandre Poitras schreef: I agree with the previous poster but I would definitly take a look at Spring's JDBCTemplate if I was you, which is very simple and makes your jdbc code much easier to write. Say farewell to your messy exception handling code :) Plus, if you want to switch to iBatis or Hibernate later on, it will be much easier this way.On 3/30/06, Adrian Merrall <[EMAIL PROTECTED]> wrote:If your app really is 1 page and 1 bean (and likely to stay around this size) then I would think adding multiple frameworks is overkill, remember the KISS principal. Some plain java and jdbc is fine. If you are thinking about persistance/data mapping frameworks to replace writing JDBC, don't forget to evaluate Apache iBatis as well as Hibernate. There are some tutorials on the ibatis site under downloads. Regards, Adrian Auckland, NZ On 3/30/06, 101questionjsf <[EMAIL PROTECTED]> wrote:Currently I'm using only myfaces to do my application. Is it advisable to use Spring and Hibernate? Can I proceed without them? Currently, whenever connect to db to do something, I'm writing jdbc statements, not using hibernate. And never use Spring. Only 1 jsp page linked to 1 managed bean. Is my approach alright? or something wrong? -- View this message in context: http://www.nabble.com/Spring%2C-myfaces%2C-hibernate-t1367883.html#a3668253 Sent from the MyFaces - Users forum at Nabble.com.-- Alexandre Poitras Québec, Canada |
begin:vcard fn:Jurgen Lust n:Lust;Jurgen org:Universiteit Gent;Directie ICT adr:gebouw S9;;Krijgslaan 281;Gent;O-VL;9000;Belgium email;internet:[EMAIL PROTECTED] title:Projectleider Java Softwareontwikkeling tel;work:09/2648554 x-mozilla-html:FALSE version:2.1 end:vcard
