Project Information
- Roadmap
- Sources
- Issue Tracking
Goals
- Deliver consistent user experience across products
- Aim for a conceptual model that represents the semantics/intentions of the domain model
- 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
- Support i18n
Design Considerations
- Core UI Abstraction: MVP
(See ManagementConsolePatterns)
- How does authentication work from the console?
(See ManagementAPISecurityDesign)
Implementation Choices
- SmartGWT (used by JON already)
- 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
- GWT Platform (MVP Abstraction)
Architectural Issues
- Embedded HTTP or Servlet Engine?
- Same Origin Policy constraint
- Deployment support for standalone & domain
- Testability: Working with GWT hosted mode
- Testability: Unit testing
Resources
- GWT Developer Guide
- Client Server Communication
- Working with JSON
- Layouts
- Widgets
- SmartGWT (Widget Library)
- MVP
- Event Handlers
- GWT and REST
- RHQ 4 GWT-UI work
- GWTP Getting Started