delicious

This is the first in a series of blog posts aimed at documenting whats involved in setting up a performance test harness from scratch. In my next post, I will show how to deploy these performance tests using Maven 2 and how to automate the process using Bamboo

CSRF vulnerabilities occur when a website allows an authenticated user to perform a sensitive action but does not verify that the user herself is invoking that action. The key to understanding CSRF attacks is to recognize that websites typically don't verify that a request came from an authorized user. Instead they verify only that the request came from the browser of an authorized user. Because browsers run code sent by multiple sites, there is a danger that one site will (unbeknownst to the user) send a request to a second site, and the second site will mistakenly think that the user authorized the request.

Recently I've been blogging extensively on some tips and tricks related to Apache Axis2...

If the client can take some alternate action to recover from the exception, make it a checked exception...Moreover, prefer unchecked exceptions for all programming errors. Never let implementation-specific checked exceptions escalate to the higher layers.

This document is mainly focused on Axis2 client-related technologies and their usage. At the end this article, you should understand the key terminologies and concepts, and most importantly how to use Axis2 client for your SOA applications.

In this article, software architect and AXIOM pioneer Eran Chinthaka gives you an overview of this new approach to XML processing.

Company B has a Web application and now they want to expose some of the business logic as web services to 3rd-party companies. For easy maintenance and convenience, Axis2 has to be bundled within the same WAR file.

The most recent Apache comes with mod_proxy, mod_proxy_balancer and mod_proxy_ajp, which do everything I used mod_jk to do.

It came out recently on infrastructure at apache dot org a little "joke" about mod_jk versus mod_proxy, which is better, and so on...

Accessing Tomcat on Port 80: From example.com:8080 to example.com. By default Tomcat and JBoss run on port 8080. So your Tomcat urls look like http://example.com:8080/index.jsp. There are a few ways ways you can access Tomcat webapps on the regular port 80 so that you do not need the port number in the URL.