|
Manoj,
That's
essentially correct. In Forte, Service Objects are created from
classes (typically application business classes) and are then deployed to one or
more servers. They are called Service Objects because they are objects
whose purpose is to provide services to clients. Deployed Service Objects
can be replicated for load balancing and failover as well.
One of
the key differences between Service Objects in Forte and Session Beans in
J2EE is that Service Objects are instantiated when the Forte server starts
running, and they remain in memory until the server is stopped.
Therefore, it was not uncommon to have a Service Object that started separate
threads on start-up to perform batch-type tasks, or a Service Object that was
completely server-based and never required any client interaction.
Contrast this with Session Beans, whose life cycle is very much tied to the
client.
In
general, you should be able to port Service Objects to Stateless Session Beans
without too much difficulty. But it will be important for you to
understand the purpose of each of the Service Objects you port, and what types
of assumptions were made regarding client access, transaction management, etc in
order to be successful. Are you working with anyone who is familiar
with Forte and the particular application you're porting? If not, you may
want to invest some time learning the basic Forte concepts
first.
Good
luck!!
Dale
Dale V.
Georg
To change your membership options, refer to: http://www.sys-con.com/java/list.cfm |
- [jdjlist] Re: Service Objects in Forte !! Georg, Dale
