I came across similar issue before and I think I used Document/Literal binding
to resolve it. You can try by using the following SOAPBinding...
@SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use=SOAPBinding.Use.LITERAL)
View the original post :
http://www.jboss.com/index.html?module=bb&op=vie
at least in my instance I get the same result as before.
btw, I'm running the version javaws that comes default with jboss 4.2.1GA. I
don't suppose this annotation change fixed your issue because you were on the
new version of jbossws?
I suppose the next step is to see if it's a parsing error
This is basically a JAXB bug
https://jaxb.dev.java.net/issues/show_bug.cgi?id=268.
The workaround you can use it to wrap your map into another class. This class
has to be annotated with @XmlAccessorType(XmlAccessType.FIELD) since the bug
prevents you from adding @XmlElement to your map field.
This absolutely works so long as it's a simple Map with simple objects(like
strings) as key/values. But this seems to break down when you've got nested
maps.
here's a "simple" map with just a string key and string value.
|
|
| 6
|
|
|
|
|
|
|
"mwkohout" wrote : This absolutely works so long as it's a simple Map with
simple objects(like strings) as key/values. But this seems to break down when
you've got nested maps.
| ...
| I'm using maps and lists to avoid making DTOs. Maybe at this point it
would just be easier to make the da
Yeah, I think you're rightthanks for your help by the way.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108988#4108988
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108988
