I think you should go for normal bean.
The external system (a converter which reads data in XML format) is also part of the same application (i.e. in same application server cluster) but independent of main syatem. The converter reads the �dynamic data� from content source (XML format) and converts it and inserts into the database. Static data is not going to the system database. The converter sends directly to the XML repository. An application component reads it from XML repository and sends to the mobile users.
The clients (mobile phones/PDAs) request for the latest data. (There may be thousands of users at time). The main system reads the data from DB and sends to the client as per the request. The rate of change of dynamic data is so high in peak season. Millions of data inserted into the database.
u need to use only servlets which
will serve ur purpose. i think u
must be using some webserver rather
than app. server. if i m right, then
go ahead with servlets only. if u r
sending any dynamic data frm ur PDA/mobile
then u need to think of EJB, provided
appn. is distributed (MAN).
Originally posted by friso dejonge:
i agree you can use servlets. However if you have an ejb container, you might as well use it.
Since your query will invoke a lot of work, you can devide the workload onto adifferent server, and reduce the workload on the servlet container.
That's not a good reason to use EJB. You can get workload management by spraying HTTP requests across a number of web containers that would work just as well, if not better (less additional network traffic).