You didn't quite mention what type of web service it was. I'd go with Ulf's suggestion on using your own dev server and configuring SSL on it. Or you could use on of several public APIs which have a getVersion() call which do not need any authentication.
If you intend to develop a SSL-secured Web Service of your own, that's trivial. Just ensure that your WEB-INF/web.xml includes transport rules that mandate that the web services URLs are to be secured.
If you are working on a SLL-enabled web service client app, it's not that hard to create a minimal web service with secured transport (as described above). Something like a "hello, world!" service just to test the encryption. Unless you are using low-level Java networking classes, however, TLS/SSL, like cookies, will be automatically negotiated and handled by the java library.
One of the advantages of a simple "Hello, World!" service is that you can confirm that SSL is working by doing an HTTP GET request to it in a stock web browser and looking at the security indicators on the response.
Bjoke: A "Bully Joke". A Statement or action made with malicious intent - unless challenged. At which point it magically transforms into "I was just funnin'" or "What's the matter, can't take a joke?"