TopLink works great.  Its been around for years. i.e. bugs have been
worked out , production code !!
The only thing to be said against it, is that in some N.I.H. orgs. it
doesn't put the level of control directly into the developers hands. 
Personally I find it liberating to work on the business problems and
not waste everyone's time with OO to Relation mappings.
 

Tomm Carr wrote:
> 
> Joseph Ottinger wrote:
> 
> > For some reason, your question gives me the screaming meemies. The
> > concept is correct - you'd use bean-managed persistence to access and
> > manipulate (and persist) the data, and the latest EJB specs certainly
> > support crossing individual entities... but the idea of adding high
> > volume to "thousands of xml files" with "complex" in their
> > description... I'm not sure you're going to GET high volume, no matter
> > what you do.
> 
> I agree.  XML makes a very good low-end, transaction-free database.  But
> this seems to be have passed "low-end" quite a while ago.  A good DBMS
> is cheap, even Oracle.  He seems to be pushing a technology way beyond
> its abilities, therefore way beyond its usefulness.  The word that came
> to my mind when reading his description was "fragile."  Which means
> trouble, lots of it, and soon.
> 
> For those who need high-powered persistence, but don't want to (or
> can't) handle the conversion from object to relational, go to the Oracle
> site and look for TopLink.  It is free and looks very impressive.  (I am
> only just now examining it, but so far I like what I see.)
> 
> Tomm
> 
> To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm


To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm

Reply via email to