| package | req. by app. client | reg. by applet | req. by web | req. by EJB |
| EJB 3.0 JSR 244 | Y | N | Y | Y |
| Servlet 2.5 JSR 154 | N | N | Y | N |
| JSP 2.1 JSR 245 | N | N | Y | N |
| JMS 1.1 JSR 914 | Y | N | Y | Y |
| JTA 1.1 JSR 907 | N | N | Y | Y |
| JavaMail 1.4 JSR 919 | Y | N | Y | Y |
| JAF 1.1 JSR 925 | Y | N | Y | Y |
| Connector 1.5 JSR 112 | N | N | Y | Y |
| Web Services 1.2 JSR 109 | Y | N | Y | Y |
| JAX-RPC 1.1 JSR 101? | Y | N | Y | Y |
| JAX-WS 2.0 JSR 224 | Y | N | Y | Y |
| JAXB 2.0 JSR 222 | Y | N | Y | Y |
| SAAJ 1.3 JSR 67 | Y | N | Y | Y |
| JAXR 1.0 JSR 93 | Y | N | Y | Y |
| Java EE management JSR 77 | Y | N | Y | Y |
| Java EE management JSR 88 | N | N | N | N |
| JACC 1.1 JSR 115 | N | N | Y | Y |
| JSP Debugging 1.0 JSR 45 | N | N | Y | N |
| JSTL 1.2 JSR 52 | N | N | Y | N |
| Web Services Metadata 2.0 JSR 181 | Y | N | Y | Y |
| JSF 1.2 JSR 252 | N | N | Y | N |
| Common Annotations 1.0 JSR 250 | Y | N | Y | Y |
| StAX 1.0 JSR 173 | Y | N | Y | Y |
| Java Persistence 1.0 JSR 220 | Y | N | Y | Y |
Tuesday, February 12, 2008
Optional packages
CX-310-052 Assignment Objectives
- Application Design Concepts and Principles
- Explain the main advantages of an object-oriented approach to system design including the effect of encapsulation, inheritance, and use of interfaces on architectural characteristics
- Describe how the principle of "separation of concerns" has been applied to the main system tiers of a Java Platform, Enterprise Edition application. Tiers include client (both GUI and web), web (web container), business (EJB container), integration, and resource tiers
- Describe how the principle of "separation of concerns" has been applied to the layers of a Java EE application. Layers include application, virtual platform (component APIs), application infrastructure (containers), enterprise services (operating system and virtualization), compute and storage, and the networking infrastructure layers
- Common Architectures
- Explain the advantages and disadvantages of two-tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security
- Explain the advantages and disadvantages of three-tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security
- Explain the advantages and disadvantages of multi-tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security
- Explain the benefits and drawbacks of rich clients and browser-based clients as deployed in a typical Java EE application
- Explain appropriate and inappropriate uses for web services in the Java EE platform
- Integration and Messaging
- Explain possible approaches for communicating with an external system from a Java EE technology-based system given an outline description of those systems and outline the benefits and drawbacks of each approach
- Explain typical uses of web services and XML over HTTP as mechanisms to integrate distinct software components
- Explain how JCA and JMS are used to integrate distinct software components as part of an overall Java EE application
- Business Tier Technologies
- Explain and contrast uses for entity beans, entity classes, stateful and stateless session beans, and message-driven beans, and understand the advantages and disadvantages of each type
- Explain and contrast the following persistence strategies: container-managed persistence (CMP) BMP, JDO, JPA, ORM and using DAOs (Data Access Objects) and direct JDBC technology-based persistence under the following headings: ease of development, performance, scalability, extensibility, and security
- Explain how Java EE supports the deployment of server-side components implemented as web services and the advantages and disadvantages of adopting such an approach
- Explain the benefits of the EJB 3 development model over previous EJB generations for ease of development including how the EJB container simplifies EJB development
- Web Tier Technologies
- State the benefits and drawbacks of adopting a web framework in designing a Java EE application
- Explain standard uses for JSP pages and servlets in a typical Java EE application
- Explain standard uses for JavaServer Faces components in a typical Java EE application
- Given a system requirements definition, explain and justify your rationale for choosing a web-centric or EJB-centric implementation to solve the requirements. Web-centric means that you are providing a solution that does not use EJB components. EJB-centric solution will require an application server that supports EJB components
- Applicability of Java EE Technology
- Given a specified business problem, design a modular solution that solves the problem using Java EE
- Explain how the Java EE platform enables service oriented architecture (SOA) -based applications
- Explain how you would design a Java EE application to repeatedly measure critical non-functional requirements and outline a standard process with specific strategies to refactor that application to improve on the results of the measurements
- Patterns
- From a list, select the most appropriate pattern for a given scenario. Patterns are limited to those documented in the book - Alur, Crupi and Malks (2003). Core J2EE Patterns: Best Practices and Design Strategies 2nd Edition and named using the names given in that book
- From a list, select the most appropriate pattern for a given scenario. Patterns are limited to those documented in the book - Gamma, Erich; Richard Helm, Ralph Johnson, and John Vlissides (1995). Design Patterns: Elements of Reusable Object-Oriented Software and are named using the names given in that book
- From a list, select the benefits and drawbacks of a pattern drawn from the book - Gamma, Erich; Richard Helm, Ralph Johnson, and John Vlissides (1995). Design Patterns: Elements of Reusable Object-Oriented Software
- From a list, select the benefits and drawbacks of a specified Core J2EE pattern drawn from the book – Alur, Crupi and Malks (2003). Core J2EE Patterns: Best Practices and Design Strategies 2nd Edition
- Security
- Explain the client-side security model for the Java SE environment, including the Web Start and applet deployment modes
- Given an architectural system specification, select appropriate locations for implementation of specified security features, and select suitable technologies for implementation of those features
- Identify and classify potential threats to a system and describe how a given architecture will address the threats
- Describe the commonly used declarative and programmatic methods used to secure applications built on the Java EE platform, for example use of deployment descriptors and JAAS
Friday, May 4, 2007
J2EE technologies list
JSRs
JavaEE technologies
first exam based on:
J2EE 1.2so the followings applies:
| JDBC 2.0 |
| RMI-IIOP 1.0? because it is no longer supported? |
| EJB 1.1 |
| Servlets 2.2? 2.3 |
| JSP 1.1? 1.2 |
| JMS 1.0? JMS 1.0.x and 1.1 |
| JNDI 1.2 (JNDI 1.2 has been integrated into J2SE releases since J2SE 1.3) |
| JTA 1.0 (1.0.1a or 1.0.1B?) |
| JavaMail 1.0 (1.2?) |
| JAF 1.0 |
In any case it seems that the real headache is to figure out what version has to be used.
blueprints
First exam objectives
1. Concepts
1.1 Draw UML Diagrams
1.2 Interpret UML diagrams.
1.3 State the effect of encapsulation, inheritance, and use of interfaces on architectural characteristics.
2. Common Architectures
2.1 Recognize the effect on each of the following characteristics of two tier, three tier and multi-tier architectures: scalability maintainability, reliability, availability, extensibility, performance, manageability, and security.
2.2 Recognize the effect of each of the following characteristics on J2EE technology: scalability maintainability, reliability, availability, extensibility, performance, manageability, and security.
2.3 Given an architecture described in terms of network layout, list benefits and potential weaknesses associated with it.
3. Legacy Connectivity
3.1 Distinguish appropriate from inappropriate techniques for providing access to a legacy system from Java code given an outline description of that legacy system
4. Enterprise JavaBeans Technology
4.1 List the required classes/interfaces that must be provided for an EJB technology.
4.2 Distinguish stateful and stateless Session beans.
4.3 Distinguish Session and Entity beans.
4.4 Recognize appropriate uses for Entity, Stateful Session, and Stateless Session beans.
4.5 State benefits and costs of Container Managed Persistence.
4.6 State the transactional behavior in a given scenario for an enterprise bean method with a specified transactional deployment descriptor.
4.7 Given a requirement specification detailing security and flexibility needs, identify architectures that would fulfill those requirements.
4.8 Identify costs and benefits of using an intermediate data-access object between an entity bean and the data resource.
5. Enterprise JavaBeans Container Model
5.1 State the benefits of bean pooling in an EJB container.
5.2 State the benefits of Passivation in an EJB container.
5.3 State the benefit of monitoring of resources in an EJB container.
5.4 Explain how the EJB container does lifecycle management and has the capability to increase scalability.
6. Protocols
6.1 Given a scenario description, distinguish appropriate from inappropriate protocols to implement that scenario.
6.2 Identify a protocol, given a list of some of its features, where the protocol is one of the following: HTTP, HTTPS, IIOP, JRMP.
6.2 Select from a list, common firewall features that might interfere with the normal operation of a given protocol.
7. Applicability of J2EE Technology
7.1 Select from a list those application aspects that are suited to implementation using J2EE.
7.2 Select from a list those application aspects that are suited to implementation using EJB.
7.3 Identify suitable J2EE technologies for the implementation of specified application aspects. 8. Design Patterns
8.1 From a list, select the most appropriate design pattern for a given scenario. Patterns will be limited to those documented in Gamma et al. and named using the names given in that book.
8.2 State the benefits of using design patterns.
8.3 State the name of a design pattern (for example, Gamma) given the UML diagram and/or a brief description of the pattern's functionality.
8.4 Select from a list benefits of a specified design pattern (for example, Gamma).
8.5 Identify the design pattern associated with a specified J2EE feature
9. Messaging
9.1 Identify scenarios that are appropriate to implementation using messaging, EJB, or both.
9.2 List benefits of synchronous and asynchronous messaging.
9.3 Select scenarios from a list that are appropriate to implementation using synchronous and asynchronous messaging.
10. Internationalization
10.1 State three aspects of any application that might need to be varied or customized in different deployment locales.
10.2 Match the following features of the Java 2 platform with descriptions of their functionality, purpose or typical uses: Properties, Locale, ResourceBundle, Unicode, java.text package, InputStreamReader and OutputStreamWriter.
Section 11: Security
11.1 Select from a list security restrictions that Java 2 environments normally impose on applets running in a browser.
11.2 Given an architectural system specification, identify appropriate locations for implementation of specified security features, and select suitable technologies for implementation of those features.
John Wetherbie's notes
MockTests
1.1 Draw UML Diagrams
1.2 Interpret UML diagrams.
1.3 State the effect of encapsulation, inheritance, and use of interfaces on architectural characteristics.
2. Common Architectures
2.1 Recognize the effect on each of the following characteristics of two tier, three tier and multi-tier architectures: scalability maintainability, reliability, availability, extensibility, performance, manageability, and security.
2.2 Recognize the effect of each of the following characteristics on J2EE technology: scalability maintainability, reliability, availability, extensibility, performance, manageability, and security.
2.3 Given an architecture described in terms of network layout, list benefits and potential weaknesses associated with it.
3. Legacy Connectivity
3.1 Distinguish appropriate from inappropriate techniques for providing access to a legacy system from Java code given an outline description of that legacy system
4. Enterprise JavaBeans Technology
4.1 List the required classes/interfaces that must be provided for an EJB technology.
4.2 Distinguish stateful and stateless Session beans.
4.3 Distinguish Session and Entity beans.
4.4 Recognize appropriate uses for Entity, Stateful Session, and Stateless Session beans.
4.5 State benefits and costs of Container Managed Persistence.
4.6 State the transactional behavior in a given scenario for an enterprise bean method with a specified transactional deployment descriptor.
4.7 Given a requirement specification detailing security and flexibility needs, identify architectures that would fulfill those requirements.
4.8 Identify costs and benefits of using an intermediate data-access object between an entity bean and the data resource.
5. Enterprise JavaBeans Container Model
5.1 State the benefits of bean pooling in an EJB container.
5.2 State the benefits of Passivation in an EJB container.
5.3 State the benefit of monitoring of resources in an EJB container.
5.4 Explain how the EJB container does lifecycle management and has the capability to increase scalability.
6. Protocols
6.1 Given a scenario description, distinguish appropriate from inappropriate protocols to implement that scenario.
6.2 Identify a protocol, given a list of some of its features, where the protocol is one of the following: HTTP, HTTPS, IIOP, JRMP.
6.2 Select from a list, common firewall features that might interfere with the normal operation of a given protocol.
7. Applicability of J2EE Technology
7.1 Select from a list those application aspects that are suited to implementation using J2EE.
7.2 Select from a list those application aspects that are suited to implementation using EJB.
7.3 Identify suitable J2EE technologies for the implementation of specified application aspects. 8. Design Patterns
8.1 From a list, select the most appropriate design pattern for a given scenario. Patterns will be limited to those documented in Gamma et al. and named using the names given in that book.
8.2 State the benefits of using design patterns.
8.3 State the name of a design pattern (for example, Gamma) given the UML diagram and/or a brief description of the pattern's functionality.
8.4 Select from a list benefits of a specified design pattern (for example, Gamma).
8.5 Identify the design pattern associated with a specified J2EE feature
9. Messaging
9.1 Identify scenarios that are appropriate to implementation using messaging, EJB, or both.
9.2 List benefits of synchronous and asynchronous messaging.
9.3 Select scenarios from a list that are appropriate to implementation using synchronous and asynchronous messaging.
10. Internationalization
10.1 State three aspects of any application that might need to be varied or customized in different deployment locales.
10.2 Match the following features of the Java 2 platform with descriptions of their functionality, purpose or typical uses: Properties, Locale, ResourceBundle, Unicode, java.text package, InputStreamReader and OutputStreamWriter.
Section 11: Security
11.1 Select from a list security restrictions that Java 2 environments normally impose on applets running in a browser.
11.2 Given an architectural system specification, identify appropriate locations for implementation of specified security features, and select suitable technologies for implementation of those features.
John Wetherbie's notes
MockTests
Bibliography, sources and so on
- JavaRanch Big Moose Saloon
- Sun Certified Enterprise Architect for J2EE Technology by Mark Cade and Simon Roberts
- Head First EJB Passing the Sun Certified Business Component Developer Exam By Kathy Sierra, Bert Bates
- Head First Design Patterns By Eric Freeman, Elisabeth Freeman, Kathy Sierra, Bert Bates
at least I've made a decision
Subscribe to:
Comments (Atom)