SortedSet - Sorted, Unique, Ascending Order
-> TreeSet - Sorted Ascending Order, fast.

Vector - grow able object, synchronized, not allow special characters and null values.

ArrayList - for Random Access, Not Synchronize, dynamically increment and decrement size.

LinkedList - provides function to Insert / deleting in middle of array, sequentially elements are linked to each other.

HashMap - Not in Order, Not Synchronized, Null value allowed, not serialized, iterator is used to traverse.

HashTable - Synchronized, Not Null Values, Serialized, Key Value Pair.

Bean Tags - cookie, define, header, include, message, page, parameter, resource, size , struts, write.

HTML Tags - base, button, cancel , checkbox, errors, file, form, frame, hidden, html, image, img, javascript, link, message, multibox, options, options Collection, password, radio, reset, rewrite, select, submit, text, textarea.

JavaScript Event Handlers - onblur, onchange, onclick, ondbclick, onfocus, onkeydown, onkeypress, onkeyup, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup.

Logic Tags - empty, equal, forward, greater Equal, greater then, iterate, less equal, match, message not present, messages present, not empty, not equal, not match, not present, present, redirect.

• Simplified version of Rational Unified Process.
• Describe simple, easy to understand approach to developing business application software using agile techniques.
• Concepts is same as RUP.
• AUP applies agile techniques including TDD, Agile modeling, agile change management and database refactoring to improve productivity.

Disciplines – Unlike RUP it has only 7 disciplines:

1. Model – understand business or organization, the problem domain address by project, and identify viable solution to address problem domain.
2. Implementation – Transform model info executable code and perform basic level testing like unit testing.
3. Test – evaluate for quality
4. Deployment – Plans for delivery of System and to execute plan to make System available for end user
5. Configuration Management – includes not only tracking artifacts version but also controlling and managing changes to them.
6. Project Management – Directs activities that takes place withing project.
7. Environment – Support the rest of effort by ensuring that proper process, guidance and tools are available for team as needed.

Internationalization (il8n): is process of designing an application so that it can be adapted to various language and regions without engineering changes.

Localization (lion): is process of adapting software for specific region or language by adding local specific components and translating text.
In Localization phase most of the portion is translation of text. Other types of data, such as sounds and images, may require localization if they are culturally sensitive. Localizers also verify that formatting of dates numbers and currencies confirms to local requirements.

Key classes for Java Internationalization

1. java.util.Local – distinguish between different localities.
2. java.util.ResourceBundle – displays appropriate message and labels for different localities using same executables and provide support for new localities without compiling new executable.
3. java.text.MessageFormat – Automatically formats elements sensitive to locality, such as dates and currencies, as appropriate to locality’s region and language.

• TDD is iterative software development process where you first write test with idea that it must fail.
• Major benefit is that code becomes thoroughly tested.

TDD base on two important principle

1. Write new business code only if automated unit test has failed
2. Eliminate duplication from code.

TDD Cycle:

1. Write some tests for specific business requirement.
2. Write some basic structure code so that test compiles but should fail.
3. Write required business code to pass test which wrote in 1
4. Finally refactor the code
5. Run tests to make sure refactored code will pass test
6. Repeat 1 to 5 for another business requirement.

TDD

• TDD eliminate duplication of code and also disciplines developer to focus on delivering what is absolutely necessary.
• TDD promotes desing to interface not implementation design Concept
• refactoring mechanism is beneficial
• Ensures that code is thoroughly tested
• Complements desing by Contract methodology and gets developer thinking in terms of pre and post condition as well as exceptions.

• Set Web Container Thread – which will be used to process incoming HTTP request.
  
• Minimum Size — Tune to Handle –> Average Load
• Maximum Size — Tune to Handle –> Peak Load
• Application Servers maintain pool of JDBC resources so that a new connection does not need to be created for each transaction.
• Tune Minimum and Maximum size of pool.
• Tune initial heap size for JVM so that garbage collector runs at a suitable interval so that it doesn’t cause unnecessary overhead. Adjust value to improve performance.
• Set session manager setting appropriately.
• Thread pool size should be set appropriately to handle average and peak load.
• If JSP and Servlet file is called frequently with identical URL then they can be dynamically cached to improve Performance.
• Turn application Server tracing off unless required for debugging.
• Some application server supports lazy loading and dirty marker strategies with EJB to improve performance

Single Sign Off – is reverse process where by a single action of signing out terminate access to multiple software systems.

Benefits of SSO:

1. Reduce amount of internet fraud by malicious employee contact.
2. Convenience of password access
3. Security on all levels of entry/exit/access to System
4. Centralized reporting for compliance adherence.

Types:
1. Host Based SSO: most commonly used.

• Host based SSO uses centralized authentication Server that all other applications and Systems utilize for authentication purpose.
  
• One of the major problem with any type of host based SSO is you create an SPF(Single Point Failure) if that authentication Server goes down, your network becomes non functional. Since no authentication takes place as all System were lost on network.

2. Script based Single Sign On:

• In this older method, you log into primary network operating System and Host stores your passwords and authentication mechanism for other Systems.
  
• When you log on the network operating System passes your authentication credentials to all other System.
• Drawback: Lack of encryption of Sensitive information, User IDS and passwords.

• Both are special kind of association.
• Aggregation is used to represent ownership or whole/part relationship and Composition is used to represent an even stronger form of ownership
• The Composite object has sole responsibility for disposition of its parts in terms of creation and destruction. i.e. Composite is responsible for memory allocations and de-allocation.
• Moreover, multiplicity on aggregation end may not exceed one i.e. it is unshared.
• An object can be part of only one composite at a time. If composite is destroyed, it must either destroy all its parts or else give responsibility for them to some other objects.

Design by Contract -

• It Specifies the obligation of a calling method and called method to each other. It should be used to build well defined interfaces.
• Strength: This technique gets programmer to think clearly about what a function does. What pre & post condition it must adhere to and also it provide documentation for caller

• Class Loaders are hierarchical in nature. Classes are introduced into JVM as they are reference by name in a class that is already running in the JVM.
• The very first class is loaded with help of static main method declared in your class.
• A class loader creates a namespace.
• All JVM includes at least one class loader that is embedded within JVM primodal/bootstrap class loader.
• Bootstarp/Primodal – Not re loadable – loads JDK internal classes java.* packages
• Extension – Not re loadable – loads jar file from JDK extension directly
• System - Not reloadable – loads classes from System classpath

1. Callback Methods:
Every EJB implements an interface (extends Enterprise Bean) which defines several method which alerts bean to various life cycle. A container is responsible for invoking these methods. These methods notify bean when to activated, to be passivated, to db, to end a transaction, to remove bean from memory etc. Entity bean has following callback methods.
public interface javax.ejb.Entitybean{
public void setEntityContext(EntityContext c);
public void unSetEntityContext();
public void ejbLoad();
public void ejbStore();
public void ejbActivate();
public void ejbPassivate();
public void ejbRemove();
}

2. EJB Context:
EJB Context provides method for interacting with container so that bean can request information about its environment like identity of caller, security, transaction status, etc.