Community
Participate
Working Groups
There are two choices on this page. the first mentions a unit test registry and the second mentions a public registry. Im not sure what uddi test registry this is refering to. I understand the other choice which mentions public registries. Also it would be nice if when we launched this page from a wsdl that the wsdl actually got brought up in the uddi somehow. Im not surehow easy this to do but I would expect a minimum solution would be to put the wsdl into the favorites section.
The "unit test registry" choice refers to any plugged-in tool for configuring a local unit test registry (as distinct from selecting a known, public registry on the internet). I don't quite understand what you mean by having the WSDL "brought up in the uddi somehow". Could you clarify please? BTW, I agree this page isn't too friendly and needs some significant work. I would prefer this page to bring up a list of known UDDI registries - public, private or otherwise - by exploiting the UDDI metadata framework similarly to how the Web Services Explorer does. I would prefer to track this is an RFE, unless the presence of the "unit test registry" choice is leading the user directly to trouble. I'm changing the severity. Please change it back if there is an actual bug at play here. Thanks - CB.
I think that if there is no plugged-in tool that provides a Unit Test registry present then the option should not be there. Another problem with this page is that check boxes are used for selection. A user could select both the "unit test" and "public uddi registry" check boxes when it only really makes sense to check one or the other. I think it might be cool if these two options were integrated into one nice control like a combo box. The Unit Test option could easily "disappear" if there is no Unit Test registry available. I think what Gil means about "having the WSDL brought up in the uddi somehow" is that the URL of the WSDL being should be "remembered" somehow and filled in automatically in the publish page of the WSE. Currently users have to hit browse and find the WSDL in their workspaces once the WSE publish page is brought up. I think this page would also be more useful if it provided a way for users to publish to a private Registry that they know the publish and inquiry URLs for. Maybe text fields could be provided to allow a user to enter the URLs for a registry previously unknown by the publish page. These are just some ideas to consider for when it's time to have another look at this page.
Created attachment 49082 [details] Mock up of Ideas for how page could look This is a screen shot of a very quick SWT mock up of how the page could look. This is only a suggestion but I wanted to provide some ideas about this before I head back to school.
*** Bug 163959 has been marked as a duplicate of this bug. ***
We should investigate this for WTP 3.0.
We need to clean up the publish page in a future release of WTP. Please raise the severity of this RFE if anyone deem this to be an important RFE for an upcoming release.
The Web services publish page needs to have some redesigning done. Let's try to look at it for WTP 3.1. Please also look at the issues brought up in bug 163959.
Deferring out of WTP 3.1.
This is not in the WTP 3.2 plan.
