![]() | ||
![]() Library Categories
Popular Content
| i
Change resource locationsHi, When we import wsdl's and schemas into the registry they are all stored under /governance/wsdls or /governance/schemas as their main "container" which is OK by me, but what I'd like to change is the "class" like structure that created under these container based on the wsdl or schema namespace. Is there any way to influence this decomposition behavior? I know I can first store my schemas in a bottom up version and than add the wsdls and change/add dependencies and association by hand, but I like the automatic way starting with the service and than just referencing the wsdl. Also, would it be possible to show a two column view of the dependency/association tree with the name of the artifact in the first and the path in the second. Thanks, Danny
|
![]() Tag Cloud
Lib Cont Right
|
Re: Change resource locations
Hi Danny,
You can take hold of the way in which the WSDLs and Schemas are stored by modifying the WSDLMediaTypeHandler which is found in the org.wso2.carbon.registry.extensions bundle. Also, FYI, we are in the process of improving our Governance API, where we would be looking into some of these usability concerns.
Another way to overcome this is to create a symbolic link to the /governance/wsdls/http/nsp/rdc/nl/RDC portion. So, that you can easily navigate to that location.
Also, your suggestion regarding the dependency viewer seems useful as well.
Thanks,
Senaka.