my wsdl doesn;t have message

[David Spades]

<?xml version="1.0" encoding="UTF-8"?>
<definitions targetNamespace="http://impl.service.training.com/"
	name="EmployeeService">
	<import namespace="http://service.training.com/" location="http://localhost:7777/employee?wsdl=1" />
	<binding name="EmployeeServiceImplPortBinding" type="ns1:EmployeeService">
		<soap:binding transport="http://schemas.xmlsoap.org/soap/http"
			style="rpc" />
		<operation name="getEmployee">
			<soap:operation soapAction="" />
			<input>
				<soap:body use="literal" namespace="http://service.training.com/" />
			</input>
			<output>
				<soap:body use="literal" namespace="http://service.training.com/" />
			</output>
		</operation>
	</binding>
	<service name="EmployeeService">
		<port name="EmployeeServiceImplPort" binding="tns:EmployeeServiceImplPortBinding">
			<soap:address location="http://localhost:7777/employee" />
		</port>
	</service>
</definitions>

and this is my web service:

@WebService(endpointInterface = "com.training.service.EmployeeService", serviceName = "EmployeeService")
public class EmployeeServiceImpl implements EmployeeService {

	@WebResult(name = "employee")
	public Employee getEmployee(@WebParam(name = "employee_code") int code) {
		
		Employee employee = new Employee(code, new Name("john", "baptist"));
		
		return employee;
		
	}

}

why doesn't the wsdl contain message element?
thanks

[Abhay Agarwal]

Your wsdl contains message elements.
Did you noticed that it also do not contain portType element ? But still your WSDL contains portType reference in binding element
<binding name="EmployeeServiceImplPortBinding" type="ns1:EmployeeService">

Now where all these elements ?

It is here <import namespace="http://service.training.com/" location="http://localhost:7777/employee?wsdl=1" />
Open this URL http://localhost:7777/employee?wsdl=1 in browser and you will find message and (porttype ) elements.

Now point to think about - why JAX WS has seperate Web Service details in two WSDL files ?
Reason - because you have defined your Service Endpoint Interface [SEI] class EmployeeService and Service Implementation Bean[SIB] class EmployeeServiceImpl in different packages.
Therefore JAX-WS has seperated WSDL details for EmployeeService and EmployeeServiceImpl as they now should be defined in different namespcace.

if you want message, portype and binding element all in one WSDL , then , define explicit target namespace for SEI and SIB.

Happy learning !!