|
Written by George Murnock
|
|
Saturday, 01 October 2005 |
Having robust, automated tests running against your Web applications will help you find defects before they reach your production environment. They'll also allow you to implement your fixes and updates quickly, confident that there were no unintended "side-effects" to your changes.
This article describes how to create, execute, and automate Web application tests using HttpUnit, an open-source, request/response-based testing tool built upon the JUnit test framework. We will cover how to use it, some of its limitations, and some advanced practices as they apply to Portal testing. This tutorial assumes basic familiarity with JUnit.
Click here to view the whole article |
|
|
Written by Aftab Mehmood
|
|
Friday, 12 August 2005 |
|
IBM beats Microsoft in developer prouductivity tools. Read out the following article and post your comments.
http://www.branhamgroup.com/tools_study
|
|
Read more...
|
|
|
Written by j2ee 1.4
|
|
Thursday, 21 July 2005 |
|
The J2EE 1.4 Tutorial is a guide to developing enterprise applications for the Java 2 Platform, Enterprise Edition (J2EE) version 1.4. Here we cover all the things you need to know to make the best use of this tutorial.
Who Should Use This Tutorial
This tutorial is intended for programmers who are interested in developing and deploying J2EE 1.4 applications on the Sun Java System Application Server Platform Edition 8.1 2005Q2 UR2.
Prerequisites
Before proceeding with this tutorial you should have a good knowledge of the Java programming language. A good way to get to that point is to work through all the basic and some of the specialized trails in The Java Tutorial, Mary Campione et al., (Addison-Wesley, 2000). In particular, you should be familiar with relational database and security features described in the trails listed in Table 1.
Table 1 Prerequisite Trails in The Java Tutorial
|
Trail |
URL |
|
JDBC |
|
|
Security |
|
How to Read This Tutorial
The J2EE 1.4 platform is quite large, and this tutorial reflects this. However, you don't have to digest everything in it at once.
This tutorial opens with three introductory chapters, which you should read before proceeding to any specific technology area. Chapter 1 covers the J2EE 1.4 platform architecture and APIs along with the Sun Java System Application Server Platform Edition 8.1 2005Q2 UR2. Chapters 2 and 3 cover XML basics and getting started with web applications.
When you have digested the basics, you can delve into one or more of the four main technology areas listed next. Because there are dependencies between some of the chapters, Figure 1 contains a roadmap for navigating through the tutorial.
- The Java XML chapters cover the technologies for developing applications that process XML documents and implement web services components:
- The Java API for XML Processing (JAXP)
- The Java API for XML-based RPC (JAX-RPC)
- SOAP with Attachments API for Java (SAAJ)
- The Java API for XML Registries (JAXR)
- The web-tier technology chapters cover the components used in developing the presentation layer of a J2EE or stand-alone web application:
- Java Servlet
- JavaServer Pages (JSP)
- JavaServer Pages Standard Tag Library (JSTL)
- JavaServer Faces
- web application internationalization and localization
- The Enterprise JavaBeans (EJB) technology chapters cover the components used in developing the business logic of a J2EE application:
- The platform services chapters cover the system services used by all the J2EE component technologies:
- Transactions
- Resource connections
- Security
- Java Message Service
|
|
|
Written by Linux lover
|
|
Friday, 17 June 2005 |
|
With more and more J2EE applications designed and developed on Linux box, I felt it's really a need for me to have an in-depth knowledge about the Linux file system structures. Having browsed quite a few reference about this issue, I extracted below content as the key points to learn Linux file system structures. Hope it's also helpful to all Linux lovers :) |
|
Read more...
|
|
|
Written by Opensource lover
|
|
Monday, 13 June 2005 |
|
Creating a new connection for each user can be time consuming (often requiring multiple seconds of clock time), in order to perform a database transaction that might take milliseconds. Opening a connection per user can be unfeasible in a publicly-hosted Internet application where the number of simultaneous users can be very large. Accordingly, developers often wish to share a "pool" of open connections between all of the application's current users. The number of users actually performing a request at any given time is usually a very small percentage of the total number of active users, and during request processing is the only time that a database connection is required. The application itself logs into the DBMS, and handles any user account issues internally.
There are several Database Connection Pools already available, both within Jakarta products and elsewhere. This Commons package provides an opportunity to coordinate the efforts required to create and maintain an efficient, feature-rich package under the ASF license.
The commons-dbcp package relies on code in the commons-pool package to provide the underlying object pool mechanisms that it utilizes.
Applications can use the commons-dbcp component directly or through the existing interface of their container / supporting framework. For example the Tomcat servlet container presents a DBCP DataSource as a JNDI Datasource. James (Java Apache Mail Enterprise Server) has integrated DBCP into the Avalon framework. A Avalon-style datasource is created by wrapping the DBCP implementation. The pooling logic of DBCP and the configuration found in Avalon's excalibur code is what was needed to create an integrated reliable DataSource.
A beneficial to desktop developer is DBCP doesn't require a web or app server!
For more informaiton, check http://jakarta.apache.org/commons/dbcp/ |
|
Last Updated ( Monday, 13 June 2005 )
|
|
|
|
<< Start < Prev 1 2 3 4 5 6 7 8 Next > End >>
|
| Results 1 - 9 of 66 |
J2EE Weblog 
