Skip to content
Free planNo credit card requiredStart writing
AI for Research home
AI for Research home
Dashboard
Sign inGet started

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 516 papers for “JavaBeans”

Role Separation with JavaBeans

Andrew Patzer · Apress eBooks · 2004

As programmers, designing web pages is not our forte. Although some of us may have modest design skills, web pages are much better left to those who make a living from designing eye-popping, user-friendly, browser-independent websites. On the other hand, most good web designers have little, if any, programming skills. Therefore, how can you expect to build good web applications that not only function well but also have an appealing interface?KeywordsAccessor MethodPage RequestScope AttributePage DesignerPublic VoidThese keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Cited by 0

CICS and Enterprise JavaBeans

Andrew Bainbridge, John Colgrave, Adrian Colyer et al. · IBM Systems Journal · 2001

IBM is supporting Enterprise JavaBeans™ (EJB) across its application server products. Together with related Java™ technologies, EJB provides a standard programming model and set of services across major server platforms. This paper presents an overview of the EJB architecture and describes the technical strategy and design approach for the EJB capability that is being delivered in the latest release of the Customer Information Control System (CICS®). It explores why CICS customers want to use enterprise Java technology, identifies some critical success factors for the CICS support of EJB, and explains its architecture in terms of a portable EJB container executing within the existing CICS run-time infrastructure, focusing on aspects such as transaction management, Java virtual machine reuse, and workload management. Application development tooling is then discussed, together with the strategy for exploiting tools such as VisualAge® for Java. Finally, the paper con siders future work and challenges for CICS in this area.

Cited by 3

JavaBeans and Software Architecture

Nenad Medvidovic, Ph. D, Nikunj R. Mehta et al. · 2003

Windowing Toolkit (AWT) ................. 30 Java Database Connectivity (JDBC) ...................... 30 JavaMail ............................................ 31 Java Management Extensions (JMX) ..................... 31 5 Java and Architecture-Based Software Development ................. 32 Concepts of Software Architectures ...................... 32 Support for Architecture in JavaBeans and Related Technologies 33 6 Summary and Conclusions ...................................... 35 GLOSSARY Architecture-based software development: An approach to software development where the architecture of the software system forms the blueprint for its development and evolution Architecture style: A set of rules that describe or constrain the organization of components and connectors and the manner in which components interact Asynchronous: A mode of interaction where the initiator continues with its processing while the target of interaction is processing the interaction request Container: A software program or runtime environment that provides necessary infrastructure facilities and services such as communication, multi-threading, security and transactional isolation to other software systems Deployment: The process whereby software is installed into an operational environment Design-time: The state and behavior of a software component while it is being composed in a system Enterprise application: An application that comprises an enterprise's systems for handling company-wide infor- mation Event: An occurrence of an incident of interest to a software system Listener: A software component that receives and processes events Middleware: Middleware is software used to provide standard interface to low-level operating system and network services, and a runti...

Cited by 0

Enterprise JavaBeans Benchmarking 1

Marek Procházka, Petr T Ma, Radek Pospíšil · 2008

Enterprise JavaBeans (EJB) is an emerging standard of a support platform for distributed multitier applications written in Java. Since the introduction of the standard in 1998, a number of EJB implementations became available, differing in many aspects from the level of standard compliance to the delivered performance. This prompted a demand for evaluation and comparison of the EJB implementations. In response, we have defined an EJB test suite and carried out a comprehensive evaluation of several EJB implementations as a part of the EJB Comparison Project [2]. The purpose of this paper is to share the experience gathered during the evaluation process, and to outline some of the pitfalls that make the evaluation difficult.

Cited by 0

KEYWORDS USING JAVABEANS TO TEACH SIMULATION AND USING SIMULATION TO TEACH JAVABEANS

Herbert Praehofer, Johannes Sametinger, Alois Stritzinger · 2008

Beans, general systems theory This work reports on two courses for computer scientists. The first is a graduate course on modeling and simulation and the second is a course on component based software engineering. For both of these courses we principally use the same basis, that is, the Java Beans component technology and the DEVS system theory formalism for discrete event simulation. However, in the two coursed, we pursue quite different objectives. While in the first course the Java Beans technology is used to teach discrete event simulation, in the second course we use simulation as an example to show how a component library can be realized using Java Beans. MODELLING AND SIMULATION COURSE

Cited by 0

Streamlined Alogrithm Deployment via JavaBeans.

Patrick Chisan Hew · The Journal of Object Technology · 2002

This paper introduces JavaBean Calculation Engines (JBCEs), a procedure for deploying algorithms in a standard JavaBean framework. For the algorithm developer, JBCEs are a finishing point for deploying an algorithm as a "qualified product". For the GUI developer, JBCEs shield internal computations behind a JavaBean interface. By standardising the interface between computational and GUI code, JBCEs improve reusability and maintainability.

Cited by 1Open access

Component Migration with Enterprise JavaBeans

M. Richmond · 2000

INTRODUCTION Currently available component infrastructure frameworks such as CORBA[3], DCOM[6] and Enterprise JavaBeans[7] support distributed applications by providing a transparent communication mechanism between components across hosts. Existing distribution support implicitly prevents a component's re-distribution after binding: these frameworks prevent a component from being moved once the application has started running. Distributed applications often have a relatively long execution time so they need to adapt to changing application loads and usage patterns. Such applications require the ability to move components at any time during the application's execution. 2. DISTRIBUTION SUPPORT Without dynamic support for these changes it is necessary to restart the application when structural changes are made. We have developed the following taxonomy[4] to consider the possible alternatives in specifying the location of components in an application: Static con

