Hi,

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.
For instance all our schemas and wsdls have their namespaces started with http://nsp.rdc.nl/RDC. This gets broken down into http/nsp/rdc/nl/RDC when storing items into the registry. This makes the registry paths unnecessarily long which makes it a) unhandy to access resources directly and b) renders the dependency/association viewer unusable. Whenever looking at the tree, I'm missing the most essential part of the path, namely the resource itself.

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