• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Jaxws client binding / unmarshal problem

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi there,
i'm developing a java web service client.
I've got a wsdl and i know the service is perl based.

It's not my first web service client, but i'm still a newbie.

I've tested the wsdl and the service response with soapUI and other clients and it works well.

I've generated some stubs using axis2, apache cxf and jax ws ri (separately) to generate the code starting from the wsdl but no client works well.
(jdk7 x64/x86 and jdk6 x64/x86)

All the clients can connect and correctly send the request, using the debugger i can confirm that all the clients correctly recieve the response .. then all becomes black.

The response is


The axis2 client with ADB binding throws an "Unsupported type" exception on http://www.w3.org/2001/XMLSchema int

The cxf client runs without errors but the getCalcResponse object fields are NULL or 0

the jaxws ri client runs similar to the cxf


Where's the mistake ? What to analyze?

I've tried to change some annotations parameters or to force the namespace on the fields but nothing changes

PLEASE help me
 
New Guy
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
finally got it working adding the name space to the methods generated by wsimport (




and adding the XmlElement in the response bean with the same namespace


 
reply
    Bookmark Topic Watch Topic
  • New Topic