Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 54059 invoked from network); 23 Mar 2006 09:17:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 23 Mar 2006 09:17:03 -0000 Received: (qmail 20943 invoked by uid 500); 23 Mar 2006 09:16:44 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 20711 invoked by uid 500); 23 Mar 2006 09:16:43 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 20700 invoked by uid 99); 23 Mar 2006 09:16:43 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Mar 2006 01:16:43 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [193.254.152.14] (HELO mail-ext.t-mobil.de) (193.254.152.14) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Mar 2006 01:16:42 -0800 Received: from mail-int.msro.detemobil.de (193.254.159.64) by mail-ext.t-mobil.de (7.2.055.1) id 42F9DCFF004E7706 for axis-user@ws.apache.org; Thu, 23 Mar 2006 10:16:19 +0100 Received: from xnx03mswb.mspr.detemobil.de (127.0.0.1) by mail-int.msro.detemobil.de (7.2.063) id 43FD75FF001C936F for axis-user@ws.apache.org; Thu, 23 Mar 2006 10:16:19 +0100 Received: by xnx03mswb.MSPR.DeTeMobil.de with Internet Mail Service (5.5.2655.55) id ; Thu, 23 Mar 2006 10:16:18 +0100 Message-ID: <8DB5BAE0F0861E43AEBFFFE7F9F544290274A7DD@cvx0dabnlw.BN.DeTeMobil.de> From: "Sensen, Andreas (external)" To: axis-user@ws.apache.org Subject: [Axis2] schema validation Date: Thu, 23 Mar 2006 10:16:14 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C64E5A.6F4B06C8" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C64E5A.6F4B06C8 Content-Type: text/plain Hi everybody, I am trying to enable schema validation for my Web service using Axis2 0.94 under linux with the included xerces 2.7.1 parser. I've a couple of questions i hope you can help me with: 1. Is it possible to enable schema validation for a particular service using the default parsing steps taken by the engine? I noticed the XmlSchema-SNAPSHOT.jar in the lib directory, but didn't find any further documentation on this topic. 2. Since i couldn't figure out an answer two question 1, i implemented a "validation module", according to the module example and user documentation, that validates incoming messages. But how can i stop message processing if validation fails? The module throws an AxisFault on invalid messages, but the messages are still relayed to the other handlers and finally the service implementation. I searched the web, documentation, mailing list archive and the API reference but couldn't find an answer. Maybe you could point me to an example or further documentation i missed. Best regards and thanks in advance, Andreas ------_=_NextPart_001_01C64E5A.6F4B06C8 Content-Type: text/html [Axis2] schema validation

Hi everybody,

I am trying to enable schema validation for my Web service using Axis2 0.94
under linux with the included xerces 2.7.1 parser. I've a couple of questions
i hope you can help me with:

1. Is it possible to enable schema validation for a particular service using the
default parsing steps taken by the engine? I noticed the XmlSchema-SNAPSHOT.jar in
the lib directory, but didn't find any further documentation on this topic.

2. Since i couldn't figure out an answer two question 1, i implemented a "validation
module", according to the module example and user documentation, that validates
incoming messages. But how can i stop message processing if validation fails? The
module throws an AxisFault on invalid messages, but the messages are still relayed to
the other handlers and finally the service implementation.

I searched the web, documentation, mailing list archive and the API reference but
couldn't find an answer. Maybe you could point me to an example or further
documentation i missed.

Best regards and thanks in advance,
Andreas

------_=_NextPart_001_01C64E5A.6F4B06C8--