Tomcat problem solved

Got the problem with Tomcat solved. Files mentioned in the web.xml and servlets must match exactly.
In assignment 2 week 7 there is a slight typo in the assignment. In the file web.xml, towards the end, in the section, it should read CIS327Servlet. An alternative would be to change the servlet’s name to CIS327.

Things work ok now.

Tomcat

After loading Tomcat 4.1, it seemed to work ok. But try to do the assignment or some examples from the text, and all I could get was that everything was unavailable.
Any suggestions?

I had to download Tomcat 4.1 from the Jakarta website. If you do, download the binary file and install it. The instructions come with the download and are on the site. After I started Tomcat, I opened Internet Explorer and entered the url: http://localhost:8080.

1-28-2005

Now for the rest of the story:

3.Polymorphism: Allows programmers to write programs that process objects of classes that are part of the same class hierarchy as if they are all objects of their superclasses.

4.Encapsulation: Hide the inner workings of operations from the outside world and other objects.

5. Association: Objects being related to each other in some fashion. A relationship between classes.

6. Multiplicity: Indication of how many objects in the classes participate in the association.

7. Qualified Association: When an association has one to many multiplicity, constraints are used to reduce it to a one to one relationship, to determine which class to use.

8. Reflexive Association: A class has an association with itself.

9. Inheritance and generalization: Creating classes from existing classes.

10. Aggregations: Objects that are made up of a combination of different types of objects.

11. Composites: A strong type of aggregation, where each component in a composite can belong to just one whole object.

12. Contexts: A model of a sequence of navigational objects fro which an order is provided.

13. Interfaces and realizations: Interface is a set of operations that specifies some aspect of an object’s behavior.

14. Use Case Diagram: A description of a system’s behavior from a user’s viewpoint.

15. Class Diagram: Shows objects that make up a class.

16: Object Diagram: Shows the objects and behaviors that make up a class.

17. State Diagrams: Shows the state of an object at any given time.

18. Sequence Diagram: Shows the time-based dynamics of interactions that occur between objects.

19: Activity Diagram: shows the activities that occur within a use case or in a sequence.

20. Collaboration Diagram: Shows how the elements of a system work together to accomplish the system’s objectives.

21. Component Diagrams: Shows different elements of a system.

22. Deployment Diagram: Shows the physical architecture of a system.

1-25-2005

Terms and definitions:

1. Absrtaction: Focusing on the objects in a class that are needed as opposed to all the objects in the class.

2. Inheritance: Where new classes of objects are derived by absorbing characteristics of existing classes.

1-20-2005

This is the first entry.

Working on getting VP and Sun One up and running.