Bill Werth

We are using pytest at work.

We first used it to test a software developer kit we sell. We looked at both pytest and unittest. I liked how pytest got things done without extra code you had to type (or probably mostly copy and paste) that essentially did nothing but make what you wrote into a class in unittest.

Pytest is powerful and felt more like you were writing Python code and not porting C++ code over to Python.

I didn't evaluate any other unit test frameworks, although I did Google a few others, but none seemed as popular as pytest, and I wanted to be able to find plenty of examples and tutorials to make learning Python + pytest easy.

I'd be interested in comments from anyone about why they picked a different testing framework.

Lots of ways this can fail. One I've seen is that you don't use exactly the same name for the server in the client as is defined in the certificate. Even though you may be able to access the server several ways (ip address, etc.), only the same exact name as in the certificate will work.

Thanks for the article link.

I don't do alot of programming in Java, but when I do it has always annoyed me that a simple feature like enums was lacking.

Nice to see it get added.

I'm a newbie with web services, so I don't know much about deployment. I have been deploying mine by putting everything in a jar file, copying it to the lib directory, and then using adminclient to deploy it.

About the only thing I see that you are doing wrong is that when you create the WSDL, use a class file instead of an interface and the parameter names will be generated correctly. That way they will end up correct in the WSDD file too. You can tell Java2WSDL the correct class file to use with the -i parameter or just change your interface into a class with empty method bodies (that is what I did).

I'm not sure that editing the WSDL to change the parameter names proves anything. It may just be proving that your deployment script isn't configured correctly.

I've edit the names and deployed the service and have kept my changes, but I don't use an ant script. That was before I found that the manual has a minor error in it. It says you can generate the WSDL using Java2WSDL from either a interface or a class, when in fact the parameter names will only be correctly generated if you provide a class compiled with debug info (-g). After this slight change in the way I create the WSDL, I no longer have to edit the parameter names.

My understanding is that the ?WSDL doesn't generate the WSDL file, it just displays one that you've previously installed with your web service.

Here is a link to a great article on how to use Axis to create your Web service: Creating Web Services with Apache Axis.

This is the article I used to write my first Web Service (and the only one so far :-) About the only thing this article is missing is how to set your classpath to compile the Web service.