[jdjlist] Re: Service Objects in Forte !!

[manoj]

Hi George, Thanks for ur detailed description...  Unfortunately no one in my team is having working exp with Forte and  we are waiting for the details of the application. So in between we have to deliver some tech comparison matrix between Forte Service object and Java technologies(J2EE) to our client. Based on our study and understanding we have prepared one comparision matrix but from one source we got the response like "No one cannot map service objects to ejbs if you are trying to convert a forte application to j2ee, because a servce object can handle many oebject and when you want to convert a Forte object to Java, you usually convert a object to a EJB.  And because a service object could handle many objects you can end up with making many EJBs" and now we are in confusion. will you pls comment on this.   Also I would very much appreciate if someone elaborates on the difference between a TOOL class with distributed property isAllowed and a Service Object. Can we access a TOOL class with distributed property isAllowed from other server/client partitions     Regards, Manoj ----- Original Message ----- From: Georg, Dale To: 'manoj' Cc: 'JDJList' Sent: Friday, July 05, 2002 9:51 PM Subject: RE: [jdjlist] Service Objects in Forte !! 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              Technical Manager Indus Consultancy Services (201) 261-3100 x229     -----Original Message----- From: manoj [mailto:[EMAIL PROTECTED]] Sent: Friday, July 05, 2002 11:53 AM To: JDJList Subject: [jdjlist] Service Objects in Forte !!   Hi All, I am working on a migration project (from Forte 4GL to J2EE)..... I have one basic doubt regarding the concept and usage of Service Objects in Forte, that is, to perform any business/logical operation based on a client request do we compulsarily need to create a service object for a class ?   Is this Service Object is something like wrapper to a business class to achieve distributed computing in Forte?     Thanks & Regards, Manoj To change your membership options, refer to: http://www.sys-con.com/java/list.cfm To change your membership options, refer to: http://www.sys-con.com/java/list.cfm