On Thursday 09 October 2008 1:15:24 pm mateamargo wrote:
> dkulp wrote:
> > My suggestion would be to turn on schema validation on the server side.
> > It
> > should provide you with a nice error message if something isn't expected.
> >
> > That said, I think the development message is completely wrong. It's
> > using
> > id/ref things which implies soap encoding which jaxb won't handle.
>
> Why is it working if can't handle it?, I though this was something like
> SOAP version mismatching.
JAXB pretty much just ignores anything it doesn't "expect". Thus, in this
case, what you would get is a default "room" object (or whatever), but it
wouldn't have all the fields filled in as would the one the ref points to.
Turning on schema validation would definitely point some of these things out.
> Btw, how do I enable schema validation?
How are you deploying your endpoint?
If using a <jaxws:endpoint> thing, just add:
<jaxws:properties>
<entry key="schema-validation-enabled" value="true" />
</jaxws:properties>
as a child element.
--
Daniel Kulp
[EMAIL PROTECTED]
http://dankulp.com/blog
