You could spend $700

Post #123,716 by tuberculosis 11/2/03 5:31:02 PM 8/21/07 6:01:51 AM Reply	You could spend $700 and buy WebObjects and just use EOF. EOF supports objects that span tables. Multiple classes in the same table. It understands stored procedures and you can specify stored procs to be used for each of the insert, read, update and delete operations. I haven't used Hibernate - it has a lot of mindshare just now and comes bundled with JBOSS. But I'm sick of hand editing dense xml files. Its too hard. Human readable my ass. I like EOF in large part because of the modeling tool. Cayenne is another OR mapper and it also has a modeling tool. Any framework lacking a modeling tool is, IMNSHO, caca. I don't have the patience to use it. OT: Am I the only developer who grows more disgusted daily at the insane amount of inane xml formatted, mostly boilerplate, meta file development I have to do these days in order to get anything done? I don't have any trouble writing the software, its all the other shit I can't keep track of. In Java, you can't escape the creepy feeling. --James Gosling Edited by tuberculosis Aug. 21, 2007, 06:01:51 AM EDT Expand All History
Post #123,721 by admin 11/2/03 5:40:45 PM Reply	CRUD and OR 99% of the business logic for our app is in stored procedures right now. OR mapping doesn't make a lot of sense, since we'd just be specifying a stored procedure to perform an operation (like, "order these bonds at this price"). A mapping layer doesn't add much value on top of that that I can see. It also doesn't help that the database structure isn't exactly the cleanest. We'd spend a lot more time cleaning the structure up to make it presentable for an OR tool. Regarding XML files: I hates them, my precious. We're looking at Struts and whaddayaknow, the pages are mapped to URLs using a bunch of frigging XML files. I'd rather do it in code. The XML isn't any more transparent to non-coders anyway. Regards, -scott anderson "Welcome to Rivendell, Mr. Anderson..."
Post #123,744 by Simon_Jester 11/2/03 9:02:32 PM Reply	XML, Struts and other - now OT Yep, Struts does use XML a lot, especially for the find-forwards. (But, to me at least, it's not TOO bad to do by hand.) But, XML should be (in these instances and IMO) a communication mechanism between 2 programming tools. There are configuration tools for Struts that will create that XML for you. (Camino, et al.) (Note: I have NOT used them.) Used that way, XML is simply a uniform easy way to store data and anyone can write a graphical front end for it. (Sadly...some people seem determined to make it difficult and write this front end in Java....don't ask me why.)
Post #124,492 by dshellman 11/6/03 1:34:55 PM Reply	Don't forget XDoclet (for JBoss, Struts, Hibernate, etc.)

Welcome to IWETHEY!