The application you are talking about is not really transactional like you
mentionned, but
you could get some payback using EJBs for your project in the following
areas:
- db connection pooling
- scalability, it is easier to scale an EJB based application than a
servlet based app
- using CMP Entity Beans to read your data you would save all the necessary
JDBC code you would need
in your servlets, since the container will generate it
- you will benefit from the caching of your EJB container as well
In order to keep your client as thin as possible I would use a session bean
to encapsulate
your graphing use cases. This session bean would in fact graph the object
using a third party tool.
I would return this graph to your client applet using a servlet and JSPs.
This idea is based on the MVC paradigm coming from Smalltalk:
- use the EJBs as the model
- the servlets serve to control the UI
- the view is implemented using JSP
Alain Dessureault
IBM Canada Ltd
[EMAIL PROTECTED]
"Booth, Peter" <[EMAIL PROTECTED]> on 03/24/99 09:34:05 AM
Please respond to A mailing list for Enterprise JavaBeans development
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (bcc: Alain Dessureault/Ontario/IBM)
Subject: Is this a suitable pilot EJB project?
Hello,
I welcome any opinions on whether the following small project
sounds like a suitable pilot EJB project:
I have an applet that currently uses cgi to connect to a legacy
graphing application on a web server. The graphing application
queries a database and produces line graphs as pdf files.
My project is to replace the legacy graphing app with an N tiered
graphing app. I had initially planned to use servlets to read data via
JDBC and return the time series data to the applet, which would build
the graph objects using a third party tool. The app is not really
transactional
in nature, I am interested in evaluating EJB technology with a project
where there is some pay-off.
Is there any gain in using entity EJBs to read data from a database?
The database stores a historical set of data points and is written to on
a daily basis. A typical graph would involve reading say eight curves
each with 2000 points. There will be perhaps 30 concurrent users.
Would EJB make it any easier to cache commonly used data?
Any opinions welcome.
Peter Booth
[EMAIL PROTECTED]
===========================================================================
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".
