Hi Hartmut,
WSO2 Registry supports three types of URLs.
1) URLs of the form http://localhost:9762/wso2registry/atom/repository/
give an ATOM feed about the target resource. It can be used to browse
and interact with the resources using APP as described in
http://wso2.org/wiki/display/registry/Registry+Protocol. This interface
is meant to be used by client applications interacting with the registry.
2) http://localhost:9762/wso2registry/web/repository/ URL gives the web
view of the target resource. You can type that URL in a web browser and
view and edit all the authorized details of that resource.
3) http://localhost:9762/wso2registry/resources/repository/config.xml
gives the raw content of the target resource. In this example, the
content of config.xml. But folders (collections) do not contain raw
content. Therefore, this pattern of URL on a folder redirects to the web
view. But in the case of WSAS or Axis2, it appends the actual file path
to the given repository location before sending to the registry. Thus,
the final URL always directs to a file and the registry serves the raw
content of that file.
So you have to give the repository location as
http://localhost:9762/wso2registry/resources/repository/, to which WSAS
appends the actual file paths to get contents of required files.
Hope this helps.
Thanks,
Chathura
[EMAIL PROTECTED] wrote:
Hi @ all,
I'm wrestling with the integration or using of the WS02 Registry in my WSAS
Server.
Below are some screenshots of my Registry configuration.
I configure the URL in the server.xml of the WSAS
<RepositoryLocation>http://localhost:9762/wso2registry/atom/repository/</RepositoryLocation>
Nothing will be loaded!!!
Where is the problem?
Can anyone help???
Thanks in advance
Hartmut
_______________________________________________
Wsas-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev
