Deployathon FAQ

Print-friendly Version

Articles Index

Introduction | FAQ | Read Me | Download

Was this a compatibility or performance test kit for Enterprise JavaBeans^TM (EJB) servers?

No. The purpose of this exercise was to assess how portable the current Enterprise JavaBeans component implementations are, using a simple yet realistic set of EJB components. This application was built to demonstrate portability, and should not be used as compatibility or performance test kit.

Is the manifest file provided with the jar files correct?

No. This was meant for our specific exercise, so yours will need to change. See the section Deployment Descriptors in the Read Me. Recreate the jar file with the new manifest file that has Enterprise-Bean: True and is associated with the name of the serialized deployment descriptor.

What does example.props do?

The example.props file provides a way to define server specific properties. Modify the example.props file to suit the vendor's needs. Save it as <vendor name>.props.

What does the resMgrSupport flag do in the deployment descriptor?

This flag, when set to false, generates an explicit commit after each database call; it guarantees that the changes are stored permanently. In this case, the transactional flag in the deployment descriptor should be set to TX_NOT_SUPPORTED. We have selected Oracle DB as the Resource Manager for this exercise. Some EJB servers are able to interact with Oracle DB as a Resource Manager, and demarcate transactions based on the corresponding deployment descriptor attribute. Other EJB servers might not.

Will this work for other vendors' databases?

We selected Oracle DB for this exercise to limit testing efforts. In the near future we plan to eliminate this restriction, as it really is not appropriate.

Does this application support the JDBC 2.0 specification?

No. For this exercise we have followed the JDBC1.x specification.

Does this application support entity beans?

Yes. The DealerCar bean is an entity bean (entity beans are optional in EJB 1.0 spec).

Does this application support Container-Managed persistence?

No. For this application we have provided only Bean-Managed Persistence.

Why do I get a PortableRemoteObject exception?

You need to ensure you have either the supplied por.jar in your classpath or the rmi-iiop distribution in your classpath. You can download the rmi-iiop classes from the RMI-IIOP home page. If your container uses IIOP for the client/server protocol then you will not require either of these sets of classes.

Will the source code be made public?

We want to get source and tutorial information into the hands of developers, but when and how we can give out source code needs to be determined.

Will there be an EJB 1.1 version of this code?

It is likely that there will be an EJB 1.1 version of the Deployathon code; again this needs to be determined.

Back to Top
Introduction
FAQ
Read Me
Download