/
public SAXParseException getSaxParseException() {
return saxParseException;
}
/**
* Set saxParseException
* @param saxParseException the saxParseException to set
*/
public void setSaxParseException(SAXParseException
sa
Title: RE: Schema validation Axis 1.3
Here is the filter... The trick with this is that you have to wrap the HttpServletRequest so that you can send the request on to filters down stream once you have read the input stream. You can do this using HttpServletRequestWrapper. I will be happy
Hi John, how complex is your filter code? It would be a great entry in
the Axis wiki ;-)
Regards,
Rodrigo Ruiz
John Pfeifer wrote:
>
> Good luck with this one. I have posted several times about schema
> validation in axis2 and it looks like you have to do it yourself. I
> wrote a servlet filte
Title: RE: Schema validation Axis 1.3
Good luck with this one. I have posted several times about schema validation in axis2 and it looks like you have to do it yourself. I wrote a servlet filter that sits in front of the axis servlet and validates the request against a given xsd
Hi John,
You have mentioned you will be getting the message using
RawXMLINOutMessageReceiver and then passing that to JiBX. Do you know
that we have in-built support for JiBX.
Just get the wsdl, code generate using that giving -d jibx. Not ony you
will get the code to pass your xml to jibx, it wi
Hi John,
You may start from here[1].
Regards,
Ali Sadik Kumlali
[1] http://www.mail-archive.com/axis-user@ws.apache.org/msg11312.html
- Original Message
From: John Pfeifer <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Thursday, October 5, 2006 4:07:57 PM
Subject: Schema
We do not do schema validation in Axis2 .. So you should do it
explicitly from your service
I am not sure is there a schema validator for OMElement .. you should ask!
Thanks
Srinath
On 10/5/06, John Pfeifer <[EMAIL PROTECTED]> wrote:
I have created a test web service (see below). This ser
of how that "should be" was useful.
Doug
On 7/12/06, Derek <[EMAIL PROTECTED]> wrote:
>
>
> > -Original Message-
> > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, July 12, 2006 11:50 AM
> > To: axis-user@ws.apache.org
on of how that "should be" was useful.
Doug
On 7/12/06, Derek <[EMAIL PROTECTED]> wrote:
> -Original Message-
> From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 12, 2006 11:50 AM
> To: axis-user@ws.apache.org
> Subject: Re: Schema
:[EMAIL PROTECTED]
> Sent: Wednesday, July 12, 2006 11:50 AM
> To: axis-user@ws.apache.org
> Subject: Re: Schema Validation (WAS: [axis2] Validating
> Messages :: WSDL :: )
>
> As I said in my original response, a databinding framework
> will always perform some basic validation -
The schema describing the message structure is the published
interface. And a schema can include all kinds of validation
requirements (e.g., default values, fixed values, uniqueness,
referential integrity, etc.) Some of these requirements are extremely
expensive to validate. A databinding framewor
> -Original Message-
> From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 12, 2006 11:50 AM
> To: axis-user@ws.apache.org
> Subject: Re: Schema Validation (WAS: [axis2] Validating
> Messages :: WSDL :: )
>
> As I said in my original
Thanks, Anne.
I guess I want to draw the line at what is specifiable in the
published interface. So, yes, regular expressions, enumerations, etc.
I'd push the decision about using those back on the Schema design
phase, not on the implementation engine. I can see you don't agree
:-). Where woul
Sorry for the silence. I took a couple of days off.
True schema validation is an extremely expensive process -- especially
if you put uniqueness or referential integrity constraints into the
schema. Even checking for nulls can be expensive if it's a large
document instance. If you have control ov
Anne doesn't appear to be around right now, but I'll bug her when it
looks like she is. In the meantime, surely some of the other list
readers have some opinions on this topic?
On 7/9/06, Benjamin Fan <[EMAIL PROTECTED]> wrote:
If there is going to be a discussion then I would very much like t
If there is going to be a discussion then I would very much like to participate in it. I am in the middle of building a production system where I do in fact need to validate against the schema. In fact the WSDL (doc literal) will form the basis of a commercial interface specification for 3rd partie
Hi
Anne and Martin,
Thank
you both for your responses. I already tried to obtain the latest WSDL but it
wasn't available. I'll try the handler method.
Ken
-Original Message-From: Anne Thomas Manes
[mailto:[EMAIL PROTECTED]Sent: Monday, May 22, 2006 5:26
AMTo: axis-user@ws
Ken,I agree with Martin -- your service provider should supply you with a new WSDL. Have you tried just doing a GET on the service URL appended with "?wsdl"?. In the meantime, you can use a handler to validate the message. Java provides native support for validation in the
javax.xml.validation pac
Good Morning Ken
Who(m)ever is supplying the WSDL to you is responsible for specifying request
and response for all methods along with specifying
parameters to those methods.
Who(m)ever is changing the schema needs to re-gen and re-publish the WSDL
A situation arose where my webservice is now
Hello Ken,
Axis does not have the functionality to validate the SOAP message.
You should look for a third-party tool (hopefully others in the group
have suggestions) to do that or write one yourself.
Good luck,
Dies
Ken Tam wrote:
Hi all,
I am consuming web services made available from my c
1. I believe the XML of the request s already deserialized and parsed
by the time it reaches any handlers, and is in the form of a DOM. To
validate in a handler or in your service implementation you must be able
either to validate the DOM or, presumably less efficiently, serialize
back to a s
21 matches
Mail list logo
