You could have a look at this...
We are too at the same stage..
Keep me updated about the same...
"
At first glance, JavaServer PagesTM (JSP) and Microsoft Active Server
Pages (ASP) technologies have many similarities. Both are designed to
create interactive pages as part of a Web-based application. To a degree,
both enable developers to separate programming logic from page design
through the use of components that are called from the page itself. And
both provide an alternative to creating CGI scripts that makes page
development and deployment easier and faster.[PARA]While JavaServer Pages
technology and Microsoft Active Server Pages are similar in many ways,
there are also a number of differences that exist. And these differences
are just as significant as the similarities, and have far-reaching
implications for the developers who use them as well as the organizations
that adopt them as part of their overall Web-based
architecture.[PARA][PARA]JSP Technology: An Open Approach [PARA]In many
ways, the biggest difference between JSP and ASP technologies lies in the
approach to the software design itself. JSP technology is designed to be
both platform and server independent, created with input from a broader
community of tool, server, and database vendors. In contrast, ASP is a
Microsoft technology that relies primarily on Microsoft
technologies.[PARA]Platform and Server Independence[PARA]JSP technology
adheres to the Write Once, Run AnywhereTM philosophy of the JavaTM
architecture. Instead of being tied to a single platform or vendor, JSP
technology can run on any Web server and is supported by a wide variety
of tools from multiple vendors.[PARA]Because it uses ActiveX controls for
its components, ASP technology is basically restricted to Microsoft
Windows-based platforms. Offered primarily as a feature of Microsoft IIS,
ASP technology does not work easily on a broader range of Web servers
because ActiveX objects are platform specific.[PARA]Although ASP
technology is available on other platforms through third-party porting
products, to access components and interact with other services, the
ActiveX objects must be present on the selected platform. If not present,
a bridge to a platform supporting them is required.[PARA]Open Development
Process, Open Source[PARA]Sun developed JSP technology using the Java
Community Process. Since 1995, Sun has used this open process to develop
and revise Java technology and specifications in cooperation with the
international Java community. Working with Sun in the JSP effort are
authoring tool vendors (such as Macromedia), container companies (such as
Apache and Netscape), end users, consultants, and others. Going forward,
Sun is licensing the latest versions of JSP and JavaTM Servlet (JSP 1.1
and Java Servlet 2.2) source code to Apache to be developed and released
under the Apache development process. Apache, Sun, and a number of other
companies and individuals will openly develop a robust reference
implementation (RI) that is freely available to any company or
individual. Additional information can be found at
http://jakarta.apache.org/.[PARA]The JSP application programming
interface (API) has undoubtedly benefited - and will continue to benefit
- from the input of this extended community. In contrast, ASP technology
is a specifically Microsoft initiative, developed in a proprietary
process.[PARA][NL]
ASP Technology JSP Technology
Web Server Microsoft IIS or Personal Web Server
Any Web server,
including Apache, Netscape, and IIS
Platforms Microsoft Windows1
Most popular platforms, including the
Solaris Operating Environment, Microsoft Windows, Mac OS, Linux, and
other UNIX platform implementations
[PARA]1. Accessing other platforms requires third-party ASP porting
products.
[NL][PARA]For a company selecting the components of a growing, Web-based
information architecture, JSP technology provides a flexible, open choice
that works with a wide variety of vendors' tools and reflects industry
input and collaboration.[PARA][PARA]The Developer's Perspective
[PARA]Both ASP and JSP technologies let developers separate content
generation from layout by accessing components from the page. ASP
supports the COM model, while JSP technology provides components based on
JavaBeansTM technology or JSP tags.[PARA]As noted previously, the
differences outweigh the similarities.[PARA]Extensible JSP Tags[PARA]The
first difference apparent to any page author are the JSP tags themselves.
While both ASP and JSP use a combination of tags and scripting to create
dynamic Web pages, JSP technology enables developers to extend the JSP
tags available. JSP developers can create custom tag libraries, so page
authors can access more functionality using XML-like tags and depend less
on scripting. With custom tags, developers can shield page authors from
the complexities of page creation logic and extend key functions to a
broader range of authors.[PARA]Reusability Across
Platforms[PARA]Developers will also notice the focus on reusability. The
JSP components (Enterprise JavaBeansTM, JavaBeans, or custom JSP tags)
are reusable across platforms. An Enterprise JavaBean component accessing
legacy databases can serve distributed systems on both UNIX and Microsoft
Windows platforms. And the tag extension capability of JSP technology
gives developers an easy, XML-like interface for sharing packaged
functionality with page designers throughout the enterprise.[PARA]This
component-based model speeds application development because it enables
developers to: [PARA]* Build quick prototype applications using
lightweight subcomponents, then integrate additional functionality as it
becomes available[PARA]* Leverage work done elsewhere in the organization
and encapsulate it in a JavaBean or Enterprise JavaBean
component[PARA]The Java Advantage[PARA]JSP technology uses the Java
language for scripting, while ASP pages use Microsoft VBScript or
JScript. The Java language is a mature, powerful, and scalable
programming language that provides many benefits over the Basic-based
scripting languages. For example, the Java language provides superior
performance to the interpreted VBScript or JScript languages. Because
they use Java technology and are compiled into Java servlets, JSP pages
provide a gateway to the entire suite of server-side Java libraries for
HTTP-aware applications.[PARA]The Java language makes the developer's job
easier in other ways as well. For example, it helps protect against
system crashes, while ASP applications on Windows NT systems are
susceptible to crashing. The Java language also helps in the area of
memory management by providing protection against memory leaks and
hard-to-find pointer bugs that can slow application deployment. Plus, JSP
provides the robust exception handling necessary for real-world
applications.[PARA]Easier Maintenance[PARA]Applications using JSP
technology are easier to maintain over time than ASP-based applications.
[PARA]* Scripting languages are fine for small applications, but do not
scale well to manage large, complex applications. Because the Java
language is structured, it is easier to build and maintain large, modular
applications with it.[PARA]* JSP technology's emphasis on components over
scripting makes it easier to revise content without affecting logic, or
revise logic without changing content.[PARA]* The Enterprise JavaBeans
architecture encapsulates the enterprise logic, such as database access,
security, and transaction integrity, and isolates it from the application
itself.[PARA]* Because JSP technology is an open, cross-platform
architecture, Web servers, platforms, and other components can be easily
upgraded or switched without affecting JSP-based applications. This makes
JSP suitable for real-world Web applications, where constant change and
growth is the norm.[PARA][NL]
ASP Technology JSP Technology
Reusable, Cross-Platform Components No
JavaBeans, Enterprise
JavaBeans, custom JSP tags
Security Against System Crashes No Yes
Memory Leak Protection No Yes
Scripting Language VBScript, JScript Java
Customizable Tags No Yes
[NL][PARA][PARA]Scalability in the Enterprise [PARA]The Java 2 Platform,
Enterprise Edition (J2EE) is the Java architecture for developing
multitier enterprise applications. As part of J2EE, JSP pages have access
to all J2EE components, including JavaBeans and Enterprise JavaBeans
components and Java servlets. JSP pages are actually compiled into
servlets, so they have all of the benefits of these flexible, server-side
Java applications. The J2EE platform containers manage the complexities
of enterprise applications, including transaction management and resource
pooling.[PARA]JSP pages have access to all of the standard J2EE services,
including: [PARA]* Java Naming and Directory InterfaceTM API[PARA]*
JDBCTM API (communicating with relational databases)[PARA]* JavaMailTM
(classes supporting Java-based mail and messaging applications)[PARA]*
JavaTM Message Service (JMS)[PARA]Through J2EE, JSP pages can interact
with enterprise systems in many ways. J2EE supports two CORBA-compliant
technologies: Java IDL and RMI-IIOP. With Enterprise JavaBeans
technology, JSP pages can access databases using high-level,
object-relational mappings.[PARA]Finally, because JSP technology was
developed through the Java Community Process, it has wide support from
tool, Web server and application server vendors. This enables users and
partners take a best-of-breed approach, selecting the best tools for
their specific applications while protecting their investment in code and
in personnel training.[PARA][NL]
ASP Technology JSP Technology
Compatible with Legacy Databases Yes (COM) Yes (using
JDBC API)
Ability to Integrate with Data Sources Works with any ODBC-compliant
database Works with any ODBC- and JDBC technology-compliant database
Components COM components JavaBeans, Enterprise JavaBeans, or
extensible JSP tags
Extensive Tool Support Yes Yes
[NL][NL]
"
Best Regards,
Deepak Goel.
The e-bistro Group.
Your navigational aid for the future.
Godrej-GE Appliances Ltd.
-----Original Message-----
From: Edward Pearson [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, January 06, 2000 11:06 AM
To: [EMAIL PROTECTED]; Deepak Goel
Subject: JSP vs. ASP
Hello list! This is my first posting and I'm a newbie to JSP. Actually,
I
know very little about it. We're using NT servers and running Active
Server
Pages (ASP) web applications with SQL 7.0 as our back-end database
server,
however, we're not thrilled with the performance. I'm wondering if
anyone
could shed a little light on whether JSP would be a much better choice
than
ASP. Thanks!
Edward Pearson
Web Developer
www.ninthhouse.com
==========================================================================
=
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
