tryPlease note: If the JVM exits while the try or catch code is being executed, then the finally block will not execute. Likewise, if the thread executing the try or catch code is interrupted or killed, the finally block will not execute even though the application as a whole continues.
{
if (userInput)
{
while (true) ;
}
else
{
System.exit(1);
}
}
finally
{
// what ever you want to clean up
}
Thursday, August 13, 2009
Code in a "finally" clause "may" fail to execute!!!
United States Postal Service web tool kit
The USPS Web Tool Kit Application Program Interfaces (APIs) allow developers of web-based and shrink-wrapped applications access to the on-line services of the United States Postal Service (USPS). They provide easy access to shipping information and services for your customers. By integrating these APIs into your web site, your customers can utilize the functions provided by the USPS without ever leaving your web site. Once the APIs are integrated into your web site, the USPS Shipping API Server communicates over HTTP using XML (Extensible Markup Language).
Implementing these APIs requires experienced programmers who are familiar with Internet and web site development tools and techniques.
This document provides guidance and step-by-step instructions for installing the USPS APIs, as well as fulfilling various administrative requirements. The administrative requirements vary between different APIs (e.g., submitting samples of labels for some APIs, signing a licensing agreement for certain software, etc.), and this document provides guidance to navigate through the process for the API you are implementing. It is imperative that developers read this manual first, as it provides necessary information and procedures prior to use.
There is a Web Tool Kit User’s Guide for each API available at http://www.usps.com/webtools/. These user guides provide information of the XML transactions to the USPS Shipping API server.
Mozilla Firefox and Microsoft Internet Explorer web browsers descended from Netscape Navigator?
Sunday, August 9, 2009
Debate on best framework for developing JEE applications
- Echo
- Struts
- RIFE
- JPublish
- Verge
- Action Framework
- Expresso
- OpenEmcee
- JWAA
- Smile
- Jeenius
- Dovetail
- Japple
- Nacho
- Click
- Cocoon
- SOFIA
- Spring MVC
- JATO
- Niggle
- Shocks
- Bento
- Turbine
- Jaffa
- MyFaces
- JWarp
- Cameleon
- Helma
- Cassandra
- GWT
- Millstone
- Tapestry
- Canyamo
- Folium
- Bishop
- TeaServlet
- jStatemachine
- Scope
- Jacquard
- Chiba
- Genie
- JFormular
- Dinamica
- Baritus
- OXF
- WebWork
- Maverick
- Jucas
- Barracuda
- wingS
- jZonic
- Warfare
- Macaw
- JBanana
- Melati
- Xoplon
- WebOnSwing
- Stripes
- JSF
Saturday, August 8, 2009
Java based Telnet daemon
- Telnet protocol implementation (following specifications, support for NVT, ECHO, TTYPE, NAWS, LINEMODE,NEWENV)
- Terminal I/O with support for various terminal types
- Simple UI toolkit as OO layer on top of the basic terminal I/O (work progress)
- Connection management (host based access and handling of idle connections)
- using the existing main() in the TelnetD class
- instantiating and activating the daemon from within your application.
- Assemble/prepare the properties that resemble your desired configuration.
- Create a TelnetD instance using one of the given factory methods in the TelnetD class (see API docs).
- Start the daemon calling start()
An example is given below, props represents a single Properties instance containing all properties for your desired configuration:
//1. create singleton instanceTelnetD daemon = TelnetD.createTelnetD(props);//2.start servingdaemon.start();