• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Com.webobjects.eoaccess package in Direct to Java
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Com.webobjects.eoaccess package in Direct to Java


  • Subject: Re: Com.webobjects.eoaccess package in Direct to Java
  • From: Ray Ackland <email@hidden>
  • Date: Thu, 6 May 2004 08:41:24 +1200

Yves,

As it says on page 53 in the (severely outdated) pdf book "WODesktopApps":

"The EOAccess layer (com.webobjects.eoaccess) is directly responsible for communicating with the data store and for registering enterprise objects with the EOControl layer. It exists only on the server and provides these functions: * generates SQL to fetch data from and commit data to data stores
* manages the communication chain between the data store and the control layer
* manages model files, which define the object-relational mapping between data stores and Java objects
* provides classes that represent various database elements, such as tables, relationships, stored procedures, and joins
* maps raw data to business objects


EOAccess provides an elegant way to interact programmatically with data stores in an abstract manner. It is designed to work with all different types of data stores and different data store vendors, so many of its objects are portable to different data access environments. Although EOAccess is an essential element of any WebObjects application, you rarely need to use it programmatically. "

In summary, it is not available on the client side of the project. This means you can import it into server side classes, but not client side ones. As you may realise, this normally means you will need to do two versions of the class file for ones which you want to make use of this package.

I have found this to be sometimes inconvenient, but also good persuasion to do things the proper way without taking tempting shortcuts.

Ray.


On 06/05/2004, at 1:28, Yves Custeau wrote:

Why is the com.webobjects.eoaccess package not available in a Java Client
Application ? How can I import it in my project ?
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.


References: 
 >Com.webobjects.eoaccess package in Direct to Java (From: Yves Custeau <email@hidden>)

  • Prev by Date: Re: Java client launch problem
  • Next by Date: Subcomponents
  • Previous by thread: Com.webobjects.eoaccess package in Direct to Java
  • Next by thread: WO hangs when sending AppleScript
  • Index(es):
    • Date
    • Thread