just adding my 2 cents.
I do agree there is no technology which fits all the requirement, I have used Hibernate 2.X and it really is a big help for normal persistance, however on some situations it was a nightmare, I hope they fixed up that in Hibernate3.x. Never worked with IBatis, so can not comment. I think I would still like to have the freedom of writing normal SQL queries while having the flexibility of using a mapping tool. I guess Hibernate does provide that kind of flexibility. However if some one want to go and write their own DAO from scratch, I would suggest them to have a look at Spring's DAO support classes, it can really help at times. I am not an architect by the way. -:) So, I guess I do have freedom to fool around with the technologies. Thanks and Regards, Nitish Kumar -----Original Message----- From: Frank W. Zammetti [mailto:[EMAIL PROTECTED] Sent: Friday, July 22, 2005 7:55 AM To: Struts Users Mailing List Subject: Re: [OT] Hibernate vs. iBatis vs. POJO I'd have to agree... It has not been unusual to estimate three months for something, and that's fairly realistic to do it right, and the business says "nope, 1.5 months is when we need it". Well, what the heck did you ask me for an estimate for in the first place then?!? I'm a lead architect by the way, very much in a position to influence deadlines, but at the end of the day IT is there to service the business, not the other way around (unless you happen to work for an IT company of course!), so, as Martin says, what's unreasonable? Frank Martin Gainty wrote: > What qualifies as unreasonable? ..give the project lead 2 weeks and > he/she cuts it to 2 days? > BTW: Thats 99% of the companies Ive worked for.. > Where specifically do they NOT follow that behaviour? > M- > ----- Original Message ----- From: "Derek Broughton" <[EMAIL PROTECTED]> > To: <user@struts.apache.org> > Sent: Thursday, July 21, 2005 5:25 PM > Subject: Re: [OT] Hibernate vs. iBatis vs. POJO > > >> Frank W. Zammetti wrote: >> >>> In such cases, the application IS important enough to code >>> trials, but the business won't allow you to but they STILL want you to >>> sweat the decisions! This is a typical way of doing things, going by my >>> experience. >> >> >> It depends what _your_ job is. If you're a consultant, you're >> expected to >> _know_ the technology, and the customer isn't paying for you to >> experiment. >> If you're an employee, I've never worked in a situation where you >> don't get >> the time to evaluate the right techniques. >> >>> >>> Even if its the largest initiative of the year for the company, the most >>> important project, there is still a deadline, usually and unreasonable >>> one, and taking the time to properly evaluate options isn't always >>> given. >> >> >> Then go find a new job. There's lots of them for capable people - don't >> work at places that put unreasonable demands on you. >> -- >> derek >> >> >> --------------------------------------------------------------------- >> 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] > > > > > -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com --------------------------------------------------------------------- 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]
