Thanks for the reply, Chris.
Your answers:
-The main logic of our application resides in very coarse mediator objects
on the server. There are about two or three dozen of these objects. In
addition, there are many entity type objects that are passed back and forth
from the GUI layer to the Business Logic layer. These entities represent
various business objects - and for the most part contain no logic.
-For the most part, transactions start and end in the service object
(mediator) layer. Client pass all necessary data to the business logic
layer, then get back any results. So the client is not exposed to
transactions.
An issues in wrapping the current application will be accommodating for the
existing business objects. Our current application passes complex data
objects back and forth. The business logic layer which we want to expose
takes and returns business objects that were written in Forte for
parameters. I'm not sure how to best work around this without abstracting
too excessively. Will I want to develop doppelganger objects on the
opposite side of the wire?
I'm currently just trying to feel my way around - see if I can identify
snags before actually hitting them. I don't necessarily have a deep amount
of experience in this type of work, so I'm left looking to outside sources
of information and/or experience to compensate.
Thanks again,
-Dave Ortman
-----Original Message-----
From: Chris Raber [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 22, 2000 1:33 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: EJB & CORBA Case Studies
Dave,
Certainly wrapping is something that is done with EJB and CORBA all the
time. I wonder however if you will face any impedence mismatch problems
between Forte's model and EJB for example. Some questions:
- Does your application have a "service" layer. In other words, do client
interact with the service in a coarse grained invocation manner or fine
grained?
- What is the transaction model of the application? If there is a service
layer, is each high level invocation on it a transaction?
If there is a service layer, and it is transactional, then this should map
nicely to session beans.
If there is a service layer, but it is not transactional, then perhaps you
can use session beans as wrappers and deploy them as tx n ot supported (you
may have to do this anyway since Forte is likely to handle it's own
transactions rather than deegating to the container).
My gut instinct is that wrapping with EJB problably has some impedence
issues. CORBA might make more sense (perhaps with Java helper class wrappers
to provide and easy adaptor layer to Java clients).
Regards,
-Chris.
www.gemstone.com
> -----Original Message-----
> From: Dave Ortman [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, June 21, 2000 9:42 PM
> To: [EMAIL PROTECTED]
> Subject: EJB & CORBA Case Studies
>
> Pardon the intrusion,
>
> I've been charged with the task of prototyping an architecture that will
> make the services of current application available to outside
> applications.
> I was hoping there might be some material available from which I could
> glean
> some inspiration and/or direction.
>
> We currently have a large database type application written entirely in
> Forte. The application was built using a layered architecture -
> segregating
> the GUI, business rules, persistence logic, etc. All of the business
> rules
> are implemented in mediator objects which reside on the server. It is
> these
> objects which we wish to make available to the outside world.
>
> There is a strong interest in moving towards Java for future endeavors.
> As
> such, it is intended that I develop my prototype utilizing EJB and CORBA
> technologies.
>
> I'm sure there are plenty of folks who are attempting similar feats. I
> was
> hoping somebody could point me in the direction of any of these efforts.
> Are there any case studies out there somebody could point me to? Does
> anyone feel like sharing similar experiences?
>
> My main concern is coming to a design that best integrates the two
> technologies (Forte and EJB), while leveraging the two in a manner that
> makes sense.
>
> I'll search the archives for any threads that speak to the above inquiry.
> In the meanwhile, does anyone have any sources I should look to? Have any
> advice to share?
>
> Thanks for your time,
> -Dave Ortman
>
> ==========================================================================
> =
> 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".
