response unable to receive the parameter sent

[saipraneeth nallapareddy]

i am new to web services, i am using the AXIS2 to develop my web service.
i generated a hand made WSDL file which has a types, message port->binding->service.
the following is my WSDL file

  
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tns="http://www.trial.com" name="TrialService" targetNamespace="http://www.trial.com">
	<wsdl:types>
		<xsd:schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://www.trial.com">
			<xsd:element name="sayHello">
				<xsd:complexType>
					<xsd:sequence>
						<xsd:element minOccurs="0" nillable="true" name="try" type="xsd:string"/>
					</xsd:sequence>
				</xsd:complexType>
			</xsd:element>
			<xsd:element name="sayHelloResponse">
				<xsd:complexType>
					<xsd:sequence>
						<xsd:element name="return" nillable="true" type="xsd:string"/>
					</xsd:sequence>
				</xsd:complexType>
			</xsd:element>
		</xsd:schema>
	</wsdl:types>
	<wsdl:message name="sayHelloRequest">
		<wsdl:part name="parameters" element="tns:sayHello"/>
	</wsdl:message>
	<wsdl:message name="sayHelloResponse">
		<wsdl:part name="parameters" element="tns:sayHelloResponse"/>
	</wsdl:message>
	<wsdl:portType name="trialPort">
		<wsdl:operation name="sayHello">
			<wsdl:input message="tns:sayHelloRequest" />
			<wsdl:output message="tns:sayHelloResponse"/>
		</wsdl:operation>
	</wsdl:portType>
	<wsdl:binding name="trialBind" type="tns:trialPort">
		<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
		<wsdl:operation name="sayHello">
			<soap:operation soapAction="sayHello" style="document"/>
			<wsdl:input>
				<soap:body use="literal"/>
			</wsdl:input>
			<wsdl:output>
				<soap:body use="literal"/>
			</wsdl:output>
		</wsdl:operation>
	</wsdl:binding>
	<wsdl:service name="TrialService">
		<wsdl:port name="HelloServiceHttpSoap11Endpoint" binding="tns:trialBind">
			<soap:address location="http://localhost:8080/axis2/services/TrialService.HelloServiceHttpSoap11Endpoint"/>
		</wsdl:port>
	</wsdl:service>
</wsdl:definitions>
  

i have a class that has been specified in my services.xml, which has a method with a parameter and returns a string in concatenation with the parameter, earlier i have used the same class and same service.xml file and created a .aar file and uploaded it to server with the AXIS2 deployed and it worked fine with the server generated WSDL and when i passed the parameter it has received that.

Now the problem is with my hand made WSDL file, it is showing no errors even when i tried to generate wsdl2java.bat all the stubs are getting generated, but when on the browser with the AXIS2 list of services and try to pass the parameter it is showing the hard coded string of my class but couldn't concatenate the passed parameter

can any one help me.

[saipraneeth nallapareddy]

can any one please go through this post.

[Ulf Dittmer]

try to pass the parameter

What does that mean? How, exactly, are you invoking the service?

[saipraneeth nallapareddy]

 http://localhost:8080/axis2/services/TrialService/sayHello?try=anystring   

where
sayHello is operation name
try is the parameter
anystring is its value

if the above link is clicked in my browser with tomcat running it should return an xml with content 'Hello anystring!'
but i don't know what went wrong it is just displaying 'Hello !'
not even null in the place of the anystring as the variable that should receive is a variable of java class.

[Ulf Dittmer]

http://localhost:8080/axis2/services/TrialService/sayHello?try=anystring

if the above link is clicked in my browser with tomcat running it should return an xml with content 'Hello anystring!'

That's not how SOAP services work. You need to use the client code that wsdl2java generated for you in order to create and send a proper SOAP request.

If, on the other hand, you prefer to use an URL like that one, maybe RESTful web services are more up your alley. Check out the JAX-RS API and its Jersey reference implementation; the WebServicesFaq also has lots of useful stuff about REST.