File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Web Services and the fly likes jax-ws complex nested type is killing me Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "jax-ws complex nested type is killing me" Watch "jax-ws complex nested type is killing me" New topic

jax-ws complex nested type is killing me

Fred Woosch

Joined: Dec 02, 2007
Posts: 10
Hy there, I am having a hard time getting my webservice working like I envisioned it. I am using the standard JDK stuff, no fancy frameworks here. I am aware that you can use JAXB to map complex types. As far as I know you can use JAXB on all kinds of java beans as long as their contained data types aren't anything complex.

My Model, just won't get fully exported to WSDL.

My data model I want to transfer is structured like this:

I am going to spare you the rest of the model classes, because they are just full of strings. My Webservice looks like this:

When I publish it via Endpoint.publish(), and try to access the WSDL, I see the first type only (TaskType) but none of all the nested types I have defined. And even TaskType only appears as a reference (and nowhere eles):

This can't be right. What am I doing wrong here? Any ideas?
Peer Reynders

Joined: Aug 19, 2005
Posts: 2933
You are supposed to see something like this:

xsd=1 is an XML Schema that contains all the necessary type definitions.
I agree. Here's the link:
subject: jax-ws complex nested type is killing me
It's not a secret anymore!