Data processing: software development – installation – and managem – Software program development tool – Managing software components
Reexamination Certificate
2000-08-24
2003-12-16
Ingberg, Todd (Department: 2124)
Data processing: software development, installation, and managem
Software program development tool
Managing software components
Reexamination Certificate
active
06665861
ABSTRACT:
BACKGROUND OF THE INVENTION
1. Technical Field
The present invention is directed to an apparatus and method for providing metadata for the creation of semi-deployed enterprise Java beans. In particular, the present invention is directed to an apparatus and method for including, in a Java Archive (JAR) file, such metadata as to provide an enterprise Java bean with deployment information to aid in deployment of the undeployed enterprise Java bean.
2. Description of Related Art
Enterprise Java beans (EJBs) are components in the Java programming language (Java is a trademark of Sun Microsystems, Inc.) used when building a distributed transaction-oriented enterprise application. EJB systems allow developers to focus on the actual business architecture of a business model, rather than worry about endless amounts of programing and coding needed to connect all the working parts. This task is left to EJB server vendors. Developers just design (or purchase) the needed EJB components and arrange them on the server. Because ETB systems are written in Java, they are platform independent. Being object oriented, they can be implemented into existed systems with little or no recompiling and configuring.
The EJB standard defines a number of roles and scenarios that are used to define the content and capability of the EJB through various stages in its development. An EJB is initially created with business logic but no knowledge of how its persistence will be managed. Such a bean is known as an “undeployed” EJB. The mapping between the persistent fields of an “undeployed” EJB and a persistent storage, such as a database, is completed at a separate time. This mapping requires additional code to be generated. The resulting Java code created based on the undeployed EJB and the additional code generated to map to a specific persistent storage and run in a specific container is known as a “deployed” EJB.
The separation of these stages is intentional and has two key benefits. First, it allows domain specific experts to concentrate their roles. Thus, the bean provider is an application domain expert who does not need to program transactions, concurrency or other runtime infrastructure into the EJB. Likewise, the deployer is an expert in a specific operational environment who must generate the additional classes to manage the EJB at runtime.
Second, it provides for portability of the undeployed bean onto any compliant server. It is possible to purchase undeployed EJBs from other companies and then deploy them into the application server of choice. The undeployed EJB will have no knowledge of the server in which it will eventually run.
The problem with this separation is that it provides no intermediate position. In other words, if an EJB creator does have information such as how an EJB's persistent fields should be mapped to a data storage, there is no mechanism to indicate this in the EJB short of creating a deployed bean. However, a deployed bean is specific to one server, which prevents the bean from being portable across servers.
Thus, it would be beneficial to have an apparatus and method for creating semi-deployed enterprise Java beans incorporating the business logic and some additional information that may be used to aid the deployment or execution of the enterprise Java bean, while the undeployed enterprise Java bean still remains portable to other server environments.
SUMMARY OF THE INVENTION
The present invention provides an apparatus, method, and system for generating semi-deployed enterprise java beans. The apparatus, method and system make use of metadata to identify an intended deployment of an undeployed enterprise java bean. The metadata may be packaged with the undeployed enterprise java bean into a java archive file which is provided to a deployment tool either on the same computing device or a different computing device. The deployment tool may make use of the metadata when generating deployment classes for the undeployed enterprise java bean. However, if the deployment tool is unable to recognize the metadata or the use of the metadata is not wanted, the deployment tool may also deploy the undeployed enterprise java bean in a conventional manner.
REFERENCES:
patent: 5937409 (1999-08-01), Wetherbee
patent: 5991534 (1999-11-01), Hamilton et al.
patent: 6023271 (2000-02-01), Quaeler-Bock et al.
patent: 6026405 (2000-02-01), Arda et al.
patent: 6167453 (2000-12-01), Becker et al.
patent: 6237135 (2001-05-01), Timbol
patent: 6269373 (2001-07-01), Apte et al.
patent: 6502112 (2002-12-01), Baisley
Francis Timothy Marc
Rich Lawrence Scott
Carstens, Yee & Cahoon
Clay A. Bruce
Ingberg Todd
International Business Machines - Corporation
Shrader Lawrence J
LandOfFree
Apparatus and method for providing metadata for the creation... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Apparatus and method for providing metadata for the creation..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Apparatus and method for providing metadata for the creation... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3127139