Goals

Provide an implementation of WSM. It can be RI for JSR 181. My point: how about developing both RI and TCK for JSR 181 in an open manner within Beehive? It can help Beehive WSM developers to be more effectively test-driven.

Requirements

Web-services-platform-neutral design. For the purpose, Beehive WSM APIs are invented so that any web services platforms such as Axis and BEA WebLogic can make use of Beehive WSM seamlessly.

Code bases

1. JSR 181 API (mostly annotation types) from JSR-181 official site
   NB: Cliff, please check out if we can import them to Beehive SVN and update them without any (legal) conflict. If not, we can make a clean-room implementation for that.
   

• WSM for Axis from ws-axis/contrib
  

Constructs

1. JSR 181 standard annnotation types

• Beehive WSM API
• An implementation of (b) for Axis Java2WSDL tool (J2SE-targeted)
• An implementation of (b) for Axis JWS support (J2EE-Web-container-targeted)
• An implementation of (b) for Geronimo (J2EE-JSR-109-targeted)
• Test cases (including TCK)
  

Directory Structure

• wsm
  • src - root for source files
    • api - JSR 181 annotation types (as specified by JCP)
      • javax/jws
      • javax/jws/soap
    • runtime - all runtime components, platform-specific and platform-independent
      • org/apache/beehive/wsm/axis - axis-specific_implementation
      • org/apache/beehive/wsm/jsr181 - jsr 181 implementation (incl. rules enforcement, default values, etc.)
        • model - Jsr181ObjectModel
        • processor - jsr 181 processor components
          • apt - modules expecting source input files
          • reflection - modules expecting byte-code input files
        • wsdl - WSDL processing
  • drt - developer regression tests
    • tests - test cases
      • org/apache/beehive/wsm/axis
      • org/apache/beehive/wsm/jsr181
        • model
        • processor - JSR 181 processor components
          • apt
          • reflection
        • wsdl