Tag: web technology

measuring response times

recovery testing

simulating many users

generating many transactions

A browser that uses a plug-in to process user data.

A distributed application where the client program does not process data, but instead passes data for processing to an enterprise bean running on an application server.

An application that cannot be stopped by a firewall.

An application compiled with the -thin option of the javac command.

Special icons for creating the user interface elements for thin clients.

A data module saved to the component area of the database.

A self-contained functional software unit that is assembled into a J2EE application and interfaces with other application components.

A JAR file

Entity bean data survives crashes.

An entity bean represents non-persistent data.

It creates its own JAR file during deployment.

You get authentication code without having to write any.

When you want to be certain your application data persists between program invocations, even in the event of a crash.

If you need to initiate a database transaction.

To process transient data that can be re-created in the event of a crash.

To keep people who do not know how to program from accidentally changing important logic code.

To make the user interface more interesting.

To simplify application deployment.

To prevent malicious programs from gaining access to sensitive information on your database server.

To make the application much easier to update, maintain, and manage.

XML imposes important limitations on the receiving program or tool.

The receiving program or tool can use the XML tagging information to determine how to best handle the incoming data.

XML tags offer an extra level of security.

XML tags specify to the receiving program or tool exactly how to format and display the data.

The thin client.

Deployment descriptors.

The JAR file.

The bean's container

When you implement entity or session bean methods to use SQL commands you provide.

When the bean's container handles data storage and retrieval.

When the J2EE server is never shut down.

When changes to database data are lost during a crash.

By thin clients.

By calls to the database.

By the J2EE server.

By the bean's container.