Enterprise Computing with Java ( ) Course Syllabus

Transcription

1 Enterprise Computing with Java ( ) Course Syllabus Revision: v Built on: :26 EST Copyright 2018 jim stafford

2

3 1. Course Description Meeting Times/Location Description Student Background Student Commitment Course Text(s) Optional Text(s) Required Software References Grading Grading Policy Academic Integrity Instructor Availability Syllabus Course Projects Project 0: Sanity Check Project 1: Data Access Tier and Business Logic Project 2: N-Tier Application Project 3: Secure and Asynchronous Application General Requirements Submission Guidelines iii

4 iv

5 Chapter 1. Course Description 1.1. Meeting Times/Location Wednesdays, 4:30-7:10pm APL, K Description This comprehensive course explores a variety of modern Java frameworks and technologies that can be used for developing mission-critical complex enterprise applications. The emphasis is on use of the latest Java EE platform, its set of underlying specifications, designing and developing server-side application components. Students will learn thru having hands-on experience in building multi-tier distributed enterprise applications, comparing and using variety of Java EE design patterns, rich set of server-side components and technologies, and web-enabled by modern design practices and communication protocols. Students will learn to: Implement a data access tier to a relational database using Java Persistence API (JPA), Java Database Connectivity (JDBC) API, and variety of data modeling and access patterns. Implement synchronous and asynchronous server-side business logic using stateless and stateful session EJBs, message-driven EJBs and the EJB Timer service. Integrate server-side logic with the web-tier components using legacy server-side and more modern RESTful API approaches that include JSON and XML. Other critical Java EE infrastructure services will be discussed, including the Java Naming and Directory Interface (JNDI), the Java Message Service (JMS), the Java Transaction (JTA) API, and Java EE security. Using modern development tools, commercial persistence providers, and application servers, students will design and implement several significant programming projects using the above-mentioned technologies and deploy them to a Java EE environment that they will manage. The course is being actively updated to JavaEE 8 (JPA 2.2, EJB 3.2, JAX-RS 2.1, and JMS 2.0) but a few order APIs and legacy examples remain. The development environment used in class is based on the Wildfly application server and is JavaSE 8 and JavaEE 7-compliant with the ability to preview some JavaEE 8-specific features Student Background Prerequisite: Distributed Development on the World Wide Web or equivalent Strong Java programming skills are assumed Student Commitment Students should be prepared to spend between hours a week outside of class. Time spent can be made efficient by proactively keeping up with class topics and actively collaborating with the instructor and other students in the course. 1

