|
Designing and Implementing J2EE Clients
Because the user places high expectations on the client, you must choose your client strategy carefully, making sure to consider both technical forces and non-technical forces. This chapter presents guidelines for designing and implementing J2EE clients amidst these competing forces.
|
|
Local and Remote EJB Interfaces
As you may already know, the Enterprise Java Bean (EJB) 2.0 specification contains both a remote client view and a new local client view. Thus, session and entity beans can have a local home interface and a local component interface, either with or instead of a remote home interface and a remote component interface (the latter is usually called "component interface", omitting the word "remote").
|
|
J2EE Components and Services
Other articles in this series discussed various components, enterprise services, and runtime environments that constitute J2EE. Now it is time to assemble all of them in one place, and take a comprehensive look at the overall J2EE platform.
|
|
J2EE EJB Configuration and Deployment
Java 2 platform, Enterprise Edition (J2EE) enterprise applications are comprised of one or more individual J2EE modules. J2EE modules have deployment descriptors specific to the module type, and J2EE enterprise applications have their own deployment descriptor format. In this article, author Paul Perrone introduces the EJB application module deployment descriptor and covers the basics of EJB deployment descriptors, deployed archives, and deployment procedures.
|
|
Developing Entity Beans
This sample chapter will teach you some key points about working with Enterprise JavaBeans. Specifically, it will discuss developing CMP and BMP beans, and deploying and entity beans.
|
|
An Overview of EJB Technology
Get an outline of Enterprise JavaBeans technology, and learn about the interaction between the EJB, the client, and the EJB container. You will also learn the EJB objects and home objects, and why the use of these constructs simplifies the development of substantial software projects.
|
|
Enterprise JavaBeans™ in Context
What are Enterprise JavaBeans™ (EJBs) and what can they do for you? Explore why you should jump on the EJB bandwagon, the EJB philosophy, EJB roles and its corresponding products.
|
|
J2EE Session EJB Development
Session beans are EJB components designed to perform an action on an enterprise system on behalf of the client. They often serve as the entry points or "frontline" EJBs for EJB clients. EJB clients interact with session beans so that they can obtain the functional behavior and services of the enterprise system that the clients desire want to utilize. In this article, Paul Perrone describes how to create session bean component implementations that adhere to the EJB component-container model contract. This enables the components to operate inside an EJB container and offer their services to session bean clients.
|
|
J2EE Entity EJB Development
One of the more significant needs of the EJB specification is the need to connect to databases from within EJB. All J2EE-based components need to talk with a database, and J2EE provides support for this via JDBC. In this article, Paul Perrone looks at how J2EE-compliant environments provide access to the JDBC API and shows how they assist in configuring JDBC resources. Paul also describes how to create entity EJBs that use JDBC for data connectivity.
|
|
J2EE Message-Driven EJB Development
In the EJB 2.0 specification, a new type of EJB is defined that allows JMS message receivers to be implemented as EJBs. Known as a message-driven EJB, this new EJB gives developers a standard way for EJBs to asynchronously receive messages. Paul Perrone examines this type of EJB and explores its advantages in this article.
|
|
Scalable Application Access with J2EE Connectors
Until recently, there has been little in the way of standardization as it relates to application connectivity. B2B expert Andre Yee discusses how the Java 2 Enterprise Edition Connector Architecture will enable connectivity in a consistent, scalable, and secure fashion.
|
|
J2EE Naming and Directory Services
Java Naming and Directory Interface (JNDI) can be used for much more than simply finding resources stored by your J2EE server. Find out how much more in this sample chapter on JNDI in Java 2, Enterprise Edition.
|
|
J2EE EJB in Practice
How scalable is scalable, and how rapid is rapid? In this article, Paul Perrone offers advice based on his real-world experiences, covering pros, cons, pitfalls, and workarounds with J2EE technology. You'll learn here why J2EE, EJB, and Java technology is a vastly superior technology to use when building enterprise systems and applications.
|
|
What's New in EJB 2.1
The first public draft of the Enterprise JavaBeans 2.1 specification was released on June 19th, 2002. The spec is only in draft, and not final, so remember: the specification will almost certainly change! There, I said it. Maybe everything in this article will still be correct when the spec is final, or maybe some of it will be different. It's hard to tell at this point.
|
|
EJB 2.1: Web Services Part 1
The driving force behind EJB 2.1 is the need for Enterprise JavaBeans technology to support Web services -- a need that in turn is driven by Microsoft's release of its mammoth .NET platform, which is a significant threat to J2EE, and to Java technology in general.
|
|
EJB 2.1: Web Services Part 2
When I first planned this two-part installment I decided to cover JAX-RPC in the first part (and did), and SAAJ and JAXM in the second part. As it turns out, though, JAXM is not destined to become a part of J2EE and thus will not become an API that EJB developers can depend on. The JAXM message-driven bean I mentioned in previous installments seems more like a pipe dream than a reality. Indeed, JAXM itself looks like an API that was in decline before it ever got started.
|
|
EJB 2.1: The Timer Service
Business systems frequently make use of scheduling systems, which can be configured to run other programs at specified times. In many cases, scheduling systems run applications that generate reports, reformat data, or do audit work at night. In other cases, scheduling systems provide callback APIs that can alert subsystems of temporal events such as due dates, deadlines, etc.
|
|
EJB 2.1: Adds New Funtionality to EJB QL
If you read the most recent edition of my book Enterprise JavaBeans, 3rd Edition, you may remember that, at the end of the chapter on EJB QL, I grumbled about several problems with the query language. My biggest complaint was the lack of an ORDER BY clause. I also pointed out other deficiencies like the limited number of functions available.
|
|
EJB 2.1: The Enhanced Message-Driven Bean
The message-driven bean has undergone some important enhancements that make it far more useful and flexible than it was in EJB 2.0. That's saying a lot, because as an enterprise bean type the message-driven bean may be one of the most important components in the J2EE platform. Message-driven beans allow programmers to process asynchronous messages efficiently, and they act as a messaging gateway to the J2EE platform. At a time when asynchronous messaging is gaining recognition as a powerful programming paradigm, expansion of the MDB to new types of messaging systems is a blessing
|
|
Enterprise JavaBeansTM Technology Fundamentals
The Enterprise JavaBeans specification defines an architecture for a transactional, distributed object system based on components. The specification mandates a programming model; that is, conventions or protocols and a set of classes and interfaces which make up the EJB API. The EJB programming model provides bean developers and EJB server vendors with a set of contracts that defines a common platform for development. The goal of these contracts is to ensure portability across vendors while supporting a rich set of functionality.
|
|
EJB Tutorial
Enterprise beans are the J2EE components that implement Enterprise JavaBeans (EJB) technology. Enterprise beans run in the EJB container, a runtime environment within the J2EE server (see Figure 1-5). Although transparent to the application developer, the EJB container provides system-level services such as transactions to its enterprise beans. These services enable you to quickly build and deploy enterprise beans, which form the core of transactional J2EE applications.
|
|
EJB best practices: Build a better exception-handling framework
Enterprise applications are often built with little attention given to exception handling, which can result in over-reliance on low-level exceptions such as java.rmi.RemoteException and javax.naming.NamingException. In this installment of EJB Best Practices, Brett McLaughlin explains why a little attention goes a long way when it comes to exception handling, and shows you two simple techniques that will set you on the path to building more robust and useful exception handling frameworks
|
|
EJB best practices: Industrial-strength JNDI optimization
Brett McLaughlin continues his EJB best practices with an examination of JNDI lookups, which are an essential and frequent part of almost all EJB interactions. Unfortunately, JNDI operations almost always exact a performance toll. In this tip, Brett shows you how a home-interface factory can reduce the overhead of JNDI lookups in your EJB applications.
|
|
Understanding the WebLogic Workshop Architecture
I was goofing off this weekend, trying to figure out what would be the best topic to write about for this month's architecture column. And, like any good columnist, I procrastinated until Sunday night (the article was due on Monday morning).
|
|
Which Integration Approach is Best?
Recently I made a long trip to the East Coast. While there, I was able to meet with a number of developers, customers, and partners. I spoke to a variety of people and heard about a number of interesting community goings-on.
|
|
What are Enterprise JavaBeans components?: Part 1: The history and goals of EJB architecture
This report provides an overview of Enterprise JavaBeans (EJB) technology, enabling readers to gain a quick understanding of essential concepts. Part 1 looks at the history of EJB technology and some of the goals, advantages, and technologies. In the interest of brevity and clarity, this report presents selected key elements of EJB technology. Note that while EJB components rely on several underlying Java services, such as the Java Transaction Service, knowledge of these related technologies is not necessary to use EJB components and realize their benefits
|
|
What are Enterprise JavaBeans components?: Part 2: EJB programming model
Part 2 of this article explains the role of the Java interfaces and classes that are needed to create an Enterprise JavaBean component. In addition to coding the bean class itself, EJB developers must define a home interface and a remote interface for the bean. Implementation classes for these interfaces are typically generated by the container, so deploying an EJB component is a cooperative effort between the developer and the EJB container. Part 2 also differentiates the two primary types of enterprise beans, session beans and entity beans, and describes the relationship between the EJB container and the EJB server.
|
|
Part 3: Deploying and using Enterprise JavaBeans components
Part 3 of this article describes the deployment process for Enterprise JavaBeans components, which is more than installation because code generation is typically involved. Deployment also uses a special deployment descriptor file, which supports parameters that govern enterprise bean behavior, such as whether a bean requires transactions. This feature of bean deployment supports the EJB goal of declarative, as well as programmatic, specification of bean behavior. Part 3 also contrasts the two primary types of persistence, bean-managed and container-managed, and discusses the relationship of EJB components to CORBA. A simple three-tier EJB application is also presented.
|
|
Best practices in EJB exception handling
Part 3 of this article describes the deployment process for Enterprise JavaBeans components, which is more than installation because code generation is typically involved. Deployment also uses a special deployment descriptor file, which supports parameters that govern enterprise bean behavior, such as whether a bean requires transactions. This feature of bean deployment supports the EJB goal of declarative, as well as programmatic, specification of bean behavior. Part 3 also contrasts the two primary types of persistence, bean-managed and container-managed, and discusses the relationship of EJB components to CORBA. A simple three-tier EJB application is also presented.
|
|
The limits of delegation
While the business delegate pattern is a popular solution to EJB abstraction, it has some serious limitations. In this installment of EJB best practices, Brett McLaughlin outlines those limitations, and shows you how to avoid them.
|
|
EJB best practices: The dynamic delegate
While the business delegate class does bring exciting new flexibility to your enterprise Java designs, it can be tedious to code up a business delegate for every session bean in your application. In this installment of his EJB best practices series, Brett McLaughlin shows you how to create an even more generic version of the business delegate class: the dynamic delegate.
|
|
An EJB training program
Enterprise JavaBean (EJB) is a complex technology, one that requires a wide range of skills. Your staff may need significant training to gain these skills.
|
|
Rules and Patterns for Session Facades
In the past couple of years Enterprise JavaBeans™ (EJBs) have really started to make an impact in the Java™ object design space. During this time, one of the most common EJB patterns that we have seen employed is the notion of a Session Facade. This is a very powerful and simple notion, and one that has been beneficial to a large number of developers. However, I have also seen that there are a number of misconceptions about exactly what this pattern means, and a great deal of misunderstanding about how it should be applied in practice.
|
|
The Business Delegate pattern
One of the most complex issues in application planning is the necessary separation between business and implementation tiers. To accomplish this separation, Brett McLaughlin builds on the Business Interface pattern with a class to handle the abstraction of Web tier from business logic. The Business Delegate pattern can help you avoid the coupling that can make your applications hard to maintain and upgrade.
|
|
Introduction to EJB
Just as the Java platform has revolutionized the way we think about software development, Enterprise JavaBeans promises to revolutionize the way we think about developing mission-critical enterprise software. It combines server-side components with distributed object technologies such as CORBA and Java RMI to greatly simplify the task of application development. It automatically takes into account many of the requirements of business systems: security, resource pooling, persistence, concurrency, and transactional integrity.
|
|
EJB Architectural Overview
Enterprise JavaBeans is a component model for component transaction monitors, the most advanced type of business application server available today. To effectively use Enterprise JavaBeans, you need to understand the EJB architecture
|
|
A beginner's guide to Enterprise JavaBeans
The original JavaBeans specification describes the standard behavior and properties of Java components that run primarily on the client side of a client/server system. The introduction of the Enterprise JavaBeans Specification Version 1.0 changes all that. Enterprise JavaBeans is a component architecture for creating scalable, multitier, distributed applications, and it makes possible the creation of dynamically-extensible application servers.
|
|
Write a session EJB
Enterprise JavaBeans gives us the perfect excuse to revisit our Forum application. EJB's ability to handle messy infrastructure issues will help us quickly replace the current RMI backend with a session bean that provides the same functionality. Because it will use the EJB container's communications, scalability, and transactions support, the ForumSessionServerBean will be surprisingly simple to write
|
|
Brewing entity Enterprise JavaBeans
The Enterprise JavaBeans (EJB) specification provides two flavors of beans: session beans and entity beans. After Sun Microsystems's release of EJB Specification 1.1, support for entity beans became mandatory. This article will introduce component developers to entity beans and show how to channel the beans' power.
|
|
Read all about EJB 2.0
More than a new point release, the new EJB 2.0 specification embodies dramatic changes, including those found in the CMP component model and a new bean type, that enhance the flexibility and portability in your application development. Be one of the first to learn the capabilities of that new spec, released as a public draft this month
|
|
What's Wrong with the EJB 2 Specification?
The EJB 2.0 beta specification was released with great fanfare last summer during JavaOne. The EJB 2.0 specification introduced new features, including a souped-up version of entity bean CMP, message-driven beans, and additional CORBA interoperability. Application server vendors have rushed to support the EJB 2.0 specification; many of them have quickly provided message-driven bean support, but few have CMP and CORBA interoperability support so far.
|
|
Programming restrictions on EJB
Sanjay provides an overview of the programming restrictions on EJB component code that developers should adhere to and lists the features in Java that you'd be wise to avoid in order to write reliable and portable EJB 1.1 components.
|
|
EJB 2 Clustering with Application Servers
The Enterprise JavaBeans (EJB) component model is becoming the component framework of choice for enterprise development among Java developers. The EJB specification goes to great lengths to define characteristics that give containers the ability to manage transactions, persistence, environment variables, resource connections, and other infrastructure services.
|
|
Clustering Stateless Session Beans
Holy scalability, Batman! How are we going to get the BatWeb to support 100,000 concurrent Gothamites using our patented BatEJB technology? Our BatWeb is primarily built with stateless session BatEJBs on a single BatServer and now you them to work on our BatCluster? Will this work?!?"
|
|
EJB Free and Open Source Tools Summary
People often ask me "What's the best platform for J2EE development?" There's no clear answer for this question. First, the vendors each provide contradictory facts to prove that their product is the best. Second, each has its zealots who will tell you all of the good things about one server and bad things about the others. Third, there are dozens of products available out there.
|
|
OpenEJB: EJB for Tomcat
There has probably been a day in your life when you've asked yourself if your web application might use other J2EE concepts besides Java servlets. Your dilemma has most likely been "Although I could read the specifications, I don't have time to set up the containers and enhance the application."
|
|
Automating EJB Unit Testing
Enterprise Java Beans, or EJBs, cannot be tested on their own as can plain Java classes. There are additional steps to deploy them to an EJB container before they can be tested. This means that our testing process must include the additional process of deployment and re-deployment of EJBs. The deployment must be automated as well.
|
|
EJB Inheritance, Part 4
So far, we've seen how inheritance can be used when calling an EJB directly through RMI. However, SOAP (web services) and JMS also allow you to invoke objects remotely. Recognizing this, the EJB committee introduced JMS consumer beans (message-driven beans) in version 2.0 of the specification, and, in version 2.1, a generic asynchronous mechanism allowing web service invocations.
|
|
EJB Inheritance, Part 3
A session bean's life revolves around pure business logic. Implementing session bean inheritance is nowhere near as hard as it is with entity beans. Home interfaces are plain, containing no tricky business logic.
|
|
EJB Inheritance, Part 2
Implementing EJB inheritance is not straightforward. In my previous article, I described a technique to implant inheritance into entity bean objects, by emulating inheritance-like behavior in some areas. These areas are create and postCreate methods, home methods, and finder and ejbSelect methods.
|
|
EJB Inheritance, Part 1
Java is an object-oriented language, which means it follows the principles of object-oriented programming, such as encapsulation, inheritance, and polymorphism. (Inheritance and polymorphism pretty much go together, so they are often simply referred to as inheritance, which is what I will do in these articles.) These are great principles and can be used to represent relationships between objects in very powerful ways.
|
|
What's New in EJB 2.1?
Only a few J2EE application servers are following the EJB 2.0 specification, and already the EJB 2.1 draft specification is out. For you busy folks who want to know about what the future has in store for EJBs but don't have the time to read a 636-page document, here is a quick overview. Fair warning: the specification is a draft, so many parts are incomplete or will change.
|
|
Business Logic, Part 3
Continuing on with the Forethought business logic, I want to spend some time on the issue of stateful versus stateless beans. I refer to it as an issue because it almost always manages to come up when working with session beans, and can have a drastic effect on your application's performance. Specifically, stateless session beans are much more efficient than stateful session beans.
|
|
Business Logic, Part 2
Once offices are set up, the next logical step is to deal with Forethought users. Users are crucial to any application, which makes the UserManager component a critical part of the Forethought application.
|
|
Business Logic, Part 1
You have now completed the data layer of your application, and are ready to dive into the business layer. If you recall from Chapter 2, the business layer incorporates your application's business logic. Specifically, you will need to provide access to your entity beans, business calculations, and a scheduling facility.
|
|
JDO vs. Entity Beans: A Modest Proposal
When Sun introduced the EJB 1.1 spec (including Entity Beans) two years ago, it was a revolution in enterprise computing. Experience revealed, however, that it was not perfect. The remote interface is slow and it makes creation of fine-grained objects difficult, in many cases.
|
|
Using XDoclet: Developing EJBs with Just the Bean Class
Have you developed an EJB? Have you been frustrated at having to create and manipulate the XML deployment descriptors, as well as the interfaces?.
|
|
The Debate Over Java Data Objects
Java programmers like working with objects (I hope!). Applications often, if not always, need us to persist information. Most server-side developers have worked with the JDBC API, which allows us to access databases, and is mainly used to query relational databases.
|
|
The Debate Over Java Data Objects
Java programmers like working with objects (I hope!). Applications often, if not always, need us to persist information. Most server-side developers have worked with the JDBC API, which allows us to access databases, and is mainly used to query relational databases.
|
|
Unlocking the True Power of Entity EJBs
I've heard too much debate in the application developer community about how flawed the entity EJB model is, and that its performance isn't on par with a stateless session EJB (SLSB). I've sat, listened, and watched the debates.
|
|
Stateful Session EJBs: Beasts of Burden
That's right. You heard it here first. I'm calling Stateful Session EJBs (SFSBs) the J2EE beasts of burden. I don't care for them. I despise them. I really hate them.
|
|
EJB Message-Driven Beans
The first section describes the Java Message Service (JMS) and its role as a resource that is available to any enterprise bean (session, entity, or message-driven). Readers unfamiliar with JMS should read the first section before proceeding to the second section.
|
|
Learning EJB QL
The specification for Enterprise Java Beans 1.1 doesn't offer a standard way to define queries for finder methods in entity beans with container-managed persistence (CMP). So EJB container providers have defined their own query syntax for the finder methods of entity beans. For example, BEA's WebLogic Application Server v. 5.1 defines a query language called WLQL.
|
|
EJB 2 and J2EE Packaging, Part II
In my last article, I discussed the nature of EAR files, what they support, what they do not support, and how to configure dependency utility libraries using the manifest Class-Path: entry within a JAR file. This article intends to expand upon the discussion of J2EE packaging issues by focusing on the approaches that vendors can use for implementing EAR classloaders.
|
|
EJB 2 and J2EE Packaging, Part II
Have you noticed the number of different types of JAR files that you have to deal with lately in J2EE?! JAR files do not just hold EJBs anymore. Rather, JAR files are being used to store utility classes, web applications, enterprise applications, and Java Connector Architecture (JCA) resource adapters. Additionally, in some scenarios, some JAR files are composed of other JAR files.
|
|
Using Ant and WebLogic EJBs
EJBs are complex in both design and implementation. The steps required just to deploy them for the numerous application servers make matters worse. However, for developers using BEA's WebLogic family of application servers, life is made easier thanks to Ant.
|
|
Using Ant and WebLogic EJBs
EJBs are complex in both design and implementation. The steps required just to deploy them for the numerous application servers make matters worse. However, for developers using BEA's WebLogic family of application servers, life is made easier thanks to Ant.
|
|
EJB 2 Message-Driven Beans
This article discusses the new EJB 2.0 Message Driven Beans. I walk through an example of using this new bean, along with the corresponding JMS infrastructure that surrounds it.
|
|
EJB 2.0 Specification Release Review
With little fanfare, Sun released the second public final draft of the EJB 2.0 specification last week. Even though the specification is in the final stages before acceptance, this update contains extensive changes. Application server vendors and developers who have been unhappy with a proposed implementation of dependent objects have pushed for changes. Some background information on these issues can be found in my earlier articles
|
|
Sorting Out the EJB 2.0 Rumors
In my last article I wrote about some potential ambiguities that may exist with dependent objects. In this article I want to focus on some rumored solutions to the dependent objects issues.
|
|
Enterprise JavaBeansTM Components and CORBA Clients: A Developer Guide
This paper discusses how to enable a client written in any language supported by CORBA to access Enterprise JavaBeansTM components ("EJBTM components"). This paper is directed at programmers with advanced knowledge of both the JavaTM 2 Platform, Enterprise Edition ("J2EETM") and CORBA (Common Object Request Broker Architecture).
|
|
Deciding whether EJB is appropriate
A recent Gartner Group report cited companies overspent $1 billion on EJB last year, when they could have just gotten by with Servlets/JSPs. This motivates our next discussion: once you've decided whether server-side Java is the way to go, you then need to make the all-important decision: are you actually going to use EJB on this project? Or is EJB overkill?
|
|
Enterprise JavaBeans:
Answers to every developer's top questions
The Enterprise JavaBean (EJB) specification provides a framework for creating reusable business logic components without regard to system infrastructure or location. This paper examines why EJBs are necessary and describes how to use them when developing enterprise applications.
|
|
Clustering EJBs in WebLogic 6.0
In order to survive and gain competitive advantage in today’s eBusiness economy, application server vendors must differentiate their product offerings. Two significant differentiators that vendors are currently focusing on are “performance” and “clustering.”
|
|
The Art of EJB Deployment
In order to survive and gain competitive advantage in today’s eBusiness economy, application server vendors must differentiate their product offerings. Two significant differentiators that vendors are currently focusing on are “performance” and “clustering.”
|
|
Reusable Components: Decades of Misconceptions, Guidelines for Success
Since well before the "structured revolution" of the mid-1970s, we've known that a library of reusable components is the single largest contributor not only to programming productivity but also to the quality of the resulting application software. Nevertheless, only a minority of organizations have managed to exploit heavy reuse.
|
|
A beginner's guide to Enterprise JavaBeans
Enterprise JavaBeans is a component architecture for creating scalable, multitier, distributed applications, and it makes possible the creation of dynamically-extensible application servers.
|
|
What are Enterprise JavaBeans components?
Part 1: The history and goals of EJB architecture
This report provides an overview of Enterprise JavaBeans (EJB) technology, enabling readers to gain a quick understanding of essential concepts. Part 1 looks at the history of EJB technology and some of the goals, advantages, and technologies. In the interest of brevity and clarity, this report presents selected key elements of EJB technology.
|
|
What are Enterprise JavaBeans components?
Part 2: EJB programming model
Part 2 of this article explains the role of the Java interfaces and classes that are needed to create an Enterprise JavaBean component. In addition to coding the bean class itself, EJB developers must define a home interface and a remote interface for the bean.
|
|
What are Enterprise JavaBeans components?
Part 3: Deploying and using Enterprise JavaBeans components
Part 3 of this article describes the deployment process for Enterprise JavaBeans components, which is more than installation because code generation is typically involved.
|
|
Enterprise JavaBeans Gopalan Suresh Raj
Enterprise JavaBeans is a specification for creating server-side scalable, transactional, multi-user secure enterprise-level applications. It provides a consistent component architecture framework for creating distributed n-tier middleware.
|
|
Enterprise JavaBeans - Part 1 : Backgrounder The Relevant Technologies
Writing distributed enterprise applications has always been a significant challenge, but this once Herculean task has been somewhat ameliorated with the advancement of component-based programming in general.
|
|
Enterprise JavaBeans - Part 2 : The EJB Model
The EJB server provides an organized framework or execution environment in which EJB containers can run. It makes available system services for multiprocessing, load balancing, and device access for EJB containers.
|
|
Enterprise JavaBeans - Part 3: EJB Components
Have you noticed the number of different types of JAR files that you have to deal with lately in J2EE?! JAR files do not just hold EJBs anymore. Rather, JAR files are being used to store utility classes, web applications, enterprise applications, and Java Connector Architecture (JCA) resource adapters. Additionally, in some scenarios, some JAR files are composed of other JAR files.
|
|
Enterprise JavaBeans - Part 4: Developing an N-tier EJB Application
How can you provide an EJB-based business solution by integrating session and entity beans? Assume you are a consulting firm that was just asked to develop an online store for a fictitious bookstore chain called Horses and Stable, Inc.
|
|
Enterprise JavaBeans - Part 5: Developing Entity Beans
To develop the virtual Horses and Stable online bookstore example, the entity beans must be developed first. We develop an inventory entity bean to use later to build the shopping cart.
|
|
Enterprise JavaBeans - Part 6: Developing Session Beans
The session bean we are about to develop acts as a client to a couple of entity beans and manages the workflow between these entities. Session beans can be also be used to create new entity instances and their data in the database. Our shopping cart session bean implemented in the following has methods to help the user to shop for various items.
|
|
Enterprise JavaBeans - Part 7 : The EJB Servlet Session Bean Client
The EJB Servlet client talks to the Cart session EJB and enables clients to buy books and music albums on the Web. The servlet instantiates a Cart session bean in its init() method and communicates with the bean via the doGet() and doPost() methods.
|
|
Enterprise JavaBeans - Part 8 : Modeling Using Session and Entity Beans
Use entity beans for a persistent object model (to act as a JDBC wrapper, for instance) giving the rest of your application an object-oriented interface to your data model. Session beans are for application logic.
|
|
Writing Enterprise Applications
with JavaTM 2 Platform, Enterprise Edition
This tutorial introduces you to the APIs, tools, and services provided in the JavaTM 2 Enterprise Edition (J2EETM) Reference Implementation. You can get the J2EE Reference Implementation as a free download for demonstrations, prototyping, and educational use.
|
|
Enterprise JavaBeans 101:
Server-Side Components
Together, these two solutions provide a universal integration and enabling technology for web-based applications — JavaBeans for client-side components and Enterprise JavaBeans for server-side components.
|
|
Enterprise JavaBeans 201:
The Aggregate Entity Pattern
The appropriate design of entity beans — especially when they are backed by a relational database — is the subject of ongoing debate. So how do you provide a performance-enhancing remote interface to a set of dependent, persistent objects within an EJB system?
|
|
Looking Into Enterprise JavaBeans
The introduction of the Enterprise JavaBeans (EJB) specification by Sun Microsystems and its adoption by major application server companies like Netscape promises to ease and speed the development of mission-critical applications.
|
|
The EJB specification brings a multitier model to the Java platform
EJB application servers are sophisticated pieces of software and differ significantly in the types of connectivity they support and the quality of services they offer.
|
|
In Quest of Enterprise JavaBeans
There are some things about Web technology that make immediate sense to me, and others that don't. XML, the eXtensible Markup Language, falls into the former class. When I first read about it, its purpose seemed clear and its importance obvious. I suppose this is because so much of what I do professionally involves moving data from one incompatible format to another, and I've wished many times for a simple, standard syntax for moving objects out of databases and back in again.
|
|
Enterprise JavaBeans: Coming soon to a server near you
The Java platform for the enterprise currently includes a group of eight technologies that are of key importance to developers of enterprise-class applications. Among the most eagerly awaited of these technologies is Enterprise JavaBeans (EJB).
|
|
Enterprise JavaBeans: Simplifying Enterprise Development in the Web Environment
The development of the World Wide Web has fundamentally changed the way customers access corporate data. Many industries have deployed client-server applications, but these applications have inherent limitations that have resulted in high costs of ownership. Today, the Web represents a more cost-effective and flexible application infrastructure for deploying applications.
|
|
AN OVERVIEW of JAVATM COMPONENTS FOR MIDDLE-TIER SERVERS
Everybody is on the Internet today-- customers, partners, employees-- and they all want to access your company's information systems. They have browsers using the HTTP protocol, and you have web servers, legacy applications, and databases. Until you integrate the front-end browsers with the back-end systems, you won't be able to deploy applications over the Internet. How do you make all of these pieces work together? With a middle-tier server.
|
|
Using EJB persistence with DB2 and WebSphere on Linux
This article is for developers of enterprise applications on Linux on iSeries who want to create and load EJB data using EJB persistence in DB2/400. You'll learn how to configure the WebSphere Application Server on Linux for iSeries with a JDBC provider and data source for EJB persistence in iSeries DB2/400. You'll create a JDBC provider, create a Java 2 Connector (J2C) authentication data entry, and configure a data source to access the database in iSeries DB2/400.
|
|
WebSphere components, EJB technologies, and the future of application servers
Java One was held in San Francisco in June. Of the many press announcements that were released in conjunction with the show, the one that probably attracted the most attention was an announcement by IBM that it would soon be offering WebSphere Business Components to enhance its WebSphere Application Server platform. What does this mean for the EJB technology?
|
|
IBM WebSphere Developer Technical Journal: Dynamic EJB Finders
This article describes the solution to another challenge posed by a Customer Relationship Management (CRM) application, an application that enables the business to manage contact and relationship information for customers and prospects, that is, using EJBs to enable flexible customer queries.
|