[prev in list] [next in list] [prev in thread] [next in thread]
List: axis-user
Subject: Re: some questions
From: "Glen Daniels" <gdaniels () macromedia ! com>
Date: 2002-04-06 17:44:21
[Download RAW message or body]
Hi June!
1. All of our validation is currently in the deserializers. The schema information \
(i.e. what XML to expect when) exists in the form of a TypeDesc \
(org.apache.axis.description.TypeDesc) for JavaBeans, which is the common case. This \
will match up elements/attributes to the appropriate Java accessors, but will not \
handle validating more complex schema constraints about values (well, we do handle \
enumerated types, but not, for instance, "integers from 0 to 100"). We plan to add \
this richer schema validation support later.
2. I'm not quite sure what you're asking here. Our serializaition/deserialization \
mechanism does not rely on "RPC-ness" at all, and in fact there are several doc/lit \
examples in our tests (see test.wsdl.nested, or test.wsdl.literal) which use \
XML<->Java databinding in a document style. If you're talking about passing \
SOAPElements or DOM Elements around, we support that to a limited extent now and will \
improve this stuff later as well.
Hope this helps,
--Glen
----- Original Message -----
From: Ma, June
To: 'axis-user@xml.apache.org'
Sent: Friday, April 05, 2002 9:09 PM
Subject: some questions
Hi AXIS experts,
I reviewed this AXIS package and have some questions that I can't figure out the \
answer. I'd appreciate if you can give me some help. 1. Do you ever do any kind of \
xml instance validation? If you do, how do you figure out the schema location \
information ?
2. We are doing the document based SOAP service. I noticed that none of the base \
classes extends java.io.Serializable. How do you make the soap message itself \
serializable ? There are plenty of discussions about different data type \
serialization, aren't these all around the RPC calls ?
Thanks,
-June
[Attachment #3 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2715.400" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi June!</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>1. All of our validation is currently in the
deserializers. The schema information (i.e. what XML to expect when)
exists in the form of a TypeDesc (org.apache.axis.description.TypeDesc) for
JavaBeans, which is the common case. This will match up
elements/attributes to the appropriate Java accessors, but will not handle
validating more complex schema constraints about values (well, we do handle
enumerated types, but not, for instance, "integers from 0 to 100"). We
plan to add this richer schema validation support later.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>2. I'm not quite sure what you're asking
here. Our serializaition/deserialization mechanism does not rely on
"RPC-ness" at all, and in fact there are several doc/lit examples in our tests
(see test.wsdl.nested, or test.wsdl.literal) which use XML<->Java
databinding in a document style. If you're talking about passing
SOAPElements or DOM Elements around, we support that to a limited extent now and
will improve this stuff later as well.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Hope this helps,</FONT></DIV>
<DIV><FONT face=Arial size=2>--Glen</FONT></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 \
2px solid; MARGIN-RIGHT: 0px"> <DIV style="FONT: 10pt arial">----- Original Message \
----- </DIV> <DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=june.ma@commerceone.com href="mailto:june.ma@commerceone.com">Ma,
June</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=axis-user@xml.apache.org
href="mailto:'axis-user@xml.apache.org'">'axis-user@xml.apache.org'</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, April 05, 2002 9:09
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> some questions</DIV>
<DIV><BR></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=586094913-05042002>Hi
AXIS experts,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=586094913-05042002></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=586094913-05042002>I reviewed this AXIS package and have some
questions that I can't figure out the answer. I'd appreciate if you can give
me some help.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=586094913-05042002>1.
Do you ever do any kind of xml instance validation? If you do, how do you
figure out the schema location information ?</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=586094913-05042002></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=586094913-05042002>2.
We are doing the document based SOAP service. I noticed that
none of the base classes extends java.io.Serializable. How
do you make the soap message itself serializable ? There are plenty of
discussions about different data type serialization, aren't these all around
the RPC calls ? </SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=586094913-05042002>Thanks,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=586094913-05042002>-June</SPAN></FONT></DIV></BLOCKQUOTE></BODY></HTML>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic