You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Adnene <ab...@infovista.com> on 2006/05/29 12:09:42 UTC
[Axis 1.4] No deserializer for anyType
Hi all,
I have already posted this message in the "No deserializer for
{http://www.w3.org/2001/XMLSchema}anyType" thread. I suppose that since it
was a reply to this thread no body has noticed it.
I reposted it in new thread because the answers I found in previous
threads dose not help me to solve my problem. I suppose that my case is
slightly different.
Here is my case:
First of all I am new in using SOAP and AXIS.
I am writing a soap client for a third party server. I tried to generate
the stubs using AXIS 1.4 WSDL2Java. The WSDL structure that corresponds to
my problem is listed below.
But when I execute my test program that call executeSQLQuery I got an
exception with "No deserializer for
{http://www.w3.org/2001/XMLSchema}anyType" message. The SOP query succeeded
and the client application got the right answer but the answer is not
correctly parsed. It seems like the AXIS generated stubs can't deserialize
the xsd:anyType type.
I am not sure that I understand correctly what would represent such a type.
I suppose tha it should be interpreted as block of character or something
like the SQL blob type. In my case the <row> element whose type is anyType
should contain the rows returned by the sql query and may have any number of
columns depending on the SQL request itself. For example the answer may be:
<return>
<row>
<name>SEP000000000001</name>
<pkid>{49465272-5C37-41F8-BD0D-01BAB52D5770}</pkid>
<description>Auto 1001</description>
</row>
<row>
<name>SEP000000000002</name>
<pkid>{1E96EEB5-66F2-4766-A6B7-07D0337A8591}</pkid>
<description>Auto 1002</description>
</row>
</return>
Can any body help me get this work?
The WSDL structure is:
<xsd:complexType name="ExecuteSQLQueryReq">
<xsd:complexContent>
<xsd:extension base="axlapi:APIRequest">
<xsd:sequence>
<xsd:element name="sql" type="xsd:string" nillable="false">
<xsd:annotation>
<xsd:documentation>WARNING: SQL Large Text and BLOB columns
cannot be fetched along with other columns. A Large Text or BLOB column
must be selected in its own SQL query.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="executeSQLQuery" type="axlapi:ExecuteSQLQueryReq"
nillable="false">
<xsd:annotation>
<xsd:documentation>This API call is used to execute a Structured Query
Language query against the database. The sql element would contain the SQL
statement. If special characters are required, wrap the SQL command inside
a CDATA element.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="ExecuteSQLQueryRes">
<xsd:complexContent>
<xsd:extension base="axlapi:APIResponse">
<xsd:sequence>
<xsd:element name="return">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="row" type="xsd:anyType" minOccurs="0"
maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>Each row element can contain any number
of sub-elements, each sub-element is a column from that row in the result
set.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="executeSQLQueryResponse"
type="axlapi:ExecuteSQLQueryRes">
<xsd:annotation>
<xsd:documentation>The response message to executeSQLQuery. The return
element represents the result set, which can contain 0 or more rows of data.
Each row can have any number of elements as defined by columns specified in
the SQL Query. The name of each sub-element of the row element represents
the column name, the value of each sub-element of the row element is the
corresponding value of that column in the database.</xsd:documentation>
</xsd:annotation>
</xsd:element>
--
View this message in context: http://www.nabble.com/-Axis+1.4-+No+deserializer+for+anyType-t1698308.html#a4608778
Sent from the Axis - User forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis 1.4] No deserializer for anyType
Posted by rlelina <en...@raytheon.com>.
I'm also a beginner to Axis, using it via Eclipse 3.3. I have generated a
java web client to the Oracle TaskQueryService which has an anyType to
represent the payload to human task activities. I don't know yet what
version of Axis is being used but I am surprised that up to this time, there
is still no built-in anyType deserializer in Axis. I wonder if someone
already wrote one, and if not, I will have to write a simple one myself to
deserialize to a org.w3c.dom.Element. So how do I specify a deserializer
through a config file?
Thanks,
Rico
Anne Thomas Manes wrote:
>
> You can specify it either programmatically or using a client-side
> configuration file.
>
> On 8/23/06, msolnit <ms...@soasta.com> wrote:
>>
>> Hi everyone. I just came across this thread and it addresses the exact
>> same
>> problem I am having. Anne and Xinjun, I understand the different between
>> Document style and RPC style services. However, what I don't understand
>> is
>> how to specify a serializer in the Axis client. Is there any
>> documentation
>> on how to do this?
>>
>> I tried adding the following code to my "XXXBindingStub" class:
>>
>> qName = new
>> javax.xml.namespace.QName("http://www.w3.org/2001/XMLSchema", "anyType");
>> cachedSerQNames.add(qName);
>> cls = org.w3c.dom.Document.class;
>> cachedSerClasses.add(cls);
>> cachedSerFactories.add(beansf);
>> cachedDeserFactories.add(beandf);
>>
>> However, this leads to the error "Unable to create JavaBean of type
>> org.w3c.dom.Document. Missing default constructor? Error was:
>> java.lang.InstantiationException: org.w3c.dom.Document."
>>
>> This makes perfect sense since there is no default constructor for
>> org.w3c.dom.Document. However, what do I do now?
>>
>> Sincerely,
>> Matt Solnit
>>
>>
>> Xinjun Chen wrote:
>> >
>> > Adnene,
>> >
>> > The following two articles may help you to understand your problem. To
>> put
>> > it simple, the service style matters significantly!
>> > First one is Anne's explanation on RPC style and document style.
>> >
>> http://searchwebservices.techtarget.com/ateQuestionNResponse/0,289625,sid26_cid494324_tax289201,00.html
>> >
>> > The second one is from IBM developerworks. It describes the service
>> style
>> > and encoding very clearly.
>> > http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/
>> >
>> > For your problem, when you are using RPC style, the anyType works
>> because
>> > in
>> > your request message, the actual xsd type is specify and attached in
>> the
>> > request message. The server side relies on your request message (the
>> > acutal
>> > xsd type, say xsd:string, not xsd:anyType) to deserialize your XML into
>> > java
>> > object. However, in document style, the deserialization of request
>> message
>> > is based on a schema. This is a contract agreed upon between the
>> service
>> > client and the service provider. The representation of this agreement
>> is
>> > the
>> > <definitions>/<types>/<schema> in the service's WSDL file.
>> > When you use RPC style, the server side try to find a deserializer for
>> > xsd:string or other type specified in the request message to
>> deserialize
>> > your request message. When you switch from RPC style to Document style,
>> > the
>> > server side will try to find a deserializer for xsd:anyType from
>> > typemapping
>> > registry to deserialize the request message. However, you didn't
>> specify
>> > any
>> > serializer/deserializer for xsd:anyType, that's why you get that
>> > Exception.
>> >
>> > Therefore, Anne suggest you use DOM object, say org.w3c.Document.
>> >
>> > Hope this clear your doubts.
>> >
>> >
>> > Regards,
>> > Xinjun
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/-Axis-1.4--No-deserializer-for-anyType-tf1698308.html#a5948464
>> Sent from the Axis - User forum at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/-Axis-1.4--No-deserializer-for-anyType-tp4608778p25135366.html
Sent from the Axis - User mailing list archive at Nabble.com.
Re: [Axis 1.4] No deserializer for anyType
Posted by programmergreg <gr...@gmail.com>.
my solution was to remove the any tag from the xsd I used to generate the
stub. I know that's not possible for most people reading these posts, but
it's worth considering or looking though your xsds to make sure you really
need the any tag.
--
View this message in context: http://www.nabble.com/-Axis-1.4--No-deserializer-for-anyType-tf1698308.html#a8450509
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis 1.4] No deserializer for anyType
Posted by Anne Thomas Manes <at...@gmail.com>.
Take a look at the Users Guide.
Programmatically:
call.setReturnType( org.apache.axis.Constants.XSD_STRING );
or
call.setReturnClass(String.class);
You can also use the TypeMappingRegistry class:
org.apache.axis.encoding.TypeMappingRegistry
Or via configuration, define a config-client.wsdd file, and specify
your typemapping there.
Anne
On 8/23/06, msolnit <ms...@soasta.com> wrote:
>
> Hi Anne. Thanks for your response. I apologize if the questions I am asking
> are too beginner-ish, but I really can't find any documentation on this
> stuff. Can you be more specific? How do I specify it programatically? Are
> there any actual complete Java source code examples that demonstrate how do
> to this?
>
> Sincerely,
> Matt
>
>
> Anne Thomas Manes wrote:
> >
> > You can specify it either programmatically or using a client-side
> > configuration file.
> >
>
> --
> View this message in context: http://www.nabble.com/-Axis-1.4--No-deserializer-for-anyType-tf1698308.html#a5950508
> Sent from the Axis - User forum at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis 1.4] No deserializer for anyType
Posted by msolnit <ms...@soasta.com>.
Hi Anne. Thanks for your response. I apologize if the questions I am asking
are too beginner-ish, but I really can't find any documentation on this
stuff. Can you be more specific? How do I specify it programatically? Are
there any actual complete Java source code examples that demonstrate how do
to this?
Sincerely,
Matt
Anne Thomas Manes wrote:
>
> You can specify it either programmatically or using a client-side
> configuration file.
>
--
View this message in context: http://www.nabble.com/-Axis-1.4--No-deserializer-for-anyType-tf1698308.html#a5950508
Sent from the Axis - User forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis 1.4] No deserializer for anyType
Posted by Anne Thomas Manes <at...@gmail.com>.
You can specify it either programmatically or using a client-side
configuration file.
On 8/23/06, msolnit <ms...@soasta.com> wrote:
>
> Hi everyone. I just came across this thread and it addresses the exact same
> problem I am having. Anne and Xinjun, I understand the different between
> Document style and RPC style services. However, what I don't understand is
> how to specify a serializer in the Axis client. Is there any documentation
> on how to do this?
>
> I tried adding the following code to my "XXXBindingStub" class:
>
> qName = new
> javax.xml.namespace.QName("http://www.w3.org/2001/XMLSchema", "anyType");
> cachedSerQNames.add(qName);
> cls = org.w3c.dom.Document.class;
> cachedSerClasses.add(cls);
> cachedSerFactories.add(beansf);
> cachedDeserFactories.add(beandf);
>
> However, this leads to the error "Unable to create JavaBean of type
> org.w3c.dom.Document. Missing default constructor? Error was:
> java.lang.InstantiationException: org.w3c.dom.Document."
>
> This makes perfect sense since there is no default constructor for
> org.w3c.dom.Document. However, what do I do now?
>
> Sincerely,
> Matt Solnit
>
>
> Xinjun Chen wrote:
> >
> > Adnene,
> >
> > The following two articles may help you to understand your problem. To put
> > it simple, the service style matters significantly!
> > First one is Anne's explanation on RPC style and document style.
> > http://searchwebservices.techtarget.com/ateQuestionNResponse/0,289625,sid26_cid494324_tax289201,00.html
> >
> > The second one is from IBM developerworks. It describes the service style
> > and encoding very clearly.
> > http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/
> >
> > For your problem, when you are using RPC style, the anyType works because
> > in
> > your request message, the actual xsd type is specify and attached in the
> > request message. The server side relies on your request message (the
> > acutal
> > xsd type, say xsd:string, not xsd:anyType) to deserialize your XML into
> > java
> > object. However, in document style, the deserialization of request message
> > is based on a schema. This is a contract agreed upon between the service
> > client and the service provider. The representation of this agreement is
> > the
> > <definitions>/<types>/<schema> in the service's WSDL file.
> > When you use RPC style, the server side try to find a deserializer for
> > xsd:string or other type specified in the request message to deserialize
> > your request message. When you switch from RPC style to Document style,
> > the
> > server side will try to find a deserializer for xsd:anyType from
> > typemapping
> > registry to deserialize the request message. However, you didn't specify
> > any
> > serializer/deserializer for xsd:anyType, that's why you get that
> > Exception.
> >
> > Therefore, Anne suggest you use DOM object, say org.w3c.Document.
> >
> > Hope this clear your doubts.
> >
> >
> > Regards,
> > Xinjun
> >
>
> --
> View this message in context: http://www.nabble.com/-Axis-1.4--No-deserializer-for-anyType-tf1698308.html#a5948464
> Sent from the Axis - User forum at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis 1.4] No deserializer for anyType
Posted by msolnit <ms...@soasta.com>.
Hi everyone. I just came across this thread and it addresses the exact same
problem I am having. Anne and Xinjun, I understand the different between
Document style and RPC style services. However, what I don't understand is
how to specify a serializer in the Axis client. Is there any documentation
on how to do this?
I tried adding the following code to my "XXXBindingStub" class:
qName = new
javax.xml.namespace.QName("http://www.w3.org/2001/XMLSchema", "anyType");
cachedSerQNames.add(qName);
cls = org.w3c.dom.Document.class;
cachedSerClasses.add(cls);
cachedSerFactories.add(beansf);
cachedDeserFactories.add(beandf);
However, this leads to the error "Unable to create JavaBean of type
org.w3c.dom.Document. Missing default constructor? Error was:
java.lang.InstantiationException: org.w3c.dom.Document."
This makes perfect sense since there is no default constructor for
org.w3c.dom.Document. However, what do I do now?
Sincerely,
Matt Solnit
Xinjun Chen wrote:
>
> Adnene,
>
> The following two articles may help you to understand your problem. To put
> it simple, the service style matters significantly!
> First one is Anne's explanation on RPC style and document style.
> http://searchwebservices.techtarget.com/ateQuestionNResponse/0,289625,sid26_cid494324_tax289201,00.html
>
> The second one is from IBM developerworks. It describes the service style
> and encoding very clearly.
> http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/
>
> For your problem, when you are using RPC style, the anyType works because
> in
> your request message, the actual xsd type is specify and attached in the
> request message. The server side relies on your request message (the
> acutal
> xsd type, say xsd:string, not xsd:anyType) to deserialize your XML into
> java
> object. However, in document style, the deserialization of request message
> is based on a schema. This is a contract agreed upon between the service
> client and the service provider. The representation of this agreement is
> the
> <definitions>/<types>/<schema> in the service's WSDL file.
> When you use RPC style, the server side try to find a deserializer for
> xsd:string or other type specified in the request message to deserialize
> your request message. When you switch from RPC style to Document style,
> the
> server side will try to find a deserializer for xsd:anyType from
> typemapping
> registry to deserialize the request message. However, you didn't specify
> any
> serializer/deserializer for xsd:anyType, that's why you get that
> Exception.
>
> Therefore, Anne suggest you use DOM object, say org.w3c.Document.
>
> Hope this clear your doubts.
>
>
> Regards,
> Xinjun
>
--
View this message in context: http://www.nabble.com/-Axis-1.4--No-deserializer-for-anyType-tf1698308.html#a5948464
Sent from the Axis - User forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis 1.4] No deserializer for anyType
Posted by Xinjun Chen <xj...@gmail.com>.
Adnene,
The following two articles may help you to understand your problem. To put
it simple, the service style matters significantly!
First one is Anne's explanation on RPC style and document style.
http://searchwebservices.techtarget.com/ateQuestionNResponse/0,289625,sid26_cid494324_tax289201,00.html
The second one is from IBM developerworks. It describes the service style
and encoding very clearly.
http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/
For your problem, when you are using RPC style, the anyType works because in
your request message, the actual xsd type is specify and attached in the
request message. The server side relies on your request message (the acutal
xsd type, say xsd:string, not xsd:anyType) to deserialize your XML into java
object. However, in document style, the deserialization of request message
is based on a schema. This is a contract agreed upon between the service
client and the service provider. The representation of this agreement is the
<definitions>/<types>/<schema> in the service's WSDL file.
When you use RPC style, the server side try to find a deserializer for
xsd:string or other type specified in the request message to deserialize
your request message. When you switch from RPC style to Document style, the
server side will try to find a deserializer for xsd:anyType from typemapping
registry to deserialize the request message. However, you didn't specify any
serializer/deserializer for xsd:anyType, that's why you get that Exception.
Therefore, Anne suggest you use DOM object, say org.w3c.Document.
Hope this clear your doubts.
Regards,
Xinjun
On 5/29/06, Adnene <ab...@infovista.com> wrote:
>
>
> Thank you Anne For your quick answer,
>
> Since I am new with Axis and SOAP, do you have any reference or
> documentation to point me to, so I can find out the way to tell Axis how
> to
> process this information?
> An example would of a great help for me.
>
> Thank you again for precious help,
>
> Adnene
>
> --
> View this message in context:
> http://www.nabble.com/-Axis+1.4-+No+deserializer+for+anyType-t1698308.html#a4611715
> Sent from the Axis - User forum at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
Re: [Axis 1.4] No deserializer for anyType
Posted by Adnene <ab...@infovista.com>.
Thank you Anne For your quick answer,
Since I am new with Axis and SOAP, do you have any reference or
documentation to point me to, so I can find out the way to tell Axis how to
process this information?
An example would of a great help for me.
Thank you again for precious help,
Adnene
--
View this message in context: http://www.nabble.com/-Axis+1.4-+No+deserializer+for+anyType-t1698308.html#a4611715
Sent from the Axis - User forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: [Axis 1.4] No deserializer for anyType
Posted by Anne Thomas Manes <at...@gmail.com>.
You must tell Axis how to process this information. Since you have no idea
what the returned data will look like, I suggest you tell Axis to take the
response and turn it into DOM. Then you can process the XML
programmatically.
Anne
On 5/29/06, Adnene <ab...@infovista.com> wrote:
>
>
> Hi all,
>
> I have already posted this message in the "No deserializer for
> {http://www.w3.org/2001/XMLSchema}anyType" thread. I suppose that since it
> was a reply to this thread no body has noticed it.
> I reposted it in new thread because the answers I found in previous
> threads dose not help me to solve my problem. I suppose that my case is
> slightly different.
>
> Here is my case:
>
> First of all I am new in using SOAP and AXIS.
> I am writing a soap client for a third party server. I tried to
> generate
> the stubs using AXIS 1.4 WSDL2Java. The WSDL structure that corresponds to
> my problem is listed below.
> But when I execute my test program that call executeSQLQuery I got an
> exception with "No deserializer for
> {http://www.w3.org/2001/XMLSchema}anyType" message. The SOP query
> succeeded
> and the client application got the right answer but the answer is not
> correctly parsed. It seems like the AXIS generated stubs can't deserialize
> the xsd:anyType type.
> I am not sure that I understand correctly what would represent such a
> type.
> I suppose tha it should be interpreted as block of character or something
> like the SQL blob type. In my case the <row> element whose type is anyType
> should contain the rows returned by the sql query and may have any number
> of
> columns depending on the SQL request itself. For example the answer may
> be:
>
> <return>
> <row>
> <name>SEP000000000001</name>
> <pkid>{49465272-5C37-41F8-BD0D-01BAB52D5770}</pkid>
> <description>Auto 1001</description>
> </row>
> <row>
> <name>SEP000000000002</name>
> <pkid>{1E96EEB5-66F2-4766-A6B7-07D0337A8591}</pkid>
> <description>Auto 1002</description>
> </row>
> </return>
>
> Can any body help me get this work?
>
> The WSDL structure is:
> <xsd:complexType name="ExecuteSQLQueryReq">
> <xsd:complexContent>
> <xsd:extension base="axlapi:APIRequest">
> <xsd:sequence>
> <xsd:element name="sql" type="xsd:string" nillable="false">
> <xsd:annotation>
> <xsd:documentation>WARNING: SQL Large Text and BLOB columns
> cannot be fetched along with other columns. A Large Text or BLOB column
> must be selected in its own SQL query.</xsd:documentation>
> </xsd:annotation>
> </xsd:element>
> </xsd:sequence>
> </xsd:extension>
> </xsd:complexContent>
> </xsd:complexType>
> <xsd:element name="executeSQLQuery" type="axlapi:ExecuteSQLQueryReq"
> nillable="false">
> <xsd:annotation>
> <xsd:documentation>This API call is used to execute a Structured Query
> Language query against the database. The sql element would contain the
> SQL
> statement. If special characters are required, wrap the SQL command
> inside
> a CDATA element.</xsd:documentation>
> </xsd:annotation>
> </xsd:element>
> <xsd:complexType name="ExecuteSQLQueryRes">
> <xsd:complexContent>
> <xsd:extension base="axlapi:APIResponse">
> <xsd:sequence>
> <xsd:element name="return">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element name="row" type="xsd:anyType" minOccurs="0"
> maxOccurs="unbounded">
> <xsd:annotation>
> <xsd:documentation>Each row element can contain any
> number
> of sub-elements, each sub-element is a column from that row in the result
> set.</xsd:documentation>
> </xsd:annotation>
> </xsd:element>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> </xsd:sequence>
> </xsd:extension>
> </xsd:complexContent>
> </xsd:complexType>
> <xsd:element name="executeSQLQueryResponse"
> type="axlapi:ExecuteSQLQueryRes">
> <xsd:annotation>
> <xsd:documentation>The response message to executeSQLQuery. The
> return
> element represents the result set, which can contain 0 or more rows of
> data.
> Each row can have any number of elements as defined by columns specified
> in
> the SQL Query. The name of each sub-element of the row element represents
> the column name, the value of each sub-element of the row element is the
> corresponding value of that column in the database.</xsd:documentation>
> </xsd:annotation>
> </xsd:element>
> --
> View this message in context:
> http://www.nabble.com/-Axis+1.4-+No+deserializer+for+anyType-t1698308.html#a4608778
> Sent from the Axis - User forum at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>