Skip to main content

@XmlSeeAlso - POOR choice?

1 reply [Last post]
dovholuk
Offline
Joined: 2005-04-26
Points: 0

Hi All,

I've been trying to get JAX WS to 'work' with derived types and have had no luck. I read on a different thread (and here http://weblogs.java.net/blog/kohlert/archive/2006/10/jaxws_and_type.html)
about the proposition for @XmlSeeAlso.

I personally don't like this idea much. I think that the annotation should reflect the actual type of substition going on... meaning whether the substition was via choice, substition group, or derivation.

@XmlSeeAlso is pretty unclear as to the intention of the annotation, don't you think?

anyway, i just wanted to know what "you all" thought about maybe making the annotation more clear.

thanks

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
kohsuke
Offline
Joined: 2003-06-09
Points: 0

@XmlSeeAlso annotation is not really tied to type/element substitutions at all. It's just a mechanism to let you tell JAXBContext to pick up more classes.

Doug is explaining how it can be used to fix the type substitution problem people face in JAX-WS, but that's not the only use.