Re: Struts DB Access :: Best Practices

So, what is your favorite ide? I love these debates. Some of you guys have some really wacky ideas and to be honest it's entertaining. It's a crazy world out their and i'm glad i have all you nutcases to share it with. To be honest there are three persistence solutions that I would currently u

RE: Struts DB Access :: Best Practices

ruts Users Mailing List Subject: Re: Struts DB Access :: Best Practices Nils Liebelt wrote the following on 3/10/2005 3:10 PM: > - You make up your model. I use UML. > - Look for a case tool where you can generate some code. Poseidon is > great. > - Put in the your xdocle

RE: Struts DB Access :: Best Practices

ruts Users Mailing List Subject: Re: Struts DB Access :: Best Practices Nils Liebelt wrote the following on 3/10/2005 3:10 PM: > - You make up your model. I use UML. > - Look for a case tool where you can generate some code. Poseidon is > great. > - Put in the your xdocle

Re: Struts DB Access :: Best Practices

Nils Liebelt wrote the following on 3/10/2005 3:10 PM: - You make up your model. I use UML. - Look for a case tool where you can generate some code. Poseidon is great. - Put in the your xdoclet tags for the mapping. - Put in your xdoclet tags for the form beans. - May be write a couple conversio

RE: Struts DB Access :: Best Practices

Hi all, Here's is a comment from a first time OJB user. I had to do a web project with a quiet large entity relationship model. Many 1toN and MtoN relations. So what do you do?! - You make up your model. I use UML. - Look for a case tool where you can generate some code. Poseidon i

RE: Struts DB Access :: Best Practices

Hi all, Here's is a comment from a first time OJB user. I had to do a web project with a quiet large entity relationship model. Many 1toN and MtoN relations. So what do you do?! - You make up your model. I use UML. - Look for a case tool where you can generate some code. Poseidon i

Re: Struts DB Access :: Best Practices

On 10 Mar 2005, at 13:48, NetSQL wrote: Ex#2: you can create a cursor to give everyone in NYC a raise, and go by row by row. Or you can do a set operation in one command. I allways avoid row by row, and allways try to go for set, as per direction by Celko and others. Your millage may vary. Okay

Re: Struts DB Access :: Best Practices

Scott Lamb wrote: NetSQL wrote: (RowSet is realy a ArrayList of HashMaps. Rows of Columns) What does a ArrayList of HashMaps get you over a java.sql.ResultSet? Collections are lighter and easier to SoA. I look at it like this: -SQL is a Set oriented lang.(row by row processing is exponentialy

Re: Struts DB Access :: Best Practices

On 10 Mar 2005, at 11:55, Scott Lamb wrote: - consistent dynamic sql (from what I see, there are different ways for altering the order and the where clauses..are there others?) There's also the , which is similar to your iterator. Ahh, lost a later draft with more here. There's no general-purpose

Re: Struts DB Access :: Best Practices

I've actually handled this in a previous project by writing a class that implements the ResultSet interface (well, *some* of it anyway). Internally the data gets stored as an ArrayList of HashMaps, so it's completely disconnected, and it's a drop-in replacement any place we would have used a Resul

Re: Struts DB Access :: Best Practices

On Thu, 10 Mar 2005 12:56:04 -0600, Scott Lamb <[EMAIL PROTECTED]> wrote: > NetSQL wrote: > > Even silly JSF uses RowSet as DTO. (RowSet is realy a ArrayList of > > HashMaps. Rows of Columns) > > What does a ArrayList of HashMaps get you over a java.sql.ResultSet? The major disadvantage of using

Re: Struts DB Access :: Best Practices

NetSQL wrote: Even silly JSF uses RowSet as DTO. (RowSet is realy a ArrayList of HashMaps. Rows of Columns) What does a ArrayList of HashMaps get you over a java.sql.ResultSet? I'll tell you a big disadvantage: it keeps everything in memory. What if the result set is large? I look at it like th

RE: Struts DB Access :: Best Practices

Along those lines, I've added an entry to the iBatis Wiki (http://wiki.apache.org/ibatis/). Select "3rd Party Contributions" and review the section "Convert ResultSet to JSTL Result". You can think of JSTL's Result interface as something *similar* to JDBC's CachedRowSet and BeanUtils' RowSetDynaCla

Re: Struts DB Access :: Best Practices

Joe Hertz wrote: The point is... I use ArrayList of Maps now for my DTO,VO and ever as a message object for WS/SOA. Wherever I used to use a bean, now I use a collection, and I like DynaMaps. I think I'm buying what you say in a big kinda way. Cool. I worked for years in an architecture that esc

Re: Struts DB Access :: Best Practices

On 10 Mar 2005, at 07:59, Larry Meadors wrote: Disclosure: I am an iBATIS developer, so I'd like to offer another opinion on the comparison. Cool! I might add an appendix to my documentation with this comparison. When I do, I'll give you another opportunity to complain. :) - iBATIS does database

