cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <>
Subject Re: Aegis schema validation design challenge
Date Tue, 02 Jun 2009 16:41:48 GMT
On Mon June 1 2009 9:44:25 pm Benson Margulies wrote:
> The way Tatu has woodstox validation set up, it would be desirable to
> activate it just before reading the first part-element. The code I've
> got so far wants to see the part, and thus get dispatched into the
> data binding, and then turn on validation. By which time, it's (for
> now) too late.
> It occurs to me that perhaps there's enough information to do this the
> other way. An endpoint can only have one data binding going, I think,
> so some sort of interceptor magic could call the DB and allow it to
> set validation on the stream before reading the part elements?

Yea.   That makes complete sense.   An interceptor that runs after the reading 
of the soap:body element that would set this up would definitely be the 
preferred route for doc/lit endpoints.   For RPC/Lit, I think the current 
setup is correct (as you don't validate the element name, just the type), but 
those are rare (and don't work with JAXB validation either).

In the AegisDataBinding init method, you should be able to add an interceptor 
to the Service object.   I believe that would work.

Daniel Kulp

View raw message