6 Chapter 1. Course Description 1.5. Course Text(s) Optional Text(s) The following is a list of optional texts that are pertinent to the course material but are not necessary for you to own. The course examples, notes, and free Internet resources for this course are plentiful. "Enterprise Java Beans 3.1, 6th Edition" [ preview#preview], Andrew Lee Rubinger and Bill Burke, 2010, O'Reilly, ISBN-10: ; ISBN-13: A Servlet/JSP Text "Core Servlets and JavaServer Pages (JSP)" [ Marty Hall and Larry Brown, 2003, Prentice Hall PTR; ISBN Required Software This course will make heavy use of development tools (Git, Maven 3, JUnit, SLF/Log4j, and Eclipse), a database (H2 Database Engine), JPA persistence provider (Hibernate), and application server (JBoss/Wildfly 13). Students are required to establish a local development environment. Detailed instructions for setup are part of the first exercise (Development Environment Setup) References The core of the EJB 3.2 content is covered in the EJB text for the course (and competing texts as well as online). Associated topics (database schema, JDBC, Web Tier, JMS, and tools) are not covered in the course text, but documentation will be provided through course slides, examples, and tutorials. A list of online references can be found on this site. Each lecture will supply a list of references for that technical area Grading 100 >= A >= 90 > B >= 80 > C >= 70 > F Table 1.1. Assessment % of Semester Grade Class/Newsgroup Participation 10% Project Startup/Sanity Check 5% Project 1 30% Project 2 30% Project 3 25% Projects will be done individually and graded 100 though 0 based on posted project grading criteria. 2

7 Grading Policy Class/newsgroup participation will be based on instructor judgment whether the student has made a contribution to class to either the classroom or newsgroup on a consistent weekly basis. A newsgroup contribution may be a well-formed technical observation/lesson learned, a well formed question that leads to a well formed follow up from another student, or a well formed answer/follow-up to another student's question. Well formed submissions are those that clearly summarize the topic in the subject, and clearly describe the objective, environment, and conditions in the body. The instructor will be the judge of whether a newsgroup contribution meets the minimum requirements for the week. The intent of this requirment is to promote public collaboration between class members. There will be one required project startup/sanity check submission and will be primarily graded on a done/not-done basis. The intent of this requirement is to promote early, more-focused productivity and exchange of artifacts between the student and instructor Grading Policy Late projects will be deducted 10pts/week late, starting after the due date/time, with one exception. A student may submit a single project up to 4 days late without receiving approval and still receive complete credit. Students taking advantage of the free first pass should still submit an to the instructor and grader(s) notifying them of their intent. Projects must be submitted via to the instructor and grader(s) with source code in a zip file with a README (links to archives on cloud storage acceptable as well). All source code must be written to portably compile in the grader's environment using Maven 3. This will be clearly spelled out during the course and you will have plenty of opportinuties to test the process prior to submitting a project for grade. Class attendance is strongly recommended, but not mandatory. The student is responsible for obtaining any written or oral information covered during their absence Academic Integrity Collaboration of ideas and approaches are strongly encouraged. You may use partial solutions provided by others as a part of your project submission. However, the bulk usage of another students implementation or project will result in a 0 for the project. There is a difference between sharing ideas/code snippets and turning in someone else's work as your own. When in doubt, document your sources. Do not host your course project in a *public* Internet repository Instructor Availability I am available at least 20min before class, breaks, and most times after class for extra discussion. I provide detailed answers to project and technical questions through the course newsgroup [ groups.yahoo.com/group/ejava_class]. You can get individual, non-technical questions answered via [mailto:jim.stafford@jhu.edu]. It is very common for me to ask for a copy of your broken project so that I can provide more analysis and precise feedback. Students needing further assistance are also welcome make other arrangements during the week or schedule a web meeting using Zoom Conferencing [ 3

8 4

9 Chapter 2. Syllabus Table 2.1. Data Tier Session Date Topic Comment 1 Aug29 Course Introduction Enterprise Java (JavaEE) Introduction Sep05 Development Environment Overview Business Logic 3 Sep12 Data Access Objects (DAOs) JPA Entity Manager 9 4 Sep19 JPA Core Entity Mapping 10 Exercise: Development Environment Setup [../html/jhu784- devenv-setup.html] Exercise: First Simple Application [../html/ first-simplemoduleex.html] Exercise: Entity Manager Exercise [../ html/jpa-entitymgrex.html] Project 0 Startup/ Sanity Check due by Sun, 8am Sep21 Exercise: Entity Mapping Exercise [../html/jpa-entityex.html] Validation API 5

10 Chapter 2. Syllabus Session Date Topic Comment 5 *NO CLASS* Online Lecture Sep26 JPA Relationships 11 Exercise: Relationship Mapping Exercise [../html/jparelationex.html] JPA Inheritance 6 Oct03 JPA Query (Queries, JPAQL, & Criteria API) Exercise: JPA Query Exercise [../html/jpaqueryex.html] JPA/SQL Tuning 7 Oct10 Project 1 Topics Project 1 preview due by Sun, 8am Oct14* Project 1 officially due by Sun, 8am Oct21* * One week extension only applies if preview is turned in by due date and 1:1 session completed. Table 2.2. N-Tier Application/Enterprise JavaBeans Session Date Topic Comment 8 Oct17 Project 1 Topics EJB Introduction 5-7 Exercise: Basic EJB Development [../html/ ejb-basic-lab.html] 9 Oct24 Basic Session EJB EJB Development Scenarios Configuring EJBs using ENC and JNDI 16 Configuring EJBs using CDI 6

11 Session Date Topic Comment 10 Oct31 EJB/Server-Side JPA Topics EJB Transactions Exercise: JPA/EJB Remote Interfaces [../ html/ejb-jpa-lab.html] Nov07 Web-enabled EJBs with JAX-RS Web-UI integration Project 2 due by Sun, 8am Nov18 *** Nov09 EP Drop/Audit Deadline EP Acedemic Calendar [ ep.jhu.edu/studentservices/academicservices/academiccalendar] Table 2.3. Security and Asynchronous Applications Session Date Topic Comment 12 Nov14 JavaEE Security 15 JavaEE Interceptors Nov21 Thanksgiving Break (no class) 13 Nov28 JMS 8 & Dec05 Asynchronous Methods EJB Timers Project 3 due by Sun, 8am Dec09 7

12 8

13 Chapter 3. Course Projects 3.1. Project 0: Sanity Check Project 0 will require construction of your development tree and early implemementation of technical requirements for class projects. The intent of this short/skeletal project is to get the student to a concrete starting point for course topics, eliminate wrong assumptions, and to generate early discussions about the development and development options/trade-offs. Grading will be primarily a done/not-done grade with unsatisfactory starts given feedback and a request to re-submit. Specific Goals: Instantiate a Maven development tree for projects 1 thru 3. Setup JUnit test case(s). Develop business logic interfaces and method signatures for end-to-end scenario. Develop skeletal business objects used in the business logic interfaces. Develop an early JUnit test that demonstrates understanding of the end-to-end requirements for project Project 1: Data Access Tier and Business Logic Project 1 will require the development of the business objects, O/R mapping of the business objects to a relational database, and business logic to integrate the end-to-end application. The artifacts from project 1 will also be used as a foundation for all follow-on projects as well. There is no application server used in project 1. All code is executes within a single JVM and database. Specific Goals: Develop and test a Java application Develop and test a set of POJOs Design a relational database schema Develop and test a DAO using JPA Entities Develop and test a business logic to manipulate data using DAOs. Ingest test data into database 3.3. Project 2: N-Tier Application Project 2 deploys the business logic and data tier to the server-side to be hosted in an EJB tier; providing resource management (e.g., threads), transactions, security (added in project 3), and remote access. A minimal user interface will be supplied through the use of Servlets and JSPs integrated with the EJBs. A remote client will also be developed for the unit tests. Students familiar with other UI frameworks make use alternative techniques but no additional credit will be gained with additional UI complexity or functionality. Specific Goals: 9

14 Chapter 3. Course Projects Deploy business logic within an EJB application using Session Beans Configure applications using JNDI and CDI. Implement HTTP remote access to services using JAX-RS, JSON, and XML. Integrate application with JTA Integrate business logic with a Web tier 3.4. Project 3: Secure and Asynchronous Application Project 3 enacts security for Project 2 and adds publish/subscribe topics and timers. An application server is used to host the application logic and JMS components. A stand-alone client is also developed to interface with the application through JMS messages. Specific Goals: Protect access to applications using Java EE security Authenticate users using Java EE security means Design asynchronous interactions Design JMS messages Develop and test MDB and stand-alone JMS clients Develop and test EJB Timers 3.5. General Requirements Projects must build using Maven 3 [ Ant [ will be used late in the semester to wrap any interactive commands (e.g., launch JavaSE JMS subscriber) All projects must be portable to build and deploy within grader and intructor environments. You may submit partial projects early to get portability feedback (not early content grading feedback). Test Cases must be written using JUnit or another unit test frameworks that will run within a Maven surefire and failsafe environments. Projects must be supplied with a README that points out how project meets requirements Submission Guidelines You should test your application prior to submission by Run maven clean, zip your project from the root, and unzip in a new location. Move your localrepository (or set your settings.xml#localrepository value to a new location -- don't delete your primary localrepository) and run mvn clean install from the root of your project. This will make sure you do not have dependencies on older versions of your modules or manually installed artifacts. This will also make sure you are not depending on any old.class files. This, of course, will download all project dependencies and help verify that the project will build in other environments. This will also simulate what the grader will see when they unzip your project. Coldstart your database instance(s) and run mvn clean install from the root of your project. This will make sure you are not depending on any residue schema or data in your database. Make sure the README documents all information required to navigate your application (primarily a project 2 and 3 requirement) and point out issues that would be important for the grader/instructor to know (e.g., "the instructor said...") 10

15 Submission Guidelines You will the projects to the grader and me with the following subject line (your name) project #; revision 0; part # of # Your submission will include source zip (link to cloud storage is acceptable) and README (could be in source zip). You may also include pre-built artifacts if it does not add a huge size burden. The easiest way to do this is to zip up the project from the root after completing a build. If you need to make a correction, the correction should have the following subject. The body should describe what you wish to revise. * (your name) project #; revision N; part # of # Submission s (mail to all [mailto:jim.stafford@jhu.edu]): Jim - jim.stafford@jhu.edu 11

16 12