I really don't have a favorite, yet, because I haven't used an ORM in a client project. I have played around with the upcoming Hibernate and it sure looks great.I am curious to know what everyone's favorite ORM tool is and why you like it over the other ones?
The 1.0.1 spec is finished. I'd suggest browsing JDOCentral.com for further info (the site was down as of this writing).What's the deal with JDO?
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Rick Hightower is CTO of Mammatus which focuses on Cloud Computing, EC2, etc. Rick is invovled in Java CDI and Java EE as well. linkedin,twitter,blog
Originally posted by Rick Hightower:
I've used a few ORMs....
I have used Hibernate on a project or two. It is cool. I don't think I would use anything else.
A big thumbs up for hibernate.
Gavin King rules!
Originally posted by Gregg Bolinger:
You like it that much huh? What are your opinions on the fact that JDO is supposed to be the big thing, and Hibernate is proprietary?
Yes, but the biggest problem with JDO - IT'S NOT ORM it's mapping between text files and objects, nothing more, nothing less.
Originally posted by Ernest Friedman-Hill:
This is a rather tremendous misstatement. JDO is a specification for an abstraction of a queryable data persistence layer. Sun's reference implementation uses flat files just so that it can be a standalone package that doesn't depend on your installing a database...
Offcource one can get all relational optimizations in commertional product's but then - vendor lock in.
Originally posted by Ernest Friedman-Hill:
This makes no sense. The whole point of JDO is that you write your Java code to the spec. ...
...
So all in all, I respectfully submit that you may need to study the matter a bit more closely.
obviously JDOQL need some enchanments
[SCJP, SCWCD, SCBCD, SCEA1, BCD, OCA DBA1]
Originally posted by Ernest Friedman-Hill:
This may be obvious to you, but it starts from the flawed premise that everything does and should look like an RDBMS. If you start designing an application by laying out tables, and the objects are just an afterthought, well, then I can't really argue with you. That's certainly one way to develop software. Not the way I choose to, but it's a way.
If you're using JDO as a transparent persistence mechanism as it's meant to be used, JDOQL shouldn't need to be used much at all; you can write major applications without touching it or any other query language.
A discussion like this one often comes up in the OODBMS vs. RDBMS debates. Do you query for objects, or do you just iterate containers? If you design applications in an RDBMS-oriented way, then an object might contain a flat (indexed) list of a million other objects. In that case, you may indeed need lots of JDOQL, perhaps with enhancements, or SQL, in which case JDO isn't for you.
But if you design object-oriented applications (and indeed, if you are used to designing data structures, rather than just letting an RDBMS hold your data) then you wouldn't design such a thing in the first place. You only need to "find" objects if you "lose" them in the database. If you never lose them in the first place, searching isn't an issue.
I have no java certifications. This makes me a bad programmer. Ignore my post.
Piscis Babelis est parvus, flavus, et hiridicus, et est probabiliter insolitissima raritas in toto mundo.
Matthew Phillips
Originally posted by David O'Meara:
I found that in Jaxor you still coupled your Java code with the database - code still contains tanle names. Its Unit of Work implementation caused us some hiccups since you can't view an object created in the unit of work until it commits, so if anything else needs it, the object doesn't appear to exist. I'm also not a fan of code generation since we normally rely on our own frameworks with our own base classes.
Those who dance are thought mad by those who hear not the music. This tiny ad plays the bagpipes:
Java file APIs (DOC, XLS, PDF, and many more)
https://products.aspose.com/total/java
|