Closed GoogleCodeExporter closed 9 years ago
I follow the example and got error too
Original comment by jigsaw1...@gmail.com
on 21 Sep 2011 at 1:45
Attachments:
Try to open your wsdl file in web browser.
Looks like wsdl file for Calculator service missed. Do you have staff samples
installed?
Original comment by loentar
on 21 Sep 2011 at 12:04
I followed the installation instruction. I can run the Calculator client in the
sample. BTW, how can I generate client for axis2/java web service using staff.
The example given was a .NET web service. Thanks.
Original comment by jigsaw1...@gmail.com
on 21 Sep 2011 at 3:12
I attached two pictures about the issue. Could you please tell me how to fix
it? Thanks.
Original comment by jigsaw1...@gmail.com
on 21 Sep 2011 at 3:19
Attachments:
[deleted comment]
Please provide additional information:
- Staff version: release and platform (32/64 bit).
- Windows version: 32 or 64bit?
Original comment by loentar
on 22 Sep 2011 at 6:15
The staff version is ws-win32-vs2005-staff-2.0.0-tp6-r523.7z
I tested both on windows32(xp) and windows64(win7)
I attached my wsdl file which is generated by axis2 code generator.
Original comment by jigsaw1...@gmail.com
on 22 Sep 2011 at 1:41
Attachments:
I have generated client from wsdl you have attached without such errors. Also I
have checked generating under windows xp for Axis2/C Calculator service: no
errors while generating.
Maybe your firewall blocks network calls?
To workaround:
1. place wsdl file to the directory where your client should located
2. start codegen on it:
staff_codegen -pwsdl WeatherWS.xml -tclient_all
continue as in example.
Original comment by loentar
on 22 Sep 2011 at 7:15
Original comment by loentar
on 23 Sep 2011 at 11:18
Hi, I am having trouble generating the client code for the attached wsdl. I
used the code generator:
staff_codegen -pwsdl DataWebService.xml -tclient_all
I attched the screenshot and the xml file. Could you please test on it?
Thanks.
Original comment by jigsaw1...@gmail.com
on 24 Oct 2011 at 5:16
Seems like files can't be attached to issue's comment via email.
Please reattach it using site
http://code.google.com/p/staff/issues/detail?id=138
Original comment by loentar
on 24 Oct 2011 at 6:05
sorry for the delay. I attached the file again
Original comment by jigsaw1...@gmail.com
on 27 Oct 2011 at 3:17
Attachments:
You're forget to attach screenshot or an error description.
I assume, you're using latest binary version, that is available from download
section. This version is slightly outdated and you can get error like this:
Element ns1:showAllSchemaResponse is not found, while parsing part
I will put new (binary) version soon, where this error was fixed.
If you can't wait, you can compile staff from source code as described in
http://code.google.com/p/staff/wiki/InstallationManualWindows
Original comment by loentar
on 27 Oct 2011 at 3:38
Here is the screenshot i just took
Original comment by jigsaw1...@gmail.com
on 27 Oct 2011 at 3:51
Attachments:
Please try new version, it should work much better.
http://code.google.com/p/staff/downloads/detail?name=ws-win32-vs2005-staff-2.0.0
-tp6-r553.7z
Original comment by loentar
on 27 Oct 2011 at 6:56
ok thanks.
Original comment by jigsaw1...@gmail.com
on 27 Oct 2011 at 9:16
go through this time. Thanks.
Original comment by jigsaw1...@gmail.com
on 28 Oct 2011 at 12:02
Hi
I used the code generation tool and got serveral files. I could compile it
and ran it. But I did not get the results it should be. The return list
should not be zero size. I tested in java, and it worked fine. So I
attached the code. I am wondering if there is something missing in the new
version.
Original comment by jigsaw1...@gmail.com
on 2 Nov 2011 at 2:17
I didn't get any attachments. Please reattach using web interface.
Original comment by loentar
on 2 Nov 2011 at 5:31
Sorry, attached again.
Original comment by jigsaw1...@gmail.com
on 2 Nov 2011 at 2:27
Attachments:
Fixed in r555.
You can recompile staff from source code using InstallationManualWindows manual.
Also you can get
http://staff.googlecode.com/svn/trunk/staff/tools/codegen/template/client/Proxy.
cpp and place it into %STAFF_HOME%\bin\client\ to update only codegen's
template without recompilation (this will fix last problem).
After applying changes, you should clean your client and build it again (need
to re-generate Proxy).
Also in r555 was added chunked style response support that fixes issue figured
on top picture.
Original comment by loentar
on 2 Nov 2011 at 8:21
OK. I will try. Thanks.
Original comment by jigsaw1...@gmail.com
on 2 Nov 2011 at 8:29
I can now get the correct size of the previous operation, but now fail on
invoking another operation.
Here is what I got
ERROR ..\src\main.cpp[63]: main: CException:
Axis2/C client send receive failed. error: Error occurred in transport
Thrown from src/ServiceClient.cpp[406]: Invoke.
Expression: "pAxiomResponseNode";
I attached the src. Thanks.
Original comment by wahaha1...@gmail.com
on 3 Nov 2011 at 5:46
Attachments:
If you cannot unzip .rar, use this .zip
Original comment by jigsaw1...@gmail.com
on 3 Nov 2011 at 6:09
Attachments:
sorry for delay.
"Error occurred in transport": is an error when server cannot handle request
because some low-level error was happen (for example given operation does not
exists, invalid url was set, while sending request).
To determine why this error occurs, you should see server's logs.
Original comment by loentar
on 4 Nov 2011 at 9:27
Does this mean that staff generated codes are not general enough. Some
functions work while others depend on server side service?
As a matter of fact, I used the generated codes and some invokes work while
some don't.
Original comment by jigsaw1...@gmail.com
on 4 Nov 2011 at 9:56
As every software, that is in development, codegen may contain bugs. It happen
rarely, but if it happen codegen will produce proxy/wrapper that cannot compile
or produce invalid xml structure. In last case you can see SOAP Fault that come
from server, with error description (some xml element is not found or other
marshalling error).
But "Error occurred in transport" is a completely different type of error. It
can happen when some serious low-level error happen on server and server cannot
response with SOAP Fault and will response with HTTP Error (for example 404 -
some resource is not found, 501 internal server error, etc..). You should
examine the server's logs to find the problem.
Have you tried to call this operation using java client?
Original comment by loentar
on 5 Nov 2011 at 9:07
Yes. I tried used java before I turned to you. I used plained axis2c and it
worked too.
Original comment by jigsaw1...@gmail.com
on 5 Nov 2011 at 7:43
Error was in incorrect parsing elementFormDefault/attributeFormDefault from
wsdl definitions.
Fixed in r557.
Original comment by loentar
on 5 Nov 2011 at 9:07
OK. I will try. Thanks.
Original comment by jigsaw1...@gmail.com
on 5 Nov 2011 at 10:02
Original issue reported on code.google.com by
jigsaw1...@gmail.com
on 21 Sep 2011 at 1:22Attachments: