Goals
- Deliver consistent user experience across products
- Share authentication with other management API entry points
- Manage both domain and standalone scenarios
- Provide extension points to layered products
- Remain lightweight and minimize dependencies
Requirements
- Provide management operations for all subsystems
- Allow remote deployment
- Manage user and groups that access the management infrastructure
Requires clarification:
- How does authentication work from the console?
Design Considerations
Implementation Choices
- Mixing SmartGWT with GWT proper
Might turn out to be a caveat. Two things to consider:
a) Is SmartGWT mostly external Javascript invoked through JSNI?
In that case the compiler optimizations wont work.
b) Does SmartGWT interplay with GWT? In both directions?
All GWT 2.1 features and future improvements need to be accessible.
- AutoBean an option?
Would be nice to avoid having to work overlay types directly.
- RestGWT might be a good choice
Has a proper service abstraction, plus Json-Java serialization which might be useful
Architectural Issues
- Embedded HTTP or Servlet Engine?
- Same Origin Policy constraint
- Deployment support for standalone & domain
Resources
- GWT Developer Guide
- Client Server Communication
- Working with JSON
- Layouts
- Widgets
- SmartGWT (Widget Library)
- MVP
- Event Handlers