Wso2 Greg Architecture

Hi, Sorry for delay in replying. We thought of getting a break before starting off in 2010. As you might have already realized, WSO2 G-Reg's main functionality falls under two categories. 1.Content repository 2.Governance Framework The content repository virtually can hold any type of content. But in order to give prominent support for SOA type services, we have special cased it as follows. 1. Special UI to capture both technical & non-technical details related to Services 2. Separate upload UI's for Policy, WSDL & Schema - which are tightly related to SOA type services 3. Built-in validation for Policy, WSDL & Schema There are two ways for you to update G-Reg with Service details. 1.Start from Service UI (Metadata -> Add -> Service) 2.Start by uploading WSDL (Metadata -> Add -> WSDL) In the first approach, if you add a service bearing the name 'OrderRegistration' with namespace as 'org.acme.services', this will create a resource inside /governance/services/org/acme/services/OrderRegistration with 'application/vnd.wso2-service+xml' as the media type. Similarly, you can upload a WSDL to the system & G-Reg will automatically create a service resource for you under /governance/services collection. Additionally, if a given service has WSDLs/Schema/policies G-Reg will automatically upload those & create associations between related artifacts(resources). So by programmatically monitoring/querying the location /governance/services you can get to know of the services registered with in G-Reg. Another option is to enable notifications (email,SOAP,HTTP POST) for the this repository location. For advance users, G-Reg supports writing custom handlers for given media types.  This is the current state of support we have for registering & discovering services in G-Reg (as of v3.0.2). Alternatively, we are working on getting jUDDI integrated into G-Reg. This will provide us with uddi v3 support. We are planning to get this out with March 2010 release. /sumedha