Ports generated in CASA today all go into one WSDL and contain default/dummy message/interface definitions, as well as 
default binding/port information. Several of these dummy defaults are not useful in all but a hello world application.

Besides the enhancments to guide the defition of the binding/port which is already covered in issue 
http://www.netbeans.org/issues/show_bug.cgi?id=124228, there are additional issues that need to be addressed when CASA 
doesn't reference an existing service/abstract WSDL.

CASA (or the wizards plugged into it) should allow for an option to easily define the message format and interface as 
part of the guided work-flow (wizard) if no existing WSDL is being referenced. There has to be a pre-populated default 
that just allows any message format (free-form, xsd any). 

It must also be possible to control where the port definitions get put, whether into their own WSDL (which should be 
default), or into an existing WSDL.

It should never be necessary to go into the WSDL manually - and CASA should guide the user to input values rather than 
having to figure out where to navigate to.