On the S-RAMP project we have implemented about 75% of the spec and we've layered governance features on top of that. The objective is to have a functional set of features before implementing features we do not need right away. Things are working now, but may not always be 100% compliant (think about things like error handling etc).
Some major features we have working now
- Working S-RAMP repo - sitting on top of JCR (ModeShape by
default) and using RESTEasy for the S-RAMP Atom binding.
- Maven integration, so developers can release artifacts into the S-RAMP repository or they can reference artifacts in their builds as dependencies.
- S-RAMP ATOM Binding, anything that can consume a atom feed can interact with the repo.
- S-RAMP GWT based browser
- S-RAMP cmdline shell, so you interact by typing, or you can script interactions
- Governance Workflow - Integration with a BPMN2 engine (jBPM by default)
- custom REST-Based BPMN2 services to deploy artifacts from S-RAMP to runtime
- customer notification service (email + templates)
- custom S-RAMP interaction service to classify artifacts as they move through their life cycle.
- Advanced XPATH-2 query capability into the S-RAMP repository.
- Security - we need SSO across the board. We are trying to use Picketlink IDM & OAuth, sticking point is that RESTEasy 3
supports it but SOA-P 6 wants to stick with 2.3.*. Maybe we can
get Bill to back port.
- Governance console to manage workflow configuration and to embed Task Forms (right now we direct you to the jbpm-console)
- Add Documentation - We developed a kick ass process to push
Asciidoc github wiki to docbook into the regular doc stream
(https://github.com/Governance/s-ramp/wiki/GuideReadme). Now all we need is more content and demos.
- Implement all features an end2end for some interesting
Switchyard use cases.
- Add more out of the box best practices governance workflow.
- RHQ and JBossAS7 domain model deployment integrations.
- Support for SLA and policies in general.
- Auditing of what goes in and out of the repo.