Strangely enough, it looks like the difference between the Axis2 examples
that successfully implement out-only messages and mine is that the Axis2
examples use the "generate synchronous methods only" option turned on. In
the ant wsdl2java java command line task, this is done as follows:
<java classname="org.apache.axis2.wsdl.WSDL2Java" fork="true"
failonerror="true">
...
<arg value="-s"/>
the ant wsdl2java task, this is done as follows:
<taskdef name="wsdl2java"
classname="org.apache.axis2.tool.ant.AntCodegenTask"
classpathref="axis2.classpath"/>
<wsdl2java
wsdlFilename="${basedir}/resources/META-INF/StockQuoteService.wsdl"
...
synconly="true"/>
My question now is, why must the WSDL2Java synchronous methods option be
turned on in order to successfully generate asynchronous messages?
-David
--
View this message in context:
http://www.nabble.com/Cannot-Find-Symbol-receiveResultpublishElint%28%29-tf3603009.html#a10066459
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
