The beans would give your clients the ability to just design their own pages
and pull the properties (info) from the bean and display it as they choose.
We use IBM's WebSphere Studio, which has a really nice model for using JSP,
Servlets, and beans together to accomplish sites like this. And don't forget
XML - it is probably exactly what you need as far as just providing data to
the page and letting the end-user of that XML file display it as they wish.
You could develop a standard XML DTD of the data that your company provides
to those clients.
Bill Hines
Hershey Foods
-----Original Message-----
From: Allan Joudrey [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 18, 2000 1:10 PM
To: [EMAIL PROTECTED]
Subject: development decision
Hi all,
I have been following the discussion on "Providing application resources"
and have found it very interesting and helpful. I think a lot of good ideas
came out in the discussion, therefore, I would like to put my current
development plan up for discussion to see if I can receive any input.
The development:
A system that is used by many smaller companies. The mainframe holds all
the user's information. Currently, an applet talks directly to the mainframe
through a package on a linux box. This requires that all the companies use
the same applet, with little ability to change the style to meet their
company profile ( they can change pics only). Many of the companies want to
develop their own unique sites. For this reason (and because I enjoy to work
with servlets ;)) we have decided to go with servlets to process requests
from the users. This will give us the ability to send objects (containing
the user's info) back to an applet or put it in a HTML page. This will make
the companies happy because they can use the applet or make their own pages.
The problem:
My part that I am not overly clear on what direction to proceed is with the
companies that will make their own pages. They will be on our system and the
dynamic data required will be placed in the HTML pages as they are requested
by the users. I have thought of just giving them the required tags and a
servlet will generate the pages dynamically by reading them in from a file.
Someone mentioned that they used this method and when they switched to a jsp
generation method that the speed increased 10 fold. I am new to jsp (really
green) but would look at this if it is a good option. Would this require
that I use beans also, or can I choose between the beans and servlets. Would
beans be an option also ( I am also new to beans but not so green as jsp).
An important point is that it has to be as simple as possible for the
companies to hire site designers to develop their pages, and they can only
receive basic templates of the info that they need to use to get the dynamic
data from the mainframe. Security is the highest issue so we can't give out
to much.
If I haven't mentioned any import points to consider, please let me know.
Any thoughts, and thanks for your input.
Allan
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
