Hi Cyrille, I would suggest a Persistence framework for firing your objects into and out of the database. Something like JDO - a free and highly polished implementation of this is JPox. IMO this will be a lot less bother than having to learn JDBC, which is the basic method of communicating with the database (JPox does the work of translating your calls into JDBC calls).
I would be wary of trying to learn too much at once unless the cost of learning the framework is less than the cost of learning how to do things without the framework. Therefore my minimum framework stack would be : MyFaces to build the UI and map your UI components (textboxes, etc.) to your business logic classes (backing beans) JPox to persist these same business logic objects to the database. This way you use the same class in the middle tier (business logic) to map (1) to the Web page and (2) to the database. Once you have these working you can look at introducing frameworks like Spring, etc. Unfortunately I have not seen Barracuda and so cannot comment on it. HTH, Fintan -----Original Message----- From: Cyrille37 [mailto:[EMAIL PROTECTED] Sent: 12 July 2006 19:38 To: [EMAIL PROTECTED] Cc: MyFaces Discussion; [EMAIL PROTECTED] Subject: [newbie] MyFaces or Barracuda ?? Hello, I'm exploring Java solutions for a new Web Application project. I'm coming from ASP.Net but for the new starting project, the first rule is plateform portability, so Java is the solution. Unfortunately, unlike .Net, Java for Web Application is not delivered as a package. So I've to make an assembly of solutions to get an environment for creating the Web Application. After surfing onto Java/J2EE projects, I've selected some nice stuff : - App Server : Enhydra - Framework : here is my interogation, MyFaces or Barracuda ?? - What else is needed for a strong and well formed Web Application ?? I guess you have opinion on that question ... Please, share your mind ;o) Thanks Cyrille. * ** *** ** * ** *** ** * ** *** ** * This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any views or opinions presented are solely those of the author, and do not necessarily represent those of ESB. If you have received this email in error please notify the sender. Although ESB scans e-mail and attachments for viruses, it does not guarantee that either are virus-free and accepts no liability for any damage sustained as a result of viruses. * ** *** ** * ** *** ** * ** *** ** *
