Start with a Java applet and build a server-based proxy system that uses your browser to access an arbitrary Web service. You'll use JavaScript code to access applet-based information and call a servlet, which retrieves the remote information. Thus, you bypass the same-server restrictions on what an applet can and cannot do.

If you're a Java programmer coming to Dojo with little or no experience of JavaScript, chances are you're going to struggle with some of the concepts that enable it to work. The main concerns with Dojo are that — at the time of writing — it is still in its infancy (version 1.0 was only released in February 2008) and the documentation available is still somewhat limited. This article helps you bridge the gap from Java code to Dojo so that you can get up to speed quickly and use the toolkit when developing your applications.

You don't need to debug Java™ applications on just your local desktop. Learn how to spread around your debugging using different connection types that make up remote debugging. This article explains the features and examples that show how to set up remote application debugging. Remote debugging can be useful for application development, such as developing a program for a low-end machine that cannot host the development platform, or debugging programs on dedicated machines like Web servers, whose services cannot be shut down. Other examples include Java applications running with limited memory or CPU power, such as mobile devices, or developers wanting to separate the application and development environments, etc.

As mobile platforms become increasingly sophisticated, the demand for mobile computing will increase. In this "Introduction to the eSWT mobile extension" series, learn about the embedded Standard Widget Toolkit (eSWT). You can use eSWT to develop native-looking Java™ applications for a variety of mobile phones. In this article, learn how to use more of the mobile controls: MobileShell, SortedList, HyperLink, TextExtension, and TaskTip.

The Hamlet framework was developed to extend Java™ servlets and enforce the separation of content from presentation. In this article, you'll find an additional way to provide dynamic content as René Pawlitzek advances the framework further and refines use of the template engine. Hamlets provide an easily used and easily understood framework for developing Web-based applications. The framework not only supports, but also enforces, the complete separation of content and presentation. Its simple and elegant design does not hide the familiar underlying servlet infrastructure. The framework provides a servlet extension called a Hamlet. A Hamlet uses the Simple API for XML (SAX) to read template files containing presentation. (These template files must contain content that can be parsed by SAX, such as strict HTML, XHTML, or XML.) While a template file is being read, the Hamlet uses a small set of callback functions to dynamically add content to those places in the template that are marked with special tags and IDs.

In the second of the Modular Java series, we'll cover static modularity. We'll describe how to create bundles, how to install them into an OSGi engine and how to set up (versioned) dependencies between bundles. In the next episode, we'll look at dynamic modularity and show how bundles can react to other bundles coming and going.

The whole point of a cloud platform like Google App Engine for Java™ is in being able to imagine, build, and deploy professional-quality killer apps that scale — without breaking the bank or driving yourself insane. In this second part of his three-part introduction to Google App Engine for Java, Rick Hightower takes you beyond the ready-made examples of Part 1 with a step-by-step guide to writing and deploying a simple contact-management application using App Engine for Java.

Google Web Toolkit (GWT) lets you use the Java™ language to implement rich client user interfaces that run in a browser. In this two-part article, David Geary brings you up to speed on the latest version of GWT and shows you how to implement a desktop-like Web application.

Some Java™ applications fail to provide reasonable quality of service despite achieving other performance goals, such as average latency or overall throughput. By introducing pauses or interruptions that aren't under the application's control, the Java language and runtime system can sometimes be responsible for an application's inability to meet service-performance metrics. This article, second in a three-part series, explains the root causes of delays and interruptions in a JVM and describes techniques you can use to mitigate them so that your applications deliver more consistent service quality.

When Java™ serialization is used to exchange information between a client and a server, attackers can try to replace the legitimate serialized stream with malicious data. This article explains the nature of this threat and describes a simple way to protect against it. Find out how to stop the deserialization process as soon as an unexpected Java class is found in the stream.