Skip to main content

@SchemaValidation question

1 reply [Last post]
fnord
Offline
Joined: 2008-02-15
Points: 0

Hello,

We're experimenting with the built in schema validation and it does not seem to be working as we'd expect it to. It appears to only be validating elements/attributes and not the contents thereof.

Previously we had been doing our own validation with Xerces and the schema-full-checking feature. This did validate element content as well.

Are we doing something wrong, or does the @SchemaValidation not validate to this level? Is it possible to pass additional features to the server side validator?

Thanks!

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Jitendra Kotamraju

metro@javadesktop.org wrote:
> Hello,
>
> We're experimenting with the built in schema validation and it does not seem to be working as we'd expect it to. It appears to only be validating elements/attributes and not the contents thereof.
>
> Previously we had been doing our own validation with Xerces and the schema-full-checking feature. This did validate element content as well.
>
@SchemaValidation in JAX-WS just uses JAXP in JDK(so it should be using
xerces). Can you provide a sample example. Also try with JDK 1.6 as JAXP
impl is different.

Jitu
> Are we doing something wrong, or does the @SchemaValidation not validate to this level? Is it possible to pass additional features to the server side validator?
>
> Thanks!
> [Message sent by forum member 'fnord' (fnord)]
>
> http://forums.java.net/jive/thread.jspa?messageID=259280
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@metro.dev.java.net
> For additional commands, e-mail: users-help@metro.dev.java.net
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@metro.dev.java.net
For additional commands, e-mail: users-help@metro.dev.java.net