RE: CRUD Operations using Tomcat
Don't think this is directly related to Tomcat, but MDA covers what you requested. Tools like OptimalJ and others could help you out. - John -Original Message- From: Valter G. Nogueira Jr. [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 21, 2004 9:57 AM To: Tomcat Users List Subject: Re: CRUD Operations using Tomcat I have read a lot about Struts, Hibernate and DAO. But these aproachs are too verbose, I mean manually define XML configs, jsp pages, actions... I was looking for some tool which I point to my database schema and it produces the bunch of code. It would be good if it was tied to a data dictionary that could dynamically change checks and labels. Valter - Original Message - From: Wendy Smoak [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Tuesday, July 20, 2004 8:25 PM Subject: Re: CRUD Operations using Tomcat From: Valter G. Nogueira Jr. [EMAIL PROTECTED] I am looking for good ways to implements CRUD ops using Tomcat Having handcrafted jsp/servlets almost identicals seems to be not only boring, but an error prone aproach. How are you doing it now? Do you have JDBC code inside your Servlets? I use Struts, and on that users list we often get the same sort of question, How do I read and write records using Struts? The answer is the same-- you don't. You do your data access in a separate layer of code so that nothing in the Action [or Servlet] even knows that a database exists. There are several options available if you're using JDBC-- I think Hibernate is one? I wrote my own and followed the J2EE Data Access Objects pattern. So in my Actions I have code along the lines of: Person person = personDAO.read( 12345 ); HTH, -- Wendy Smoak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CRUD Operations using Tomcat
I have read a lot about Struts, Hibernate and DAO. But these aproachs are too verbose, I mean manually define XML configs, jsp pages, actions... I was looking for some tool which I point to my database schema and it produces the bunch of code. It would be good if it was tied to a data dictionary that could dynamically change checks and labels. Valter - Original Message - From: Wendy Smoak [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Tuesday, July 20, 2004 8:25 PM Subject: Re: CRUD Operations using Tomcat From: Valter G. Nogueira Jr. [EMAIL PROTECTED] I am looking for good ways to implements CRUD ops using Tomcat Having handcrafted jsp/servlets almost identicals seems to be not only boring, but an error prone aproach. How are you doing it now? Do you have JDBC code inside your Servlets? I use Struts, and on that users list we often get the same sort of question, How do I read and write records using Struts? The answer is the same-- you don't. You do your data access in a separate layer of code so that nothing in the Action [or Servlet] even knows that a database exists. There are several options available if you're using JDBC-- I think Hibernate is one? I wrote my own and followed the J2EE Data Access Objects pattern. So in my Actions I have code along the lines of: Person person = personDAO.read( 12345 ); HTH, -- Wendy Smoak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
OT Re: CRUD Operations using Tomcat
From: Valter G. Nogueira Jr. [EMAIL PROTECTED] I have read a lot about Struts, Hibernate and DAO. But these aproachs are too verbose, I mean manually define XML configs, jsp pages, actions... Cross Struts off that list, it has nothing to do with accessing your data. DAO is a pattern-- some of the existing frameworks implement it, or you can do it yourself. I haven't used Hibernate, but of the three I think it's the closest to what you want. It should get you out of having to worry about when/where to store the information. I was looking for some tool which I point to my database schema and it produces the bunch of code. It would be good if it was tied to a data dictionary that could dynamically change checks and labels. JDO might be what you're looking for: http://jdocentral.com/ http://java.sun.com/products/jdo/index.jsp You're still going to have to do some work up front to configure whatever you choose. -- Wendy Smoak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
CRUD Operations using Tomcat
Hi, I am looking for good ways to implements CRUD ops using Tomcat Having handcrafted jsp/servlets almost identicals seems to be not only boring, but an error prone aproach. Thanks for any advice Valter
Re: CRUD Operations using Tomcat
Valter G. Nogueira Jr. wrote: I am looking for good ways to implements CRUD ops using Tomcat We use Apache Struts to implement the CRUD approach, along with it's DynaActionForms feature. Regards, Graham -- smime.p7s Description: S/MIME Cryptographic Signature
Re: CRUD Operations using Tomcat
From: Valter G. Nogueira Jr. [EMAIL PROTECTED] I am looking for good ways to implements CRUD ops using Tomcat Having handcrafted jsp/servlets almost identicals seems to be not only boring, but an error prone aproach. How are you doing it now? Do you have JDBC code inside your Servlets? I use Struts, and on that users list we often get the same sort of question, How do I read and write records using Struts? The answer is the same-- you don't. You do your data access in a separate layer of code so that nothing in the Action [or Servlet] even knows that a database exists. There are several options available if you're using JDBC-- I think Hibernate is one? I wrote my own and followed the J2EE Data Access Objects pattern. So in my Actions I have code along the lines of: Person person = personDAO.read( 12345 ); HTH, -- Wendy Smoak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
