Hi,
The use of Plain Vanilla Java Objects is very much justified in the scenario put
forward by you.
There are many Factors that favour the use of POJO's over Session Bean ,Let me try and
summarize them.
1) Since the operations stretch over a long period of time ,hence the use of EJB is
not Justified at all
as this will led to timeouts of EJB's.
My suugestion is to process these operations in a pure Java Only environmnet and not
hosting them in EJB based environment.
-----Original Message-----
From: Kalra, Ashwani [mailto:[EMAIL PROTECTED]
Sent: Wed 17/12/2003 10:22
To: [EMAIL PROTECTED]
Cc:
Subject: Re: Messaging Bean
you will not gain much on using session beans. Can you give more details on
what you will be doing in the java classes?
Pooling and transaction is provided for MDBs also. if you are doing lot of
CRUD operations, than use of Entity EJBs should improve scalability.
/Regds
Ashwani
-----Original Message-----
From: Sachin Tandon [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 16, 2003 9:59 PM
To: [EMAIL PROTECTED]
Subject: Messaging Bean
Hi
We are using Messaging Beans on our project. The message bean in turn
will be calling different java classes for performing some actions.
The java classes will be having business logic and will access the DB.
We will process billions of records.
I wanted to decide on using EJBs against normal java classes in this
scenario.
1) Billions of rows of data to be processed
2) Lots of calculation involved in processing data
3) Weblogic clustering - need to load balance requests received
by MDB across instances.
Any thoughts? What do we loose when we use normal java classes in this
scenario as against using session beans
Thanks
=========================================================================== 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".
