This tutorial provides tutorial notes on JVM statistics monitoring tools. Topics include listing JVM processes with 'jps', the JVM remote monitoring server - 'jstatd', Java security policy file, connecting 'jps' and 'jstat' to a remote machine, RMI protocol and URL, getting garbage collection statistics with 'jstat -gcutil'. 'jps' - JVM Process Status Tool

This article provides tutorial notes on using DataSource objects and JNDI to connect Java DB (Derby) Database. Topics include creating connections with ClientDataSource objects directly without JNDI; downloading and installing JNDI File System Service Provider; Binding ClientDataSource objects to JNDI names; Looking up ClientDataSource objects through JNDI.

A transaction is a unit of work that consists of a group of activities performed as a unit such that either all or none of them succeed. Every transaction has a beginning and an end. The process of marking the transaction boundaries is known as transaction demarcation. Transactions either commit or roll back to their initial stage. In EJB, a transaction must pass the ACID test.

KBank chose Elixir Report, which best satisfies all reliability, performance and cost-effectiveness metrics. Elixir Report offers true multi-lingual support, coupled with sophisticated report layout control and a rich set of output format choices, making the report server transition as painless as possible. Built on Java™ technology, Elixir Report runs seamlessly on multiple platforms, allowing KBank to leverage existing IT infrastructure without a mandate for dedicated hardware and software environment.

Jakarta's Digester maps data from an XML source to Java objects. Learn all about this package and its advantages over other similar APIs. Then follow a real life Digester parsing example.

The Internet has no doubt become the most popular source of information today. More and more businesses have adopted the Internet as the vehicle to display their business information, advertise their products, and maintain customer interactions. The activity of developing Web applications occupies a fair amount of resources, time, and effort.

Joe Walnes's XStream is a unique open-source Java library for serializing objects into XML and deserializing that XML into objects. Unlike other APIs, such as David Megginson's XMLWriter or Elliotte Rusty Harold's XOM, which use specific classes and methods to produce XML, XStream relies on Java idioms such as object names to produce element names and strings within classes to produce element content. It also produces a kind of reflection of objects in XML.

The big story in app development for the past few years has been the competition between Microsoft’s .NET Framework and products that support the J2EE specs. Lots of people have talked about it, and many development organizations have been faced with this issue. To a large extent, the .NET vs. J2EE struggle has defined the recent app development landscape.

With demand for Microsoft SQL Server connectivity for Java applications growing steadily, and with many companies migrating their production platform from the 32-bit SQL Server 200 Enterprise Edition to the 64-bit versions of SQL Server 2000 and SQL Server 2005, JNetDirect has added 64-bit support to two of its components.

The previous installments of this column gave you a thorough overview of JAXB, so you're now ready to study varying data binding implementations. This article begins an in-depth look at JaxMe, an open source implementation of JAXB. In addition to offering several enhancements to the basic JAXB specification, JaxMe offers integration with databases and Enterprise JavaBeans, both significant extensions to basic data binding behavior.

As the message of Java's robust health permeated the 2004 JavaOne Developer conference, an underlying message became clear: The opportunities for Java developer entrepreneurship are also alive and well.

Sun Microsystems held it's annual JavaOne conference in San Francisco this year. There was a great turnout and many announcements made during the first two days. For details on each announcement Sun has set up a nice JavaOne website to link you to more detailed information.

In a previous article (XML Basics Part One);we had a brief look at XML. However, as stated in the article, XML itself is worth nothing without the set of APIs that are generated-it would simply be just another fancy form of CSV, that is, a proprietary data format! My aim in this set of articles is not to actually reveal XML in its every detail, but rather have a look at the implications of XML in today’s technologies. That’s why the previous article only sheds a little light into the insights of XML, which included some terms and technologies you will be confronted with the moment you step in the XML arena.

Last time, we learned about JAXP, Xerces, DOM and the javax.xml.parsers Java Package. How about getting a little taste of the SAX interfaces? We look at available classes and interfaces, and learn how to use SAX for XML Processing. Given SAX's power, perhaps we can look forward to the day when we'll be translating not just XML, but maybe even Klingon! Maybe not. Before you get started, you'll want to download the support files for this tutorial.

So far, during this series of articles (part 1, part 2) we've looked at DOM and SAX, and I suppose most of you are thinking which one of the two approaches is preferable? Well, there is no general rule of thumb, but this article might help you make the right decision when you’ll have to.

In the previous lesson entitled Java JAXP, Implementing Default XSLT Behavior in Java , I explained default XSLT behavior, and showed you how to write Java code that mimics default XSLT behavior. The Java program named Dom11 that I developed in that lesson serves as a skeleton for more advanced transformation programs. This lesson updates Dom11 into a new program that tests and exercises several methods that were not tested by the samples used in the previous lesson.

Sometimes you just wish software architects weren't so creative or, at least, were more coordinated. It seems that's what happened with SOAP, the standard format for web services messages. The SOAP specification started out defining a lot of protocol-specific XML structures that now, in hindsight, could obviously better be delegated to the W3C XML Schema language, the whole purpose of which is to define the structure of XML documents. It's a disconnect that the Java community is still working out.

As the name implies, the Java API for XML Processing (JAXP) is an API provided by Sun designed to help you write programs for processing XML documents. JAXP is very important for many reasons, not the least of which is the fact that it is a critical part of the Java Web Services Developer Pack (Java WSDP).

O'Reilly has released the first edition of Java and SOAP. It is a nuts-and-bolts look at what Java developers will need to know in order to take advantage of the Simple Object Access Protocol when building applications that tie together databases or messaging functions.

O'Reilly has released the first edition of Java and SOAP. It is a nuts-and-bolts look at what Java developers will need to know in order to take advantage of the Simple Object Access Protocol when building applications that tie together databases or messaging functions.