Putting The Framework to Work (Tasklist)

Introducing business logic
- Keeping a list
- Adding items
- Design challenge: whose list is it anyway?
A familiar refrain: MVC, separation of concerns
Sakai Enabling Technologies
- A registry for components
- A registry for tools
- Sakai sessions
- Sakai events
- Users, Sites, Courses
- Authorization
Dependency injection revisited
- Using a universal component to get the user's name
- Using tool context to show the correct list
- Registering events with Sakai
What are the benefits, by the way?
- Authentication mediated by the portal
- Access to Sakai facilities for browsing, adding, and configuring tools
- Convenience for your users
- Information about the current user through an API
- Centralized events for system reporting
The small matter of functionality
- Our servlet, dead-simple Controller
- The classes for the Model
- Putting lipstick on a pig: the View
maven cln bld dpl
svn commit -m "Having coupled our tool to Sakai, we derive a few benefits."

Here are the files we'll be writing in this iteration:

Labels