RE: Struts DB Access :: Best Practices

Vic writes: > :snip: > The point is... I use ArrayList of Maps now for my DTO,VO and ever as a > message object for WS/SOA. > > Wherever I used to use a bean, now I use a collection, and I like > DynaMaps. > > maybe one day you guys catch up;-) I think I'm buying what you say in a big kinda way

RE: Struts DB Access :: Best Practices

Vic writes: > :snip: > The point is... I use ArrayList of Maps now for my DTO,VO and ever as a > message object for WS/SOA. > > Wherever I used to use a bean, now I use a collection, and I like > DynaMaps. > > maybe one day you guys catch up;-) I think I'm buying what you say in a big kinda way

Re: Struts DB Access :: Best Practices

Larry Meadors wrote: - iBATIS has a lot of options to use JavaBeans, which I don't find useful. I just take parameters in a java.util.Map and return a java.sql.ResultSet directly. (I'm a DynaActionForm kind of guy, so using a form bean form this would be a little out of place.) OK, now I have to

Re: Struts DB Access :: Best Practices

Hi karthikeyan, Stick with SQL based persistent frameworks like iBATIS. The learning curve is minimal, expertise is easily available and your application will stand the test of time. Relational databases and SQL are'nt going away any time soon. OR mapping tools are like EJBs, full of hype. They

Re: Struts DB Access :: Best Practices

I agree with Rick. SQL has been around for years and years. IMO, it will outlive most languages we are writing with today because of its wide acceptance. Before using iBATIS, I used Hibernate. In my experience with it, it made the simple things simple, and the difficult things all but impossible.

Re: Struts DB Access :: Best Practices

On Wed, 09 Mar 2005 15:48:52 -0600, Scott Lamb <[EMAIL PROTECTED]> wrote: > karthikeyan balasubramanian wrote: > > I looked at iBATIS, it seems to be simple and easy to use. I will > > also check out > > others and let you know my thoughts. > > I'll add one to your list: Axamol SQL Library >

Re: Struts DB Access :: Best Practices

Jesse Clark wrote the following on 3/9/2005 4:46 PM: However, I would disagree with your earlier comment that Hibernate is very easy to learn. It is a powerful tool and makes life easier once you learn it, but I think realistically you are looking at a 3 to 6 week learning curve to really figure

Re: Struts DB Access :: Best Practices

karthikeyan balasubramanian wrote: I looked at iBATIS, it seems to be simple and easy to use. I will also check out others and let you know my thoughts. I'll add one to your list: Axamol SQL Library It's a project of mine, so I'd love to hear i

Re: Struts DB Access :: Best Practices

I agree that you can use Hibernate to generate code in a top-down or bottom-up approach fairly easily. However, I would disagree with your earlier comment that Hibernate is very easy to learn. It is a powerful tool and makes life easier once you learn it, but I think realistically you are looki

Re: Struts DB Access :: Best Practices

Equinox (http://equinox.dev.java.net) allows you to use Struts+Spring and any of the following persistence engines: Hibernate iBATIS JDO (JPOX) OJB Spring JDBC Personally, I like Hibernate when I get to create my schema, and iBATIS when it already exists. iBATIS is the easiest to learn/use in

Re: Struts DB Access :: Best Practices

Hi all, Thank you all for inputs. Now my list has grown big : 1. Castor 2. JDO 3. iBATIS 4. Hibernate 5. OJB I looked at iBATIS, it seems to be simple and easy to use. I will also check out others and let you know my thoughts. Have a great day. Karthikeyan B On Wed, 09 Mar 2005 11:31:

Re: Struts DB Access :: Best Practices

I do not completely agree here. You can choose from where you come and to where you go using Hibernate. As other approach I only know EJB and here it depends on the tools you have. With xDoclet your start with the class and go to the db over the mappings. Regards Sebastian Hennebrueder ht

RE: Struts DB Access :: Best Practices

i prefer to use OJB for persistence, because i like the approach of coming from the object world and define the mapping to the database, while hibernate (and others) tend to come from the database and help you generate classes. OJB is very easy to use, and you won't see anything related like PK-FK

Re: Struts DB Access :: Best Practices

karthikeyan balasubramanian wrote: I want to know what is the best way to access database using struts. This is just one way: http://www.ibatis.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [

Re: Struts DB Access :: Best Practices

Struts using Hibernate. Hibernate is quite easy to learn and has a large community. Regards Sebastian Hennebrueder http://www.laliluna.de Tutorials for JSP, JavaServer Faces, Struts, Hibernate and EJB karthikeyan balasubramanian wrote: Hi all, I am planning to use Tomcat/Struts/MySQL in my