EJB

The EJB container runs on the Java EE server and manages the execution of an application's enterprise beans.

The EJB container runs on the Java EE server and manages the execution of an application's enterprise beans.

This diagrams illustrates a number of useful aspects of the UML™ Parsing Analysis approach.

There is a lot of resuse of analysis elements now, mostly the work involves just tweaking aspects of existing elements.

It is implied that EJBs execute, which is modelled as an analysis operation, with a Dependency from the source text «wrapper» Component to the Operation, so that it can be traced.

We are told that 'enterprise beans' are 'of an application', so the Association 'provide the business logic in' is strengthened with shared aggregation of the multiple :EJB[*] Property, and a Dependency is drawn from the «wrapper» Component to its Property symbol within *Applicaton_JavaEE. The other Property end is named "'of'", to become of:*Application_JavaEE.

OK, now we have some analysis models of the Java EE containers, it's time to summarise their relationship to a Java EE server ..

The EJB container is the interface between enterprise beans, which provide the business logic in a Java EE application, and the Java EE server.

The EJB container is the interface between enterprise beans, which provide the business logic in a Java EE application, and the Java EE server.

This is the first time that any specific information about the Enterprise JavaBean (EJB) has been given in the Your First Cup: An Introduction to the Java EE Platform source text.

If you have followed this UML™ Parsing Analysis demonstration trail from the beginning you may recall that the analysis model - as driven strictly by the Your First Cup: An Introduction to the Java EE Platform source text - did not converge well around the 'business component' and 'business logic' concepts, which part of the analysis model to date is reproduced in all its glory (or should I say gory detail) below the «wrapper» Component for this source text sentence about EJBs, not only as a demonstration of the incredible power of the UML™ Parsing Analysis recipe in handling complex and/or confusing and/or contradictory documentation, but also because business logic is so very vital to this demonstration, especially as these analysis «wrapper» Components are to be bound to reverse-engineered "designed" Java EE Classes and Interfaces, as we work deeper into the First Cup demonstration.

Is the EJB the rescue ? Is it in fact simply the 'business component' that was modelled as *Component_business ?

For now it will be tentatively assumed that the EJB is indeed "substitutable" for it. However then it is no longer clear that a Java EE *Server aggregates *Component_business, as indicated by the analyst's "challenge" «wrapper» Component. To resolve this more examples of the use of EJBs are needed from the Your First Cup: An Introduction to the Java EE Platform source text.

There are cases when it is NOT a good idea to try to "divide and conquer", and this is one of them; here we need to see in one place all relevant analysis elements and relevant source text «wrapper» Components.

Please don't be intimidated by the complexity of the unconverged part outside the "focus" source text «wrapper» Component about EJBs. Just for now trust that the UML™ Parsing Analysis recipe - if followed patiently - will sort this out, and by building these analysis foundations well one can build and/or bind good designs on top of it. It is about making architectural words "run" via UML.. What is about to come is nothing short of amazing, and is well worth the effort !

The EJB Container

The EJB Container

A UML™ Parsing Analysis navigation diagram after the structure of Your First Cup: An Introduction to the Java EE Platform.

Syndicate content