You can't get the WSDL via TCP. The WSDL should be available via HTTP.
If the tcp transport is correctly working, then there should be a tcp
binding in the WSDL.
The ability to get WSDL via ?wsdl is an HTTP feature.
Paul
On Feb 7, 2008 8:28 PM, h b [EMAIL PROTECTED] wrote:
Hello is it possible
Hello is it possible to generate a service stub when the service is using a
TCP transport? I don't seem to be able to do: WSDL2JAVA -uri
tcp://localhost:6060/axis2/services/myservice?wsdl.
Thanks
Thanks Paul, that's great! I checked my wsdl and it has the TCP
trasnport...thanks for the hint.
You see I'm using my service consumer is using a service stub that was
created using WSDL2Java.
Is there a way I can instruct the stub to use the TCP port to communicate
with the service? When I do
Hello, I still have the same problem but here is some more info:
I got the sample TCP Client to work...so hopefully my set up is right. And
my service is accessible from HTTP. Also when I do NETSTAT I see that
localhost:6060 is listening
Here is the exact Exception:
[INFO] Unable to parse
OK I fixed the problem:
I need to send an explicit configurationContext into the serviceStub to get
the thing working.
config = ConfigurationContextFactory.*
createConfigurationContextFromFileSystem*(*null* ,
AXIS-HOME\conf\\axis2.xml);
I'm not sure why I have to do this...can anyone explain it
If the client needs a modified axis2.xml you have to use a CCF.
Otherwise it uses a built-in version. The builtin version doesn't have
the tcp receiver enabled.
Paul
On Feb 8, 2008 2:24 AM, h b [EMAIL PROTECTED] wrote:
OK I fixed the problem:
I need to send an explicit configurationContext
