Intrepid optimizers Jack Shirazi and Kirk Pepperdine, Director and CTO of JavaPerformanceTuning.com, follow performance discussions all over the Internet. A recent stop on TheServerSide.com message boards revealed some questions on stress testing and load testing. Jack and Kirk examine this subject in detail and discuss how the right tool can make a load of difference in your results.
The Java language may be the most widely used programming language to rely on garbage collection, but it is by no means the first. Garbage collection has been an integral part of many programming languages, including Lisp, Smalltalk, Eiffel, Haskell, ML, Scheme, and Modula-3, and has been in use since the early 1960s.
All Knowledge Management solutions face the challenge of putting the right information in front of the right people. It's possible to confront this challenge with the right technology. Todd Sundsted demonstrates how to use Java technology, the Java Message Service (JMS) API, and XML to build a messaging infrastructure that routes messages based on their content.
Internet transactions, especially messages, are the lifeblood of e-business. Ensuring their security is a requirement, not a luxury, for sensitive transactions. This article examines the Java technologies that developers can use to bring security to their e-business transactions, whether Internet messages or other types of operations. This article focuses on describing the security requirements and concepts, as well as demonstrating Java security technologies that can be used for authenticating and verifying the integrity of an e-mail message. This article also presents ways in which a message can be kept confidential by enshrouding its contents with secrecy.
Deadlock occurs when two or more threads are blocked while waiting for each other. For example, the first thread is blocked on the second thread, waiting for a resource that the second thread holds. The second thread does not release this resource until it acquires a resource held by the first thread.
A few months ago, developerWorks posted some excerpts from my book, Practical Java, published by Addison-Wesley. I will initially use this column on developerWorks to answer some questions asked by readers and to respond to various comments about the excerpts.
The Sun JDK JavaBeans API provides a framework for defining reusable software components that can be manipulated in a visual builder tool. You may have already read the developerWorks tutorial Designing JavaBeans for visual programming. This article extends your design so that visual builder tools can use reflection, introspection, or both to analyze JavaBeans and consequently to allow users to customize them. It includes an example showing how to add your beans to WebSphere AppletDesigner, where users can customize or manipulate the beans from within the tool itself using property editors or customizers you design.
Have you encountered situations where objects don't appear on top of another control as they should? Read this helpful tip to understand how to control the appearance of objects.
The finally keyword is the best addition to the Java exception handling model over other language's models. The finally construct enables code to execute whether or not an exception occurred. Using finally is good to maintain the internal state of an object and to clean up non-memory resources. Without finally, your code is more convoluted. For example, the following is how you must write code to free non-memory resources without the benefit of finally:
A common misconception exists that parameters in Java are passed by reference. They are not. Parameters are passed by value. The misconception arises from the fact that all object variables are object references. This leads to some unexpected results if you do not understand exactly what is happening.