EJB and ASP

Answer 1

Think of XSL and JSP as the X and Y axis. They approach solving an HTML (or
XML) rendering problem in two different ways. Each has its benefits. When
the primary input is a known flavor of XML, then XSL is definitely a better
way to go.
Cameron Purdy
Tangosol
"Argyn Kuketayev" <[email protected]> wrote in message
news:[email protected]...
I think the best approach would be to use XML and XSL. I didn't work on itfor
production, but I'm going to try.
I would call EJB's from servlet, then put returns in one or more XMLfiles, then
take XSL and convert to anything, say HTML on the fly and send it back to
client's browser.
In this model web designer won't need to care about Java, JavaBeans andJSP tags,
he will get my XML definition and make a XSL.
Jason Jonas wrote:
The best way we have found is:
/->Database
Client->Servlet->EJBs-->Legacy Systems
^ | \->Etcetera
\ |
\---JSP
All client requests are handled by servlets. Servlets perform the
brunt of Java work that would otherwise be in your JSP or a bean. The
servlets, of course, make calls to EJBs. The EJBs carry out all
business logic (e.g. talking to databases, legacy systems...). The
servlets then set attributes in the request and forward the request to
a JSP. The only responsibility the JSP has is presentation. We have
found this reduces the required Java in a JSP down to a manageable
subset that, in some cases, the HTML folks can handle. For instance,
enumerating through a Vector to populate a list box... It doesn't
always work this way, but most of the time.
If client requests first hit a JSP, I would certainly encourage you to
use JavaBeans in an effort to reduce the amount of Java in a JSP to a
manageable amount.
Jason
On Tue, 08 Aug 2000 18:23:13 -0400, Argyn Kuketayev
<[email protected]> wrote:
one more option:
in your JSP call servlets, and they will call EJBs and return java
beans
(simple containers like struct in C/C++) with data.
in this case JSP will be your presentation layer, servlet - controllerand
EJBs - model. you may prefer to wrap all entity EJB calls in astateless
session beans, which will implement your business workflow.
example:
displayItems.jsp has a form with one text field "name" and a button
"search".
when you click a button, it will post a request to ItemListServlet. the
servlet takes "name" parameter, and calls a ItemHome.findByName(String
ItemName) method of Item session EJB. then it processes the returning
Collection, and puts an array with myItems[] into a session andredirects to
another page ItemList.jsp. now, ItemJsp takes an array and populates atable
on the screen. here myItems is a simple java class with public fields,like
C struct.
in this option, your servlets are kind of dispatchers between jsp andEJBs.
>>>
Arda Mirek wrote:
What is the recommended/proven architecture for accessing
EJB through JSP (speed / ease of development / maintainability)?
Is accessing EJBs through JSP a bad idea and is it better to provide
another layer between the two like JavaBeans (JSP -> JavaBeans ->
EJB) ?
>>>>
Speed and scalibility is very important (as usual :)
Thanks.
Arda Mirek