JAAS Configuration

IBM WebSphere

http://publib.boulder.ibm.com/infocenter/wasinfo/v5r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tsec_j2clogin.html

Unit Test Tutorial & Sample

Unit Test EJB with Cactus

http://www.ibm.com/developerworks/websphere/techjournal/0206_wosnick/wosnick.html#download

OOAD Toolbox

Analysis and Design
1. Well-designed software is easy to change and extend
2. Use basic OO principles like encapsulation and inheritance to make your software more flexible
3. If a design isn't flexible, then CHANGE IT! Never settle on bad design, even if it's your bad design that has to change
4. Make sure each of your classes is cohesive: each of your classes should focus on doing ONE THING really well
5. Always strive for higher cohesion as you move through your software's design life cycle


OO Principles
1. Encapsulate what varies
2. Code to an interface rather than to an implementation
3. Each class in your application should have only one reason to change
4. Classes are about behaviour and functionality

Great Software in 3 steps

1. Make sure your software does what the customer want it to do.
2. Apply basic OO principles to add flexibility.
- refactor, look for duplicate code
3. Strive for a maintainable, reusable design.
- apply design pattern