Some advantages of session beans:
1.) Access via RMI. No need for a web server. You can use a Java
thin-client approach. The client is mainly user-interface code. The
session beans contain
some business logic and make use of data access objects that interface to
your legacy application. Rather than using JDBC, the data access objects
communicate directly with your legacy app.
2.) If you need your backend to maintain some state for each user, then you
might want to use stateful session beans. There are other alternatives, of
course.
If transactions aren't important and you mainly need to interface a browser
based application with your legacy application, mainly passing, for example,
form data through to the legacy app with little processing or complex logic,
then servlets may be the simplest and best performing alternative. EJBs
aren't always the best solution.
Original Message:
From: Tahir Awan <[EMAIL PROTECTED]>
To: "'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>
Date: Tue, 2 Oct 2001 12:04:11 -0400
Subject: [JBoss-user] design question
Hi,
(sorry for this rePost but I think someone should be able to answer this).
For a new project, I need to decide whether its suitable to use session
beans or a servlet/jsp approach is enough.
The java application talks to a legacy C++ application and all the
communication is XML over Https.
There's absolutely no requirement to handle transaction and security in java
app (as all is done from legacy app).
Assuming that scalability, fail-over can also be achieved through a decent
servlet engine. Is there any other advantage of using session-beans (entity
beans are already gone as there's no persistance to handle).
Thanks in advance.
~tahir
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
