Heiko Braun <hbraun@redhat.com>
            Mar 2010
Agenda

•   What is it?
•   What can it be used for?
•   Why should I care?
•   Building blocks
•   Project status
What is it?
Workspaces and tools
•   Workspace is a collection of tools
•   Tools represent anything you like
    •   Build in GWT
•  ...
UI Framework
•   Foundation to which to deploy your tools
•   Provides loading, initialization and access to
    tools
•  ...
Development environment
•   Not just another GWT library

•   Provides complete sandbox:
    - GWT SDK installation
    - ...
What can it be used for?
Use cases
•   Building rich client applications
•   Management functionality beyond operational
    level
•   Few constrai...
i.e Drools Guvnor




> http://www.jboss.org/drools/drools-guvnor.html
                                                   9
i.e Riftsaw Console




   > http://http://www.jboss.org/riftsaw   10
Why should I care?
Considerations

•   Tool composition at various stages
    - sandbox, project, product
•   Different feature set, maturity...
Composition and
            interplay
•   i.e. Guvnor and BPM Console
    •   Distinct tools on a project level
    •   Co...
Building blocks
Workspace sandbox

•   Low barrier entry point

    •   Java knowledge, IDE, API Docs

•   Environment to build, test and ...
Sandbox example
(1) mvn archetype:generate [...]

(2) Define value for groupId: : org.picketbox.console
    Define value for...
Workspace API

•   Reduction of boilerplate
•   Use to wire tools within a workspace
•   Split between
    - user (buildin...
User API Sample




                  18
Federation of tools
•   Leverage central repository

    •   Maven in this case

•   Mix and match:

    •   Project vs. P...
Status and roadmap
Status

•   Released 1.0 in March 2010
    •   Baseline for tool development
    •   Ready to get your hands on
•   Alread...
Roadmap

•   Focus on SOA-P requirements, i.e.
    •   Guvnor/ BRMS migration
    •   Picketbox management tools
    •   A...
Q&A
Upcoming SlideShare
Loading in …5
×

Errai Workspaces

1,993 views

Published on

What is Errai Workspaces and what can it be used for?

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,993
On SlideShare
0
From Embeds
0
Number of Embeds
455
Actions
Shares
0
Downloads
21
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Errai Workspaces

  1. 1. Heiko Braun <hbraun@redhat.com> Mar 2010
  2. 2. Agenda • What is it? • What can it be used for? • Why should I care? • Building blocks • Project status
  3. 3. What is it?
  4. 4. Workspaces and tools • Workspace is a collection of tools • Tools represent anything you like • Build in GWT • Workspaces is UI framework ... • ... but also a development environment • API, Sandbox, Repository 4
  5. 5. UI Framework • Foundation to which to deploy your tools • Provides loading, initialization and access to tools • Consists of common, shared API and services • Authentication, Logging, Exception Handling, etc 5
  6. 6. Development environment • Not just another GWT library • Provides complete sandbox: - GWT SDK installation - Build environment • Ways to distribute and integrate tool implementations: - Versioning - Repository • Aims at: - Low barrier entry point - Collaboration 6
  7. 7. What can it be used for?
  8. 8. Use cases • Building rich client applications • Management functionality beyond operational level • Few constraints on tool implementation • High expectations on: - User experience - Interactivity 8
  9. 9. i.e Drools Guvnor > http://www.jboss.org/drools/drools-guvnor.html 9
  10. 10. i.e Riftsaw Console > http://http://www.jboss.org/riftsaw 10
  11. 11. Why should I care?
  12. 12. Considerations • Tool composition at various stages - sandbox, project, product • Different feature set, maturity and target audience • Tool interplay important part of the strategy 12
  13. 13. Composition and interplay • i.e. Guvnor and BPM Console • Distinct tools on a project level • Composition at product level • Or simply re-use of tools in other projects • Picketbox Identity Management tools 13
  14. 14. Building blocks
  15. 15. Workspace sandbox • Low barrier entry point • Java knowledge, IDE, API Docs • Environment to build, test and distribute your tools • Maven archetype • Auto GWT setup • Includes necessary libraries 15
  16. 16. Sandbox example (1) mvn archetype:generate [...] (2) Define value for groupId: : org.picketbox.console Define value for artifactId: : IdentityManagement Define value for version: 1.0-SNAPSHOT Define value for package: org.picketbox.console (3) cd IdentityManagement mvn gwt:run (4) Point your browser to http://localhost:xyz (5) Open IDE and start hacking 16
  17. 17. Workspace API • Reduction of boilerplate • Use to wire tools within a workspace • Split between - user (building tools) - framework (extending workspace) 17
  18. 18. User API Sample 18
  19. 19. Federation of tools • Leverage central repository • Maven in this case • Mix and match: • Project vs. Product • JBoss vs. 3rd Party • Foster re-use and extendability • Divide and conquer 19
  20. 20. Status and roadmap
  21. 21. Status • Released 1.0 in March 2010 • Baseline for tool development • Ready to get your hands on • Already used in - Riftsaw, jBPM and Drools Flow • 8 weeks release cycle > http://jboss.org/errai 21
  22. 22. Roadmap • Focus on SOA-P requirements, i.e. • Guvnor/ BRMS migration • Picketbox management tools • Apache JUUDI console 22
  23. 23. Q&A

×