Women in Technology

Article:		Flawed JDO Points the Way to the "Objectbase"
Subject:		Apples to Apples?
Date:		2002-04-26 18:56:39
From:		gennick
Response to: Apples to Apples?
<blockquote> In effect, you're using a *non-portable* Java only solution to the business problems you're solving with the software you're writing. </blockquote> Ok, I have a question. If I'm using JDO, what happens when I need to access my objects from another language, say C++? With a UDT, the object definition is stored in the database where it is accessible from any language. Isn't that a good thing?

Showing messages 1 through 1 of 1.

• Portability?
  2002-04-30 16:36:58  Donald Bales | [View]
  
  
  Entity behavior that exists only in Java classes is not accessible to anything but Java. So it follows that using JDO against a relational database limits the accessibility of behavior to Java programs only.
  
  My assertion is that having entity behavior exist in the objectbase will make it accessible to all languages that can access the objectbase. For the most part, I believe this is an unpopular idea because it is not a Java only solution. Instead it's a Java and SQL solution. SQL's non-procedural nature is its strength. If an objectbase existed where the definition language and access language was strictly implemented in Java, then many Java programmer's would be very happy. But that technology would be stricly procedural and lack the power of SQL.