Back to: Rensselaer Home Gerard's home page

Spring 2002
Course: CISH6960H35 Enterprise Java Beans

Course Syllabus Internet and Email Grading Course Policy Assignments Examples Links
Final answer key


Syllabus

Instructor Name: Gerard Weatherby Starting Date of Course:  January 10, 2002
Office Location: Engineering department, 8th floor Fax No.: 561-258-0876 
Office Hours: By appointment Email Address:  gerardw@rh.edu

Meetings:
Thursdays, 5:30-8:30 pm Room 425

Overview:
            This course will explore Enterprise Java Beans. Topics covered include entity, session, and message-driven beans, deployment descriptors and JNDI (Java Naming and Directory Interface).
Security, transactions, bean-managed and container-managed persistence, and scalability will be covered. The benefits and limitations provided by the relationship between the EJB and the container (server) are included.Students will build and deploy a sample EJB application.

Prerequisites:
            CISH-6960 Web Technologies, CSCI-4380 Database Systems, and familarity with Java. You'll need to create JSP pages and servlets, write deployment descriptors (XML documents) and Oracle DDL and DML SQL.

Objectives:

  1. Understand the relationship between EJB and the EJB container.
  2. Describe the benefits, limitations, and costs of EJBs.
  3. Explain the relationship of EJB to other portions Java 2 Enterprise Edition.
  4. List and describe the people roles of EJB.
  5. Describe the purpose of, distinctions between, and lifecycle of:
  6. Explain the purpose and format of deployment descriptors.
  7. Explain security considerations of EJBs.
Syllabus
Text:
Enterprise Java Beans, 3rd Edition, Richard Monson-Haefel, ISBN 0-596-00226-2
Errata for book
Reading assignments should be done before the listed class meeting. In general the text does not need to be brought to class.
Hardcopy notes will not be distributed. Students should download and print the notes before coming to class.
"Notes" files are better for screen display and include hypertext links. "Print" files are better for printing (2 screens per page).
Date Topic Reading Notes Print
1 1/10/02 Intro 1-5 Intro.pdf Intro2.pdf
2 1/17/02 Entity Beans 5-7,10 Entity.pdf Entity2.pdf
3 1/24/02 Session Beans 11-12 Session.pdf Session2.pdf
4 1/31/02 Message Beans 13-14 EJBMessage.pdf EJBMessage2.pdf
5 2/7/02 Final
Complete notes in single document
EJB.pdf
EJB2.pdf (2 screens per page)
Internet and e-mail
 Some information necessary to succeed in the course will only be available via the Operating System Internet web page or the list server (see below.)  The SUN accounts automatically provided to each student provide access to an e-mail account and web browser, or you may use your own. Students should:
