Details
-
Type: Task
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: Aquidneck
-
Fix Version/s: 2.0.0, Sprint 2: 06-26-2012, Aquidneck
-
Component/s: None
-
Labels:None
Description
The idea here is to take a stab at developing the reseller login functionality with the goal to establish a process for working with 3rd-party development teams in successive sprints/iterations.
Why login user story:
Small-enough to get done quickly before 3rd-parties are fully on-board.
Small-enough to serve as a reference implementation as 3rd-parties ramp-up.
Makes use and potentially serves as a reference to how the security components will work
What it could be/how it could be done:
1. Develop wireframes for login
2. Provide a jar for service stubs
3. Develop the reseller GWT war and make it build-able and deployable from git/pulse
4. Make security subsystem build-able/deployable from git/pulse as a services war
5. Develop login gwt artifacts, build into war
6. integrate and test
Devil is in the details, feel free to modify as appropriate. Subtasks can be added and assigned based on the desired approach.
Attachments
1.
|
Create AvVenta github repository | Closed | Patrick Wynne | |
2.
|
Create GWT sample application | Closed | Gavin Nicol (Inactive) | |
3.
|
Create AvVenta pulse build | Closed | Patrick Wynne | |
4.
|
API documentation build process | Closed | Gavin Nicol (Inactive) |