Hello Dims,
I dropped jalopy.jar in the classpath but still no effect. Do I need
to do anything more this? Please advice. Thanks
Ramesh
On 11/18/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
Please open a JIRA bug and upload your wsdl. If you drop jalopy jar in
your classpath, the code is a
Please open a JIRA bug and upload your wsdl. If you drop jalopy jar in
your classpath, the code is automatically beautified.
-- dims
On 11/17/06, Michael Moser <[EMAIL PROTECTED]> wrote:
And I get similar compile errors on code generated for the client:
In the generated code for class Classifi
And I get similar compile errors on code generated for the client:
In the generated code for class ClassifiedServiceStub there are multiple
locations that read:
---
...
//adding SOAP headers
_serviceClient.addHeadersToEnvelope(env); // <<< does not exist
...
Sorry - I have to take my last append back - the errors still DO exist
(and are also regenerated, if one deletes the code and regenerates
again).
I had been looking using the wrong eclipse "perspective"...
Michael
"Michael Moser" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Str
Strange - since I tried again (and to verify I tried a few more times)
the code generated is now always OK.
Beats me, what went wrong the first time...
Michael
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
When running WSDL2Java I am getting two classes on which the compiler
yells:
ClassifiedServiceMessageReceiverInOnly.java line 296
The method getNamespaceURI() is undefined for the type OMNamespace
ClassifiedServiceMessageReceiverInOut.java line 343
The method getNamespaceURI() is undefined for
