The net effect is the same: a session bean becomes invalid and an entity bean is
removed from the database.

Mike

Anmol Tiwari wrote:

> Hi all,
>
> Is there any difference between EJBHome.Remove() and EJBObject.Remove()
> method calls ?
>
> Anmol.
>
> Anmol Tiwari
> E-Commerce Team,
> Metamor Global Solutions Limited,
> E-9/12, SDF,
> NEPZ,
> Noida- 201305
> Ph-     91-011-91-4568210-16 (Extn-363)
> E-mail- [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>                 [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>
>         -----Original Message-----
>         From:   Frank Sauer [SMTP:[EMAIL PROTECTED]]
>         Sent:   Tuesday, March 21, 2000 9:26 AM
>         To:     [EMAIL PROTECTED]
>         Subject:        Re: Question about catalog management component
> using EJB
>
>         Sounds like a typical Gemstone/J application. It contains a
> transactional
>         persistent cache, so you can go with the last option you mention,
> except
>         you don't have to develop the cache... Your servlets will have
> access to
>         this so called PCA, and can create/modify/delete java objects in the
> cache
>         and when you want, do a 2 phase commit to the RDBMS as well. The
> GS/J cache
>         as well as the EJBs and JDBC connections are managed by OTS.
>
>         We use GS/J with Session beans, persistent java objects and an RDBMS
> on the
>         third tier. I recommend you check it out at http://www.gemstone.com
>         There are also some whitepapers there as well explaining design
> patterns on
>         how to design J2EE systems using the persistent cache.
>
>         Sorry if this sounds like a  Gemstone plug, if I worked for them I'd
>         enclosed it in <vendor> tags, but I don't, I'm just a satisfied
> customer....
>
>         Frank Sauer
>         The Technical Resource Connection
>         Tampa, FL
>         http://www.trcinc.com
>
>         > -----Original Message-----
>         > From: A mailing list for Enterprise JavaBeans development
>         > [mailto:[EMAIL PROTECTED]]On Behalf Of Yan Jing
>         > Sent: Monday, March 20, 2000 5:26 PM
>         > To: [EMAIL PROTECTED]
>         > Subject: Question about catalog management component using EJB
>         >
>         >
>         > Hi, All,
>         >
>         > I have read this forum for a while and learned a lot from
>         > you. Now I am thinking to redesign my catalog management
>         > component using EJB and hope to get some advises from you.
>         >
>         > I am designing a B2B catalog based net marketplace solution
>         > (not product since I am working for an
>         > Application-Service-Provider company .:)), which supposes
>         > have a huge catalog content and allows buyers to
>         > browse/search the catalog with different price programs from
>         > different sellers, and allows seller or suppliers to change
>         > their catalogs and their price programs. I have three
>         > architectures in mind:
>         >
>         > 1. using JSP ---> Servlet ---> JDBC ---> RDBMS. Do object
>         > cache in both session level and application level. This way
>         > we have to code our own cache system. Perfomance should be
>         > OK. But no cache can share between different JVM, which
>         > increases the database hits. ( I used this architecture in my
>         > previous B2C commerce server product, the number of database
>         > hits was the bottle neck for performance. So I believe the
>         > object caching is neccessary.)
>         >
>         > 2. using JSP ---> Servlet ---> BMP Entity Beans ---> JDBC
>         > ---> RDBMS. This way EJB container will do the object cache
>         > for us. But since the catalog intends to be big (the number
>         > of EJB objects will be huge), I think the overhead from EJB
>         > container will be too much.
>         >
>         > 3. uisng JSP ---> Servlet ---> RMI caching server ---> JDBC
>         > ---> RDBMS. This way, time to market will be problem since we
>         > have to develop that multithreadeed RMI caching server. Also
>         > scalibity will be a protential problem.
>         >
>         > I know there have be many threads in the forum discussing
>         > related issues. But I still hope some of you have being
>         > dealing with the similar problem will give me some advises.
>         >
>         > Thanks in advance.
>         >
>         >
>         > Best,
>         >
>         >
>         > Jing
>         >
>         > ==============================================================
>         > =============
>         > 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".
>
> ===========================================================================
> 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".

--
//////////////////////////////////////////////////////
//
//  Mike Clark
//
//  Clarkware Consulting
//  Enterprise Java Architecture, Design, Development
//
//  http://www.clarkware.com
//  [EMAIL PROTECTED]
//  +1.720.851.2014
//

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