In wadl2java-generated code, NullPointerException from HttpTransportPipe

Question

I wrote a WADL document and used JAXB schemagen to create an XSD for my Jersey RESTful web-service, and referenced that XSD in that WADL document.
Then, I used wadl2java to generate client-code for my service.
However, then, I had numerous jar-dependency problems while trying to run that generated code. Perhaps I got myself into some trouble by choosing the wrong jar-file in one case or another. I thought it was odd that one of the missing class-files was SOAPException. Another one is part of FastInfoSet. And one of the problems seemed to require adding a JSR-related jar provided by BEA.
I managed to find some possibly relevant source-code. However, it seems to simply indicate no need for an outputStream for a GET-request, which makes lots of sense:
From HttpClientTransport:
118:            public OutputStream getOutput() {
119:                try {
120:                    createHttpConnection();
121:                    sendCookieAsNeeded();
122:                    // for "GET" request no need to get outputStream
123:                    if (requiresOutputStream()) {At this point, I'm not able to use wadl2java, thanks to this failure to get this generated client-code running. I'd like to avoid writing custom client-code instead. I'd sooner revert to SOAP and wsdl2java.
Any help with this would be much appreciated.
Exception in thread "main" javax.xml.ws.WebServiceException: java.lang.NullPointerException
     at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:157)
     at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:74)
     at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:559)
     at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:518)
     at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:503)
     at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:400)
     at com.sun.xml.ws.client.Stub.process(Stub.java:228)
     at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:167)
     at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:193)
     at com.sun.research.ws.wadl.util.JAXBDispatcher.doGET(JAXBDispatcher.java:92)
     at com.foo.bar.restapi.client.Endpoint$Product.getAsProduct(Endpoint.java:66)
     at com.foo.bar.restapi.client.Test.main(Test.java:9)
Caused by: java.lang.NullPointerException
     at java.io.Writer.<init>(Unknown Source)
     at java.io.OutputStreamWriter.<init>(Unknown Source)
     at com.bea.xml.stream.XMLOutputFactoryBase.createXMLStreamWriter(XMLOutputFactoryBase.java:45)
     at com.sun.xml.ws.api.streaming.XMLStreamWriterFactory$Default.doCreate(XMLStreamWriterFactory.java:204)
     at com.sun.xml.ws.api.streaming.XMLStreamWriterFactory$Default.doCreate(XMLStreamWriterFactory.java:199)
     at com.sun.xml.ws.api.streaming.XMLStreamWriterFactory.create(XMLStreamWriterFactory.java:152)
     at com.sun.xml.ws.encoding.xml.XMLCodec.encode(XMLCodec.java:35)
     at com.sun.xml.ws.encoding.MimeCodec.encode(MimeCodec.java:64)
     at com.sun.xml.ws.encoding.XMLHTTPBindingCodec.encode(XMLHTTPBindingCodec.java:173)
     at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:128)
     ... 11 more

Answer 1

Thanks, that solved that problem.
Then, however, I had a couple of other problems, having to do with namespace declarations. I've apparently fixed them.
The one remaining problem is that the generated code seems to treat a certain template parameter as if it were a header-parameter. The WADL-file definitely uses style="template" for that parameter.
I temporarily manually patched the generated EndPoint class to get it working.
The effect of this problem was that the result was in the form of the HTML-message returned by Apache when a resource cannot be found. That was because that template parameter was missing and was being passed instead in a header.
Perhaps I'll investigate this further at some point. However, "time's a wastin'", and reverting to SOAP is now quite likely.
Thanks.