Seen on Windows XP with Hula 070403_10 and JDK 1.6.0_1.

A screenshot of the Select WSDL Port is attached.

Here's a few comments about the current implementation about the Load WSDL ports
feature:

1. It's hard to tell from the information presented what port we are talking
about. When I click Load WSDL Ports, I get a dialog that contains a few lines
like "Service=servicePort, Port=portClient", which don't give me any useful
information about the BC type, etc. At minimum, I'd like to also know the BC
type, since that's visually the most obvious trait of any WSDL port in the CASA
Design view.

Per the developers:

The basic use case is to provide a method allowing the user to load a specific
WSDL port into CASA from a service unit. The pre-condition is that the user
knows which port to load. . . . we are assuming that the user knows the content
of WSDL in SU and wants to load a specific port.

2. I'm concerned that we're expecting users to have memorized the contents of
their included SUs, which I think HIE will agree is a no-no in the usability
world, at least for those of us over a certain age. :D

3. There is no particularly good way for a user to see what WSDL ports are
defined in an SU. If I look at the correct WSDL document (the particular JBI
module contains 2 WSDL files) I can see that there is a SOAP service endpoint
defined, but it isn't easy to see the mapping between the service elements in
the WSDL document and the WSDL ports shown in the CASA Design view. (Probably a
cross-feature usability issue for making the graphical representations more
consistent.)

4. Can I choose multiple ports from the dialog? The current title implies that I
can only choose 1 at a time (Select WSDL Port), although the command is plural
(Load WSDL Ports).