· if not familar with the Sun operating system, attend the Sun user's workshop and/or review the network user's guide
· subscribe to the listserv
· forward their Rensselaer email address to another address, if desired. (see http://www.rh.edu/tis/internal/UserGuide/messages.html#m10)
· review the web site at the beginning of the course and when suggested by the listserv.
Enterprise Java Beans Grading


Attendance  5%
Assignments 45%
Final  50%
    The project will consist of a J2EE application. It may be hosted on a copy of Sun's J2EE reference implementation server installed at RH. If a student has access to another EJB 2.0 compliant server which can be publicly accessed via the internet that may also be used. Students are encouraged to work in groups of two.

    The final exam is closed book and notes.

    There are specific requirements for hardcopy assigments which must be followed.

    The student is responsible for ensuring the material required by the assignment is turned in.  Excuses such as 'Someone from work must have taken my printout' and 'I know I forgot the output but you can see the code is correct' will not be accepted.  There are no redos, extra credit projects, etc.

    The only deviations from this policy will be due to serious injury or illness of the student or immediate family member. Contact me as soon as practical in this event.

    Final grades will be curved using a modified Z-score. Raw scores about 90% or a z-score above 1 (i.e. your score is more than one standard deviation above class average) will be awarded an "A."  The instructor may, at his discretion, lower the minimum score for an A at the end of the semester based on inspection of the score distribution.

Enterprise Java Beans Policy

Office hours are Tuesdays and Thursdays and selected Saturdays by appointment. Since class meets one day a week, attendance is essential and will be noted. You are highly encouraged to utilize the listserv and email to contact me with questions and problems. Assignments must be handed in on time. In order to allow prompt return of assignments, they will not be accepted late. In general, makeup exams will not be given. If you anticipate being unable to attend class, please notify me before class to make arrangements for any assignments that may be due. If an emergency arises, please contact me.

It should be understood that as an adjunct lecturer, I generally have no reason to be at Rensselaer other than on class nights; you should not expect items left for me in my engineering department mailbox to be received quickly.

In order to facilitate the answering of questions, Rensselaer at Hartford has set up a listserv. This will allow you to contact each other as well as myself with questions pertaining to course content, assignments, or the use of the compiler. To subscribe, send an email to "listserv@rh.edu" and include the line "subscribe ejb" in the message body. See http://www.rh.edu/tis/listserv.html. Alternatively, you can use a the use the form found on http://www.charlesconsulting.com/scripts/listserv.pl. To unsubscribe, use the instructions you received when you subscribed or use this link. Students are responsible for information posted to the listserv.

Questions regarding assignments or general questions should sent to the listserv. This ensures all students have access to the same information. Only questions regarding a specific situation should be sent directly to me.  General questions sent directly to me may be returned unanswered with a request to repost the question to the listserv.

Academic Integrity:

Student-teacher relationships are built on trust. For example, students must trust that teachers have made appropriate decisions about the structure and content of the courses they teach, and teachers must trust that the assignments which students turn in are their own. Acts, which violate this trust, undermine the educational process.

The Rensselaer Handbookdefines various forms of Academic Dishonesty and procedures for responding to them. All forms are violations of the trust between students and teachers. Students should familiarize themselves with this portion of the Rensselaer Handbook and should note that the penalties for plagiarism and other forms of cheating can be quite harsh.

The expectation is every student will do their own work. Discussion, exchange of ideas, assistance in debugging or illustrating concepts with sample code is okay and encouraged, but the expectation is each student will submit assignments they have typed, compiled, and testing themselves. This is the default condition at Rensselaer unless otherwise specified by the instructor. Any form of collaboration on the individual portions of this course will be considered as cheating and I will take immediate action to stop such behavior. Penalties for students who violate the code of academic honesty include dismissal from Rensselaer at Hartford. (See the student catalog or review online at http://www.rh.edu/dept/pub/Catalog9899/policies.html#AD)

Hardcopy requirements

The following requirements apply to hardcopy submissions:

  • the submission must have a cover page with your name and the assignment designation on it.
  • the assignment must be printed on standard 8 ½ x 11 paper.
  •  multiple sheets must be stapled together.
  • the use of color printouts is discouraged because they are typically more expensive and donÆt help your grade at all.
  • for group projects the name of the author and anyone who modifies the code should be marked in the code as comments

  •  

     
     










    Disclaimers

    The RH J2EE server is still in the process of being installed. Modifications to this syllabus may be required in the event of technical difficulties.
    Many of the terms used here and in this course are trademarked by Sun, such as JavaTM. (Note this applies to the language only, as far as I know the island and caffeinated beverage are not covered by this trademark.)

    Snow policy

    See official Rensselaer at Hartford policy.  Bottom line: your safety is more important than getting to class. If you feel you're circumstances preclude you from getting here safetly, don't come. Email me when you can.
     

     


    Last Updated: Thursday, February 22 2007 08:45
    Rensselaer at Hartford, 275 Windsor St, Hartford, CT 06120
    For more information: 1-800-433-4723 or info@rh.edu
    Please send questions, comments or suggestions to webmaster@rh.edu