Even though the output and goal of the WSDL wizard and the CASA drag&drop of ports is very close (with a few small 
differentiators) they have nothing in common today whether in work-flow or output. It also is not easy to combine the 
two to achieve a goal where a combination of both approaches is desired.

* CASA only generates a dummy WSDL that needs to be manually changed for all but the most simple projects
* WSDL wizard has a more guided view to generate the expected message structure, operation, and binding details - but 
this is too much of a WSDL centric view and people are guided towards using the CASA drag & drop to create bindings

CASA has an additional requirement in that it should allow the easy creation of additional bindings/ports (either in 
an existing WSDL or by referencing one that is potentially in another project)

WSDL wizard has an additional requirement in that it can just create abstract WSDLs without binding.

Even if there remain some differences in work-flow they need to be more consistent, leverage each other and should be 
able to be combined.
* It should be possible for CASA to add additional ports into an existing WSDL (that might have been created via the 
WSDL wizard)
* CASA needs to be able to let the user either choose an existing interface/porttype (same or different project), or 
it needs to have the same capabilities as the WSDL editor to create a message definition and operation (actually there 
should also be a default porttype definition that describes a message that can have any contents via xsd any). 
* CASA needs to have the capabilities to define the binding specific details in a guided way just like the WSDL wizard 
(actually the current guidance should be enhanced for both)