This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • February 2010 Report
Skip to end of metadata
Go to start of metadata


This report has been posted at


Stonehenge has been incubating since December 2008. Stonehenge is a set of example applications for Service Oriented Architecture that spans languages and platforms and demonstrates best practices and interoperability by using currently defined W3C OASIS standard protocols.

Since the last report in December 2009, the Stonehenge project has intensified its efforts around interop testing between the M2 implementation of the claims-based security model extension to the Stock Trader implementations. Testing between .NET, Axis2/Java and Metro/Glassfish implementations have uncovered various bugs and were subsequently corrected in the web services library and the application code. An example of which is an OpenSSO problem in the Metro/Glassfish implementation that was corrected in the original code base.


With testing winding down, the community is preparing to vote and release its M2. M2 constituted of expanding the Stocktrader application to use claims-based authentication using an active and a passive STS for each implementation. We also upgraded the usage of the WS-* specs from the submitted versions to the ratified one. Extensive documentation work was done in parallel to describe the new feature set and simplify the installation and configuration process.


The focus remains on creating "micro samples" for many common WS-* scenarios, with the goal being around creating implementations with low barriers to entry. Discussions are in progress about testing frameworks and scenarios of interest. A proposed spec should be presented soon to the community to seed the discussion around defining M3

Graduation Map

  • Grow community around new claims based stocktrader implementations just added
  • More thorough documentation that empowers developers to replicate interoperability scenarios demonstrated
  • Demonstrate full interoperability between existing components, and release
  • No labels