Example "Mashup" of wso2registry and another website?
I am interested in creating a site that includes capabilities of wso2registry but is not "exclusively" a wso2registry site.
Are there any examples or documentation for weaving together elements from wso2registry with elements from other sources? Ideally, wso2registry elements would be "components" within the larger site's content and logic.
Bookmark/Search this post with:
- Login or register to post comments
- Printer friendly version
- 327 reads
Using WSO2 Registry in other applications
WSO2 Registry can be used as a library inside other applicatios. So those applications will get all the capabilities of WSO2 Registry and they can build thier logic on top of WSO2 Registry components.
The application/site that uses the WSO2 Registry should include wso2registry jar file in its class path. Then it can access the Registry functionalities via the Registry API. Guide for using the Registry API is given in http://wso2.org/project/registry/1.1/docs/userguide.html under the "Embedding the WSO2 Registry" section. This method is applicable only for Java based applications/sites.
If you are planning to build an application/site in some other language (PHP, .NET, etc.) that needs WSO2 Registry capabilities, the APP based remote interface of the WSO2 Registry is the ideal option. You can deploy the registry in a server and then your application can access it using the APP based protocol documented in http://wso2.org/wiki/display/registry/Registry+Protocol. We have already developed client libraries for this interface in some languages. And we are planning develop client libraries for all widely used languages. But till those become available, it is possible to let your applications directly interact with the APP based protocol to get the capabilities of the WSO2 Registry.