Have a look at Servlets / JSP technology.
Using this implement the Model 2 MVC pattern . In this pattern, the servlets
act as the controller, collecting form input and calling JDBC or EJBs to
perform business logic. They then populate regular JavaBeans (call them
screen beans) and then redirect to a JSP page. The JSP page then uses
standard JSP 1.0 tags to take data out of the JavaBean and display it.
In this Model 2 model, the servlet will not write out HTML and the JSP page
has no code at all at the server side. here is a good article
http://www.javaworld.com/javaworld/jw-12-1999/jw-12-ssj-jspmvc_p.html
This model gives the most open way of separating content and code. It is
also vendor neutral and sticks to standards that the bulk of the industry
are following. What this also gives you is the ability to put separate teams
of different skilled people on to projects. The servlet developers are the
nerds and the JSP page developers are the pony tailed creative guys.
If you want an open source implementation check out Apache/Tomcat. Tomcat is
not ready for production, IMHO. But soon will be. I have heard good reports
of Apache/Jserv in production but it is at a backlevel of the spec.
WebSphere does all this now but is Servlet spec 2.1 and JSP 1.0 compliant.
Tomcat is Servlet 2.2 and JSP 1.1 compliant.
Now this is what I am following because I like open standards. There are
others doing stuff out of servlets using template libraries and the not.
Some of which are open source and some proprietary.
Read Jason Hunter's web site (the soapbox section) for his views on JSPs and
his proposal to use a JSP engine.
http://www.servlets.com/
I don't agree with everything he says.
IBM's WebSphere also bundles in the Lotus XSL processor. IMHO, the most
advanced of the lot with regard to maturity of XML/XSL. In fact, the Apache
Xerces uses the bulk of the code from the IBM parser.
This is very useful, if you have a variety of http devices such as browsers,
set-top boxes, mobile phones etc. and you want to generate HTML, XML, WML,
pdf, doc etc. out at the last minute.
As a final point, the worst thing you can ever do is to have servlets
spewing out HTML or put heavy server side Java code in your JSP. Both are
heavy no no's and will result in unmaintnable applications.
-- Aravind
> -----Original Message-----
> From: Rick Welykochy [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, 4 May 2000 12:37
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: IBM App Dev Kit for Linux
>
>
> Aravind,
>
> A couple more questions if I may, re: IBM dev kit.
>
> We are looking for a Linux-based e-commerce solution for the web
> that allows us to more cleanly separate data from presentation,
> semantics from markup, that kind of thing.
>
> I'm looking at Cocoon, an Apache/XML project, but that solution
> seems a bit immature at the moment.
>
> What experience have you had (if any) [or have any SLUGGERS had]
> with cleanly separating out the content from the HTML presentation,
> and only merging the two at the last possible moment, when the
> pages are being served up?
>
> I understand the noble goals of XML/XSL, but feel the technology has a
> way to go yet. Perhaps Websphere has addressed this issue. Or do
> you find that with Java Servlets you are generating HTML from inside
> the Java classes you write?
>
> I tend to think that open source is a requirement here as well,
> for the obvious reasons of vendor neutrality, permanence, security
> and solution ownership.
>
> Thanks,
> Rick W
>
>
>
>
> --
> Rick Welykochy || Praxis Services
>
>
>
--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to [EMAIL PROTECTED] with
unsubscribe in the text