Cited by 2

Advanced Transactions in Enterprise JavaBeans

Marek Prochazka · 2000

. Enterprise JavaBeans (EJB) is a new technology that aims at supporting distributed transactional component-based applications written in Java. In recent years, a lot of new advanced software applications have arisen, which have new requirements for transaction processing. Since EJB is modern concept that deals with transactions, the paper discusses the support of EJB for those requirements for advanced transactions and identifies weaknesses of transactions in EJB. The paper also proposes an extension of the current transactional concepts in EJB, which can be a remedy for some of the weaknesses identified. The extension, called Bourgogne transactions, allows a transaction to delegate bean objects to other transactions, to share bean objects with other transactions, and to establish flow control dependencies between transactions. Implementation issues together with pitfalls of the proposed extension are discussed. 1 1

Cited by 1

Extending Transactions in Enterprise JavaBeans

Marek Prochazka · 2000

Enterprise JavaBeans (EJB) is a new technology that aims at supporting distributed component-based applications written in Java. Since distributed electronic transactions are one of the frequent applications of EJB, the paper discusses the EJB support for advanced transactional applications and proposes an extension of the current transactional concepts in EJB. The extension, Bourgogne transactions, allows a transaction to delegate bean objects to transactions, to share bean objects with other transactions, and to establish flow control dependencies between transactions. Implementation issues together with pitfalls of the proposed extension are discussed. Keywords: Enterprise JavaBeans, transactions, advanced transaction models, Bourgogne transactions. 1 Introduction Enterprise JavaBeans (EJB) is an emerging standard platform for distributed component-based applications written in Java. EJB provides not only a distribution mechanism for the communication between clients and co...

Cited by 4

On Performance of Enterprise JavaBeans

Radek Pospil Marek, Marek Procházka, Vladimír Mencl · 2007

Enterprise JavaBeans (EJB) is a new-sprung technology for Java-based distributed software components. During the one year of EJB existence, several implementations have been developed, mainly by the leading corporations of the software industry. The goal of the paper is to identify a set of criteria, which would help developers to evaluate specific EJB implementations. These criteria especially cover a particular implementation's compliance to the EJB specification and performance of the implementation. Experience gained from a project 2 evaluating several EJB implementations is used in this paper. 1 Overview With the expansion of multitier application architectures, the enterprise software providers focus their attention on the request brokers, transaction monitors, and other middleware services that facilitate building the multitier applications. In response to this demand, Sun Microsystems introduced the Enterprise JavaBeans (EJB) standard, a component framework that provi...

Cited by 0

On Performance of Enterprise JavaBeans

Radek Pospisil, Marek Prochazka, Vladimir Mencl · 1999

Enterprise JavaBeans (EJB) is a new-sprung technology for Java-based distributed software components. During the one year of EJB existence, several implementations have been developed, mainly by the leading corporations of the software industry. The goal of the paper is to identify a set of criteria, which would help developers to evaluate specific EJB implementations. These criteria especially cover a particular implementation's compliance to the EJB specification and performance of the implementation. Experience gained from a project 2 evaluating several EJB implementations is used in this paper. 1 Overview With the expansion of multitier application architectures, the enterprise software providers focus their attention on the request brokers, transaction monitors, and other middleware services that facilitate building the multitier applications. In response to this demand, Sun Microsystems introduced the Enterprise JavaBeans (EJB) standard, a component framework that provi...

Cited by 0

Using JDO in Enterprise JavaBeans

David Ezzio · Apress eBooks · 2003

Contrary to a common misconception, JDO is not a replacement for Enterprise JavaBeans (EJBs). The EJB specification is primarily concerned with sharing access to remote objects and controlling distributed transactions, while JDO is primarily concerned with an object's relationship to persistent storage. Nevertheless, EJB containers and JDO provide overlapping services for managing objects. Both provide transactional semantics for objects, and both entity beans and persistent objects have mechanisms that tie object state to persistent storage. Although the overlap in services fosters the misconception that JDO and EJBs are in competition, in fact, JDO can be used with EJBs, and to some extent, it eases their development.KeywordsEnterprise ApplicationPersistent StoragePersistent ObjectBusiness MethodSerialize ObjectThese keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Cited by 0

Enterprise JavaBeans: Container Managed Persistence 2.0

Richard Sperko · Apress eBooks · 2003

On January 6, 1482, the people of Paris were awakened by the tumultuous clanging of all the bells in the city. Container Managed Persistence had reached maturity. Actually, the specification was finalized August 14, 2001, but who cares about dates. We finally have a specification that allows for complex automatic persistence of our entity beans. And we are about to get another revision in the EJB 2.1 specification.KeywordsApplication ServerUnit TestLocal InterfaceReference ImplementationPublic InterfaceThese keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Cited by 0

JavaBeans and Java Enterprise Server Platform

David Wadsworth · Auerbach Publications eBooks · 2001

A majority of the world’s data resides on mainframe servers. This legacy poses many challenges to the information systems (IS) community as it struggles with the demands of business units for new and innovative solutions to business problems. Organizations need to adopt a flexible, secure, and cost-effective architecture that will enable them to remain competitive and enable breakaway business strategies. Adoption of Java™ computing realizes these benefits by providing key technology enablers.

Cited by 0