We do something like this in Business Components for Java,
Oracle's Java/XML-based framework for building Java Apps
for EJB, CORBA, and Servlets.
Rather than restricting what comes to the
client to a primary key and a label (ok for poplist
list, but not really a general solution to the
problem) we support fully-remoteable,
fully-updateable, arbitrary SQL views over
your business data which coordinate automatically
with lightweight entity beans that run in
the server (managed by a session bean). These
lightweight, remotable collections (that we call
ViewObjects) can expose selected methods from
the underlying entities to act as a remoteable
facade with just the data you need for the occasion.
Have a read of our technical whitepaper at
http://technet.oracle.com/tech/java
to understand more about how the combination
of the benefits of component-based development
and the flexibility of SQL can work nicely together
without compromise.
________________________________________________________
Steve Muench, BC4J Development Team & XML Evangelist
http://technet.oracle.com/tech/java
http://technet.oracle.com/tech/xml
----- Original Message -----
From: Michael Schuerig <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, November 02, 1999 12:51 AM
Subject: Re: Design Pattern - was Returning Collections - Serializing vs
RemoteObject?
| Jon Ferguson schrieb:
|
| > I think the design would be different dependent on the client. Eg. with
a
| > client application you might want a class implementing the Collection
| > interface that internally does the lookups of 'light-weight' proxies
(which
| > might contain a primary key + label - in many cases the label shown to
the
| > user may be part of the pk). The Collection is serializable and
originally
| > populated server side with the results of you're specific query. The
| > results are that the client can view a simple list of labels but when
they
| > select one and request more information the 'light-weight' proxy first
| > populates itself with the full class then returns the desired info.
|
| This is roughly how we're doing it, too. One difference is that we're
| using EJBObjects instead of primary keys. Is there any reason to prefer
| primary keys?
|
| Michael
|
|
===========================================================================
| To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
| of the message "signoff EJB-INTEREST". For general help, send email to
| [EMAIL PROTECTED] and include in the body of the message "help".
|
|
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
