Trouble is, Visual Age 3.02EE's Access Beans 'stink' when it comes to Entity
Bean associations. I have had no success generating Access Beans for EJB
entity beans with 1-many associations.

In addition, it seems to me that there should be some automated process for
generating an "access model" as opposed to a simple "access bean". The
reason for this is that remote methods which return remote objects (say,
Customer has a method getPurchases(), which returns an enumeration of
Purchase instances, and Customer and Purchase are both EJBs), then the
generated wrapper model should have CustomerAccessBean and
PurchaseAccessBean -- and, further, the getPurchases() method of
CustomerAccessBean should return an Enumeration of PurchaseAccessBean
instances, rather than Purchase instances.

An additional problem with Access Beans is that AccessBean versions do not
(and cannot) implement the remote interface of the entity they extend --
because of the additional exceptions included in every method signature.

In short, if we want a regular Java object model wrapped around an EJB
model, then all the generated associations between the Java wrappers need to
return Java wrappers, not the delegated classes as the EJBs themselves do.
VisualAge does not support this to my knowledge, and for any sizeable,
maintainable object model it seems like a necessity.

Charles May, Programmer/Analyst
AFCO Credit Corp. - Pittsburgh Systems Group
A Mellon Financial Company

(The views represented in this message are my own, and do not necessarily
represent the views of my employer).

> -----Original Message-----
> From: John Earles [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, April 07, 2000 2:31 PM
> Subject:      Re: 'local' entity beans vs dependent objects
>
> >>And of course, it's only in theory so far.
>
> Actually, if I have correctly followed this thread, it is not as radical
> as
> you may think.  IBM's VisualAge for Java 3.0 Enterprise Edition has what
> it
> calls 'Access Beans'.  These wrap either a Session or Entity EJB inside a
> serializable Java Class.  When the bean is instantiated it will lazy
> initialize the EJB, encapsulating the Home lookup, narrowing, and the
> finding or creation step, and providing a pass-through of the remote
> interface methods into the EJB.
>
> John Earles [[EMAIL PROTECTED]]
> Castek Software Factory
> 221 Front Street East
> Toronto, Ontario, Canada
> M5A 1E8
>
> phone: (416) 777-2550 x260
> fax: (416) 777-2551

===========================================================================
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".

Reply via email to