Eclipse provides support for Java program development such as editing, compiling, and debugging, and is readily extensible through its plug-in mechanism. Many have been involved in the development of plug-ins that support the building and launching of embedded applications (with support for various platforms, such as J2ME/MIDP, PocketPC, and PalmOS). This talk will show how applications can be developed, compiled, analyzed, and compressed to fit on really small devices. It will include reports on practical experience, it will provide background information on developing Java applications for resource-constrained environments, and explain what Java standardization processes are under way.

Why a Java technology standard? Why technology communities? This session will explore the circle of adoption and business opportunity from an IT Manager and IT developer perspective, as well as, how Java technology fits into these circles, and the significance of conformance and the 'Write Once, Run Anywhere' promise. This session will also examine the role the Java Community Process (JCP) program plays by carefully focusing on binary compatibility and bringing together the community to agree on standards and the results of this effort - multiple implementations from many sources based on Java technology.

This session will present a collection of programming tips and tricks related to consuming and providing Web services in Java. This collection has been created by a number of developers and consultants and is the result of many real-life project experiences. We will focus on implementation aspects for Web services and not go into any detail on architecture or conceptual issues. In other words, these are the problems that developers face once they have started coding.

Service-oriented architecture, Web services, and J2EE technologies are dramatically changing the ways in which enterprises develop and deploy their Internet-facing applications. Because these applications potentially have a global user base, correctly architecting applications is a particular challenge. A combination of grid computing and utility computing offers a way to provide computing resources when and where they are needed, but developers must factor in certain considerations during design. This session will provide an in-depth overview of three real-world case studies using Grid computing in combination with Web services and J2EE to create Internet-based SOAs. It is designed for application architects and developers, and attendees will learn how applications can be designed to operate in a distributed computing environment such that performance and scalability problems are bypassed during deployment.

This session will provide guidelines, best practices, and a methodology to tackle a problem that is sapping the budgets of enterprise that have invested heavily in J2EE technology - the migration of enterprise applications between J2EE application servers. The strategy and planning for such initiatives is very complex and requires planning in advance. Enterprise applications, once deployed, have a multitude of dependencies, besides the dependency on Java APIs. The drivers for migration can include version upgrades, corporate agenda, maintenance costs, industry alliances, rapid upgrades to the J2EE platform APIs, etc. A planned migration ensures a successful implementation while minimizing the impact. This session will describe a strategy to plan for the migration of large portfolios of applications between application server vendors, between application server versions, and between hardware platforms. Real world examples of how this strategy has been applied in the industry will be provided.

Linux and Apache drove a dramatic change in the server operating system and Web server marketplaces. These areas, dominated by Microsoft and Sun in the late 1990s, now see leading open source alternatives challenging these leaders. But open source's impact doesn't stop there. JBoss, the open source J2EE platform, is becoming the high-volume leader in the J2EE application space. More recently, Mono, the open source implementation of Microsoft .NET, promises to be a main strategic item for Novell. Mono may extend Microsoft's hegemony into Linux and open-source by countering J2EE's cross-platform strategic advantage.

Even though WS-* security standards (WS-Security, WS-Trust, WS-SecureConversation, WS-Policy, etc.) are sufficiently prescriptive on specific security subjects like signing, SOAP message encryption, and request/receive security tokens, they do not provide end-to-end security protocol that Web services can depend on to meet their security requirements. The most significant gap is identity propagation from a Web service into a J2EE container. Current JAX-RPC specification or JSR 109 does not cover this issue. This presentation identifies the gaps and discusses the approaches to plug these gaps. It also discusses implementation of a solution for identity propagation from client to Web service and from Web service to J2EE container.

Web services are ideal for integrating third-party services into your applications. However, SOAP-based Web services are based on the request-response model like most Web sites. To provide finely grained functionalities, the RPC API is often very verbose and requires multiple network round-trips to perform a simple task. That has posed a performance problem and a reliability problem for rich client applications, especially mobile clients that consume those Web services. In this talk, I will discuss how middleware solutions, such as Eclipse RCP and OSGi mobile, can help make Web services more efficient via intelligent client-side proxies. The new generation of lightweight aspect-oriented middleware, such as the JBoss microcontainer, makes it very easy to provision and utilize services in rich clients.

Rich client, thick client, thin client - what are they? What are the benefits of rich client, in particular Java Rich Client? This session presents an overview of the various client technologies, in particular various Java-based rich-client solutions, including Swing/AWT, SWT, and XML. Further, it analyzes the trade-off between these different Java-rich client technologies, and presents real-world case studies to justify the ROI of Java-Rich Client solutions.

Any modern financial trading system is a complex distributed application that runs on multiple platforms and consists of components and services that have to communicate with each other. This presentation is about using JMS and message-oriented middleware as a backbone that provides a fast and reliable delivery mechanism between various components and tiers of such systems. This presentation is based on my real-world experience in design, development, and production support of an application that had to wire together midrange computers with J2EE and LDAP servers, non-Java stock exchange software, and mainframe legacy reporting systems.