You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@ws.apache.org by s....@tin.it on 2002/07/24 10:00:26 UTC
Problems with complexType again
Hi, I'm here again...
Indrasish,
yesterday you told me that there is a solution, please tell me this solution.
Yes, the webservice is written in .NET and client in Java, the webservice
use MS.NET as SOAP implementation while i use Apache SOAP.
Thanks
Re: BeanSerializer problem. Gurus Please help.
Posted by Scott Nichol <sn...@scottnichol.com>.
No example.
----- Original Message -----
From: "Indrasish N Basuroychowdhury"
<in...@fanniemae.com>
To: <so...@xml.apache.org>
Sent: Wednesday, July 24, 2002 12:28 PM
Subject: Re: BeanSerializer problem. Gurus Please help.
> Thanks Scott. Any example of how to use BeanInfo?
>
> Thanks,
>
> Indrasish.
>
> Scott Nichol wrote:
>
> > Indrasish,
> >
> > I believe that BeanInfo is the way to force the use of the leading upper
> > case character.
> >
> > Scott Nichol
> >
> > ----- Original Message -----
> > From: "Indrasish N Basuroychowdhury"
> > <in...@fanniemae.com>
> > To: <so...@xml.apache.org>
> > Sent: Wednesday, July 24, 2002 12:07 PM
> > Subject: BeanSerializer problem. Gurus Please help.
> >
> > > Now I need a help from you all gurus.
> > > I have already written clients for sending/receiving datasets using
> > > literal/document.
> > > Now I am trying to write clients using encoded style which Apache
uses.
> > There
> > > are lot of issues and I could solve most of them. There are too many
> > interop
> > > problems. However, I could now send and receive object.
> > > There is one problem though.
> > > I am using java Bean and using BeanSerializer of Apache to serialize
and
> > send
> > > messages. There is one problem though. This is with the data member
naming
> > > convention. If I use data member name UserName, the Bean serializer
will
> > conver
> > > it to userName and send it to the webservice. This is as per the Bean
> > > specification as he first letter will be decapitalized unless the
second
> > letter
> > > of the member is also capital. i.e. UserName will be cchanged to
userName
> > but
> > > USERNAME will be left as it is.
> > > In the .Net side, it will be expecting UserName and won't find it and
as
> > such it
> > > will not assign the value to that particular variable.
> > > Anyone has any idea of how to overcome it.
> > > i.e. how can I use member name UserName and not let the Bean conver
it.
> > Can we
> > > do it by BeanInfo or similar interface.
> > >
> > > Thanks,
> > >
> > > Indrasish.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > > For additional commands, e-mail: <ma...@xml.apache.org>
> > >
> > >
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: BeanSerializer problem. Gurus Please help.
Posted by Scott Nichol <sn...@scottnichol.com>.
No example.
----- Original Message -----
From: "Indrasish N Basuroychowdhury"
<in...@fanniemae.com>
To: <so...@xml.apache.org>
Sent: Wednesday, July 24, 2002 12:28 PM
Subject: Re: BeanSerializer problem. Gurus Please help.
> Thanks Scott. Any example of how to use BeanInfo?
>
> Thanks,
>
> Indrasish.
>
> Scott Nichol wrote:
>
> > Indrasish,
> >
> > I believe that BeanInfo is the way to force the use of the leading upper
> > case character.
> >
> > Scott Nichol
> >
> > ----- Original Message -----
> > From: "Indrasish N Basuroychowdhury"
> > <in...@fanniemae.com>
> > To: <so...@xml.apache.org>
> > Sent: Wednesday, July 24, 2002 12:07 PM
> > Subject: BeanSerializer problem. Gurus Please help.
> >
> > > Now I need a help from you all gurus.
> > > I have already written clients for sending/receiving datasets using
> > > literal/document.
> > > Now I am trying to write clients using encoded style which Apache
uses.
> > There
> > > are lot of issues and I could solve most of them. There are too many
> > interop
> > > problems. However, I could now send and receive object.
> > > There is one problem though.
> > > I am using java Bean and using BeanSerializer of Apache to serialize
and
> > send
> > > messages. There is one problem though. This is with the data member
naming
> > > convention. If I use data member name UserName, the Bean serializer
will
> > conver
> > > it to userName and send it to the webservice. This is as per the Bean
> > > specification as he first letter will be decapitalized unless the
second
> > letter
> > > of the member is also capital. i.e. UserName will be cchanged to
userName
> > but
> > > USERNAME will be left as it is.
> > > In the .Net side, it will be expecting UserName and won't find it and
as
> > such it
> > > will not assign the value to that particular variable.
> > > Anyone has any idea of how to overcome it.
> > > i.e. how can I use member name UserName and not let the Bean conver
it.
> > Can we
> > > do it by BeanInfo or similar interface.
> > >
> > > Thanks,
> > >
> > > Indrasish.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > > For additional commands, e-mail: <ma...@xml.apache.org>
> > >
> > >
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Re: BeanSerializer problem. Gurus Please help.
Posted by Indrasish N Basuroychowdhury <in...@fanniemae.com>.
Thanks Scott. Any example of how to use BeanInfo?
Thanks,
Indrasish.
Scott Nichol wrote:
> Indrasish,
>
> I believe that BeanInfo is the way to force the use of the leading upper
> case character.
>
> Scott Nichol
>
> ----- Original Message -----
> From: "Indrasish N Basuroychowdhury"
> <in...@fanniemae.com>
> To: <so...@xml.apache.org>
> Sent: Wednesday, July 24, 2002 12:07 PM
> Subject: BeanSerializer problem. Gurus Please help.
>
> > Now I need a help from you all gurus.
> > I have already written clients for sending/receiving datasets using
> > literal/document.
> > Now I am trying to write clients using encoded style which Apache uses.
> There
> > are lot of issues and I could solve most of them. There are too many
> interop
> > problems. However, I could now send and receive object.
> > There is one problem though.
> > I am using java Bean and using BeanSerializer of Apache to serialize and
> send
> > messages. There is one problem though. This is with the data member naming
> > convention. If I use data member name UserName, the Bean serializer will
> conver
> > it to userName and send it to the webservice. This is as per the Bean
> > specification as he first letter will be decapitalized unless the second
> letter
> > of the member is also capital. i.e. UserName will be cchanged to userName
> but
> > USERNAME will be left as it is.
> > In the .Net side, it will be expecting UserName and won't find it and as
> such it
> > will not assign the value to that particular variable.
> > Anyone has any idea of how to overcome it.
> > i.e. how can I use member name UserName and not let the Bean conver it.
> Can we
> > do it by BeanInfo or similar interface.
> >
> > Thanks,
> >
> > Indrasish.
> >
> >
> >
> >
> >
> >
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
> >
> >
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: BeanSerializer problem. Gurus Please help.
Posted by Indrasish N Basuroychowdhury <in...@fanniemae.com>.
Thanks Scott. Any example of how to use BeanInfo?
Thanks,
Indrasish.
Scott Nichol wrote:
> Indrasish,
>
> I believe that BeanInfo is the way to force the use of the leading upper
> case character.
>
> Scott Nichol
>
> ----- Original Message -----
> From: "Indrasish N Basuroychowdhury"
> <in...@fanniemae.com>
> To: <so...@xml.apache.org>
> Sent: Wednesday, July 24, 2002 12:07 PM
> Subject: BeanSerializer problem. Gurus Please help.
>
> > Now I need a help from you all gurus.
> > I have already written clients for sending/receiving datasets using
> > literal/document.
> > Now I am trying to write clients using encoded style which Apache uses.
> There
> > are lot of issues and I could solve most of them. There are too many
> interop
> > problems. However, I could now send and receive object.
> > There is one problem though.
> > I am using java Bean and using BeanSerializer of Apache to serialize and
> send
> > messages. There is one problem though. This is with the data member naming
> > convention. If I use data member name UserName, the Bean serializer will
> conver
> > it to userName and send it to the webservice. This is as per the Bean
> > specification as he first letter will be decapitalized unless the second
> letter
> > of the member is also capital. i.e. UserName will be cchanged to userName
> but
> > USERNAME will be left as it is.
> > In the .Net side, it will be expecting UserName and won't find it and as
> such it
> > will not assign the value to that particular variable.
> > Anyone has any idea of how to overcome it.
> > i.e. how can I use member name UserName and not let the Bean conver it.
> Can we
> > do it by BeanInfo or similar interface.
> >
> > Thanks,
> >
> > Indrasish.
> >
> >
> >
> >
> >
> >
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
> >
> >
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
Re: BeanSerializer problem. Gurus Please help.
Posted by Scott Nichol <sn...@scottnichol.com>.
Indrasish,
I believe that BeanInfo is the way to force the use of the leading upper
case character.
Scott Nichol
----- Original Message -----
From: "Indrasish N Basuroychowdhury"
<in...@fanniemae.com>
To: <so...@xml.apache.org>
Sent: Wednesday, July 24, 2002 12:07 PM
Subject: BeanSerializer problem. Gurus Please help.
> Now I need a help from you all gurus.
> I have already written clients for sending/receiving datasets using
> literal/document.
> Now I am trying to write clients using encoded style which Apache uses.
There
> are lot of issues and I could solve most of them. There are too many
interop
> problems. However, I could now send and receive object.
> There is one problem though.
> I am using java Bean and using BeanSerializer of Apache to serialize and
send
> messages. There is one problem though. This is with the data member naming
> convention. If I use data member name UserName, the Bean serializer will
conver
> it to userName and send it to the webservice. This is as per the Bean
> specification as he first letter will be decapitalized unless the second
letter
> of the member is also capital. i.e. UserName will be cchanged to userName
but
> USERNAME will be left as it is.
> In the .Net side, it will be expecting UserName and won't find it and as
such it
> will not assign the value to that particular variable.
> Anyone has any idea of how to overcome it.
> i.e. how can I use member name UserName and not let the Bean conver it.
Can we
> do it by BeanInfo or similar interface.
>
> Thanks,
>
> Indrasish.
>
>
>
>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: BeanSerializer problem. Gurus Please help.
Posted by Scott Nichol <sn...@scottnichol.com>.
Indrasish,
I believe that BeanInfo is the way to force the use of the leading upper
case character.
Scott Nichol
----- Original Message -----
From: "Indrasish N Basuroychowdhury"
<in...@fanniemae.com>
To: <so...@xml.apache.org>
Sent: Wednesday, July 24, 2002 12:07 PM
Subject: BeanSerializer problem. Gurus Please help.
> Now I need a help from you all gurus.
> I have already written clients for sending/receiving datasets using
> literal/document.
> Now I am trying to write clients using encoded style which Apache uses.
There
> are lot of issues and I could solve most of them. There are too many
interop
> problems. However, I could now send and receive object.
> There is one problem though.
> I am using java Bean and using BeanSerializer of Apache to serialize and
send
> messages. There is one problem though. This is with the data member naming
> convention. If I use data member name UserName, the Bean serializer will
conver
> it to userName and send it to the webservice. This is as per the Bean
> specification as he first letter will be decapitalized unless the second
letter
> of the member is also capital. i.e. UserName will be cchanged to userName
but
> USERNAME will be left as it is.
> In the .Net side, it will be expecting UserName and won't find it and as
such it
> will not assign the value to that particular variable.
> Anyone has any idea of how to overcome it.
> i.e. how can I use member name UserName and not let the Bean conver it.
Can we
> do it by BeanInfo or similar interface.
>
> Thanks,
>
> Indrasish.
>
>
>
>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
BeanSerializer problem. Gurus Please help.
Posted by Indrasish N Basuroychowdhury <in...@fanniemae.com>.
Now I need a help from you all gurus.
I have already written clients for sending/receiving datasets using
literal/document.
Now I am trying to write clients using encoded style which Apache uses. There
are lot of issues and I could solve most of them. There are too many interop
problems. However, I could now send and receive object.
There is one problem though.
I am using java Bean and using BeanSerializer of Apache to serialize and send
messages. There is one problem though. This is with the data member naming
convention. If I use data member name UserName, the Bean serializer will conver
it to userName and send it to the webservice. This is as per the Bean
specification as he first letter will be decapitalized unless the second letter
of the member is also capital. i.e. UserName will be cchanged to userName but
USERNAME will be left as it is.
In the .Net side, it will be expecting UserName and won't find it and as such it
will not assign the value to that particular variable.
Anyone has any idea of how to overcome it.
i.e. how can I use member name UserName and not let the Bean conver it. Can we
do it by BeanInfo or similar interface.
Thanks,
Indrasish.
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
BeanSerializer problem. Gurus Please help.
Posted by Indrasish N Basuroychowdhury <in...@fanniemae.com>.
Now I need a help from you all gurus.
I have already written clients for sending/receiving datasets using
literal/document.
Now I am trying to write clients using encoded style which Apache uses. There
are lot of issues and I could solve most of them. There are too many interop
problems. However, I could now send and receive object.
There is one problem though.
I am using java Bean and using BeanSerializer of Apache to serialize and send
messages. There is one problem though. This is with the data member naming
convention. If I use data member name UserName, the Bean serializer will conver
it to userName and send it to the webservice. This is as per the Bean
specification as he first letter will be decapitalized unless the second letter
of the member is also capital. i.e. UserName will be cchanged to userName but
USERNAME will be left as it is.
In the .Net side, it will be expecting UserName and won't find it and as such it
will not assign the value to that particular variable.
Anyone has any idea of how to overcome it.
i.e. how can I use member name UserName and not let the Bean conver it. Can we
do it by BeanInfo or similar interface.
Thanks,
Indrasish.
Re: Problems with complexType again
Posted by Scott Nichol <sn...@scottnichol.com>.
Thanks.
----- Original Message -----
From: "Indrasish N Basuroychowdhury"
<in...@fanniemae.com>
To: <so...@xml.apache.org>
Sent: Wednesday, July 24, 2002 11:08 AM
Subject: Re: Problems with complexType again
> Scott,
>
> Here we go.
>
> http://support.microsoft.com/directory/article.asp?id=q308466&sd=msdn
>
> You might have to serch for id=q308466 to get to the article. It has
sample code
> too.
>
> Sonia,
>
> You may like to look into this article too.
>
> Thanks,
>
> Indrasish.
>
> Scott Nichol wrote:
>
> > Indrasish,
> >
> > Do you recall more specifically? I grabbed the source for the article I
> > found on MSDN, but discovered that it uses the Favorites service, which
is
> > rpc/encoded, not document/literal.
> >
> > Scott Nichol
> >
> > ----- Original Message -----
> > From: "Indrasish N Basuroychowdhury"
> > <in...@fanniemae.com>
> > To: <so...@xml.apache.org>
> > Sent: Wednesday, July 24, 2002 10:43 AM
> > Subject: Re: Problems with complexType again
> >
> > > Scott,
> > >
> > > It is similar. But one I picked up is from yahoogroups.
> > >
> > > Thanks,
> > >
> > > Indrasish.
> > >
> > > Scott Nichol wrote:
> > >
> > > > Indrasish,
> > > >
> > > > Thanks for the info on the Scott Sealy article. Is the one of which
you
> > > > speak at
> > > >
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservice/h
> > > > tml/service08152001.asp?
> > > >
> > > > Scott Nichol
> > > >
> > > > ----- Original Message -----
> > > > From: "Indrasish N Basuroychowdhury"
> > > > <in...@fanniemae.com>
> > > > To: <so...@xml.apache.org>
> > > > Sent: Wednesday, July 24, 2002 9:55 AM
> > > > Subject: Re: Problems with complexType again
> > > >
> > > > > Sonia,
> > > > >
> > > > > .NET webservice by default uses literal/document type. Where as
Apache
> > > > uses
> > > > > encoded type (RPC). You have to change the .NET service to use
encoded
> > > > type. That
> > > > > can be done by adding [SoapRpcMethod] beside [WebMethod] while
> > building
> > > > .NET
> > > > > webservice. This is valid only if you own the webservice.
> > > > > If not you have two options:
> > > > > 1. Follow Scotts suggestion of switching to Axis.
> > > > > 2. Else, there is an example provided by Scott Sealy of Microsoft
in
> > which
> > > > he
> > > > > shows how to send and receive documents using Apache. You have to
> > build
> > > > Body,
> > > > > Header, ClientHandler and the proxy by yourself. Tedious, but
works.
> > In
> > > > fact that
> > > > > is the only way I could send and receive Dataset.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Indrasish.
> > > > >
> > > > > s.vignaroli@tin.it wrote:
> > > > >
> > > > > > Hi, I'm here again...
> > > > > > Indrasish,
> > > > > > yesterday you told me that there is a solution, please tell me
this
> > > > solution.
> > > > > > Yes, the webservice is written in .NET and client in Java, the
> > > > webservice
> > > > > > use MS.NET as SOAP implementation while i use Apache SOAP.
> > > > > > Thanks
> > > > > >
> > > > > > --
> > > > > > To unsubscribe, e-mail:
> > <ma...@xml.apache.org>
> > > > > > For additional commands, e-mail:
> > <ma...@xml.apache.org>
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > To unsubscribe, e-mail:
<ma...@xml.apache.org>
> > > > > For additional commands, e-mail:
<ma...@xml.apache.org>
> > > > >
> > > > >
> > > >
> > > > --
> > > > To unsubscribe, e-mail:
<ma...@xml.apache.org>
> > > > For additional commands, e-mail:
<ma...@xml.apache.org>
> > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > > For additional commands, e-mail: <ma...@xml.apache.org>
> > >
> > >
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Re: Problems with complexType again
Posted by Scott Nichol <sn...@scottnichol.com>.
Thanks.
----- Original Message -----
From: "Indrasish N Basuroychowdhury"
<in...@fanniemae.com>
To: <so...@xml.apache.org>
Sent: Wednesday, July 24, 2002 11:08 AM
Subject: Re: Problems with complexType again
> Scott,
>
> Here we go.
>
> http://support.microsoft.com/directory/article.asp?id=q308466&sd=msdn
>
> You might have to serch for id=q308466 to get to the article. It has
sample code
> too.
>
> Sonia,
>
> You may like to look into this article too.
>
> Thanks,
>
> Indrasish.
>
> Scott Nichol wrote:
>
> > Indrasish,
> >
> > Do you recall more specifically? I grabbed the source for the article I
> > found on MSDN, but discovered that it uses the Favorites service, which
is
> > rpc/encoded, not document/literal.
> >
> > Scott Nichol
> >
> > ----- Original Message -----
> > From: "Indrasish N Basuroychowdhury"
> > <in...@fanniemae.com>
> > To: <so...@xml.apache.org>
> > Sent: Wednesday, July 24, 2002 10:43 AM
> > Subject: Re: Problems with complexType again
> >
> > > Scott,
> > >
> > > It is similar. But one I picked up is from yahoogroups.
> > >
> > > Thanks,
> > >
> > > Indrasish.
> > >
> > > Scott Nichol wrote:
> > >
> > > > Indrasish,
> > > >
> > > > Thanks for the info on the Scott Sealy article. Is the one of which
you
> > > > speak at
> > > >
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservice/h
> > > > tml/service08152001.asp?
> > > >
> > > > Scott Nichol
> > > >
> > > > ----- Original Message -----
> > > > From: "Indrasish N Basuroychowdhury"
> > > > <in...@fanniemae.com>
> > > > To: <so...@xml.apache.org>
> > > > Sent: Wednesday, July 24, 2002 9:55 AM
> > > > Subject: Re: Problems with complexType again
> > > >
> > > > > Sonia,
> > > > >
> > > > > .NET webservice by default uses literal/document type. Where as
Apache
> > > > uses
> > > > > encoded type (RPC). You have to change the .NET service to use
encoded
> > > > type. That
> > > > > can be done by adding [SoapRpcMethod] beside [WebMethod] while
> > building
> > > > .NET
> > > > > webservice. This is valid only if you own the webservice.
> > > > > If not you have two options:
> > > > > 1. Follow Scotts suggestion of switching to Axis.
> > > > > 2. Else, there is an example provided by Scott Sealy of Microsoft
in
> > which
> > > > he
> > > > > shows how to send and receive documents using Apache. You have to
> > build
> > > > Body,
> > > > > Header, ClientHandler and the proxy by yourself. Tedious, but
works.
> > In
> > > > fact that
> > > > > is the only way I could send and receive Dataset.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Indrasish.
> > > > >
> > > > > s.vignaroli@tin.it wrote:
> > > > >
> > > > > > Hi, I'm here again...
> > > > > > Indrasish,
> > > > > > yesterday you told me that there is a solution, please tell me
this
> > > > solution.
> > > > > > Yes, the webservice is written in .NET and client in Java, the
> > > > webservice
> > > > > > use MS.NET as SOAP implementation while i use Apache SOAP.
> > > > > > Thanks
> > > > > >
> > > > > > --
> > > > > > To unsubscribe, e-mail:
> > <ma...@xml.apache.org>
> > > > > > For additional commands, e-mail:
> > <ma...@xml.apache.org>
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > To unsubscribe, e-mail:
<ma...@xml.apache.org>
> > > > > For additional commands, e-mail:
<ma...@xml.apache.org>
> > > > >
> > > > >
> > > >
> > > > --
> > > > To unsubscribe, e-mail:
<ma...@xml.apache.org>
> > > > For additional commands, e-mail:
<ma...@xml.apache.org>
> > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > > For additional commands, e-mail: <ma...@xml.apache.org>
> > >
> > >
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Problems with complexType again
Posted by s....@tin.it.
Scott, Indrasish,
thanks for the articles, I'll read them then I'll try again following your
advices.
Bye, for now...
>-- Messaggio originale --
>Reply-To: soap-dev@xml.apache.org
>Date: Wed, 24 Jul 2002 11:08:53 -0400
>From: "Indrasish N Basuroychowdhury"
> <in...@fanniemae.com>
>To: soap-dev@xml.apache.org
>Subject: Re: Problems with complexType again
>
>
>Scott,
>
>Here we go.
>
>http://support.microsoft.com/directory/article.asp?id=q308466&sd=msdn
>
>You might have to serch for id=q308466 to get to the article. It has sample
>code
>too.
>
>Sonia,
>
>You may like to look into this article too.
>
>Thanks,
>
>Indrasish.
>
>Scott Nichol wrote:
>
>> Indrasish,
>>
>> Do you recall more specifically? I grabbed the source for the article
>I
>> found on MSDN, but discovered that it uses the Favorites service, which
>is
>> rpc/encoded, not document/literal.
>>
>> Scott Nichol
>>
>> ----- Original Message -----
>> From: "Indrasish N Basuroychowdhury"
>> <in...@fanniemae.com>
>> To: <so...@xml.apache.org>
>> Sent: Wednesday, July 24, 2002 10:43 AM
>> Subject: Re: Problems with complexType again
>>
>> > Scott,
>> >
>> > It is similar. But one I picked up is from yahoogroups.
>> >
>> > Thanks,
>> >
>> > Indrasish.
>> >
>> > Scott Nichol wrote:
>> >
>> > > Indrasish,
>> > >
>> > > Thanks for the info on the Scott Sealy article. Is the one of which
>you
>> > > speak at
>> > >
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservice/h
>> > > tml/service08152001.asp?
>> > >
>> > > Scott Nichol
>> > >
>> > > ----- Original Message -----
>> > > From: "Indrasish N Basuroychowdhury"
>> > > <in...@fanniemae.com>
>> > > To: <so...@xml.apache.org>
>> > > Sent: Wednesday, July 24, 2002 9:55 AM
>> > > Subject: Re: Problems with complexType again
>> > >
>> > > > Sonia,
>> > > >
>> > > > .NET webservice by default uses literal/document type. Where as
Apache
>> > > uses
>> > > > encoded type (RPC). You have to change the .NET service to use
encoded
>> > > type. That
>> > > > can be done by adding [SoapRpcMethod] beside [WebMethod] while
>> building
>> > > .NET
>> > > > webservice. This is valid only if you own the webservice.
>> > > > If not you have two options:
>> > > > 1. Follow Scotts suggestion of switching to Axis.
>> > > > 2. Else, there is an example provided by Scott Sealy of Microsoft
>in
>> which
>> > > he
>> > > > shows how to send and receive documents using Apache. You have
to
>> build
>> > > Body,
>> > > > Header, ClientHandler and the proxy by yourself. Tedious, but works.
>> In
>> > > fact that
>> > > > is the only way I could send and receive Dataset.
>> > > >
>> > > > Thanks,
>> > > >
>> > > > Indrasish.
>> > > >
>> > > > s.vignaroli@tin.it wrote:
>> > > >
>> > > > > Hi, I'm here again...
>> > > > > Indrasish,
>> > > > > yesterday you told me that there is a solution, please tell me
>this
>> > > solution.
>> > > > > Yes, the webservice is written in .NET and client in Java, the
>> > > webservice
>> > > > > use MS.NET as SOAP implementation while i use Apache SOAP.
>> > > > > Thanks
>> > > > >
>> > > > > --
>> > > > > To unsubscribe, e-mail:
>> <ma...@xml.apache.org>
>> > > > > For additional commands, e-mail:
>> <ma...@xml.apache.org>
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > To unsubscribe, e-mail: <ma...@xml.apache.org>
>> > > > For additional commands, e-mail: <ma...@xml.apache.org>
>> > > >
>> > > >
>> > >
>> > > --
>> > > To unsubscribe, e-mail: <ma...@xml.apache.org>
>> > > For additional commands, e-mail: <ma...@xml.apache.org>
>> >
>> >
>> >
>> > --
>> > To unsubscribe, e-mail: <ma...@xml.apache.org>
>> > For additional commands, e-mail: <ma...@xml.apache.org>
>> >
>> >
>>
>> --
>> To unsubscribe, e-mail: <ma...@xml.apache.org>
>> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
>
>--
>To unsubscribe, e-mail: <ma...@xml.apache.org>
>For additional commands, e-mail: <ma...@xml.apache.org>
>
Re: Problems with complexType again
Posted by s....@tin.it.
Scott, Indrasish,
thanks for the articles, I'll read them then I'll try again following your
advices.
Bye, for now...
>-- Messaggio originale --
>Reply-To: soap-dev@xml.apache.org
>Date: Wed, 24 Jul 2002 11:08:53 -0400
>From: "Indrasish N Basuroychowdhury"
> <in...@fanniemae.com>
>To: soap-dev@xml.apache.org
>Subject: Re: Problems with complexType again
>
>
>Scott,
>
>Here we go.
>
>http://support.microsoft.com/directory/article.asp?id=q308466&sd=msdn
>
>You might have to serch for id=q308466 to get to the article. It has sample
>code
>too.
>
>Sonia,
>
>You may like to look into this article too.
>
>Thanks,
>
>Indrasish.
>
>Scott Nichol wrote:
>
>> Indrasish,
>>
>> Do you recall more specifically? I grabbed the source for the article
>I
>> found on MSDN, but discovered that it uses the Favorites service, which
>is
>> rpc/encoded, not document/literal.
>>
>> Scott Nichol
>>
>> ----- Original Message -----
>> From: "Indrasish N Basuroychowdhury"
>> <in...@fanniemae.com>
>> To: <so...@xml.apache.org>
>> Sent: Wednesday, July 24, 2002 10:43 AM
>> Subject: Re: Problems with complexType again
>>
>> > Scott,
>> >
>> > It is similar. But one I picked up is from yahoogroups.
>> >
>> > Thanks,
>> >
>> > Indrasish.
>> >
>> > Scott Nichol wrote:
>> >
>> > > Indrasish,
>> > >
>> > > Thanks for the info on the Scott Sealy article. Is the one of which
>you
>> > > speak at
>> > >
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservice/h
>> > > tml/service08152001.asp?
>> > >
>> > > Scott Nichol
>> > >
>> > > ----- Original Message -----
>> > > From: "Indrasish N Basuroychowdhury"
>> > > <in...@fanniemae.com>
>> > > To: <so...@xml.apache.org>
>> > > Sent: Wednesday, July 24, 2002 9:55 AM
>> > > Subject: Re: Problems with complexType again
>> > >
>> > > > Sonia,
>> > > >
>> > > > .NET webservice by default uses literal/document type. Where as
Apache
>> > > uses
>> > > > encoded type (RPC). You have to change the .NET service to use
encoded
>> > > type. That
>> > > > can be done by adding [SoapRpcMethod] beside [WebMethod] while
>> building
>> > > .NET
>> > > > webservice. This is valid only if you own the webservice.
>> > > > If not you have two options:
>> > > > 1. Follow Scotts suggestion of switching to Axis.
>> > > > 2. Else, there is an example provided by Scott Sealy of Microsoft
>in
>> which
>> > > he
>> > > > shows how to send and receive documents using Apache. You have
to
>> build
>> > > Body,
>> > > > Header, ClientHandler and the proxy by yourself. Tedious, but works.
>> In
>> > > fact that
>> > > > is the only way I could send and receive Dataset.
>> > > >
>> > > > Thanks,
>> > > >
>> > > > Indrasish.
>> > > >
>> > > > s.vignaroli@tin.it wrote:
>> > > >
>> > > > > Hi, I'm here again...
>> > > > > Indrasish,
>> > > > > yesterday you told me that there is a solution, please tell me
>this
>> > > solution.
>> > > > > Yes, the webservice is written in .NET and client in Java, the
>> > > webservice
>> > > > > use MS.NET as SOAP implementation while i use Apache SOAP.
>> > > > > Thanks
>> > > > >
>> > > > > --
>> > > > > To unsubscribe, e-mail:
>> <ma...@xml.apache.org>
>> > > > > For additional commands, e-mail:
>> <ma...@xml.apache.org>
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > To unsubscribe, e-mail: <ma...@xml.apache.org>
>> > > > For additional commands, e-mail: <ma...@xml.apache.org>
>> > > >
>> > > >
>> > >
>> > > --
>> > > To unsubscribe, e-mail: <ma...@xml.apache.org>
>> > > For additional commands, e-mail: <ma...@xml.apache.org>
>> >
>> >
>> >
>> > --
>> > To unsubscribe, e-mail: <ma...@xml.apache.org>
>> > For additional commands, e-mail: <ma...@xml.apache.org>
>> >
>> >
>>
>> --
>> To unsubscribe, e-mail: <ma...@xml.apache.org>
>> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
>
>--
>To unsubscribe, e-mail: <ma...@xml.apache.org>
>For additional commands, e-mail: <ma...@xml.apache.org>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Problems with complexType again
Posted by Indrasish N Basuroychowdhury <in...@fanniemae.com>.
Scott,
Here we go.
http://support.microsoft.com/directory/article.asp?id=q308466&sd=msdn
You might have to serch for id=q308466 to get to the article. It has sample code
too.
Sonia,
You may like to look into this article too.
Thanks,
Indrasish.
Scott Nichol wrote:
> Indrasish,
>
> Do you recall more specifically? I grabbed the source for the article I
> found on MSDN, but discovered that it uses the Favorites service, which is
> rpc/encoded, not document/literal.
>
> Scott Nichol
>
> ----- Original Message -----
> From: "Indrasish N Basuroychowdhury"
> <in...@fanniemae.com>
> To: <so...@xml.apache.org>
> Sent: Wednesday, July 24, 2002 10:43 AM
> Subject: Re: Problems with complexType again
>
> > Scott,
> >
> > It is similar. But one I picked up is from yahoogroups.
> >
> > Thanks,
> >
> > Indrasish.
> >
> > Scott Nichol wrote:
> >
> > > Indrasish,
> > >
> > > Thanks for the info on the Scott Sealy article. Is the one of which you
> > > speak at
> > >
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservice/h
> > > tml/service08152001.asp?
> > >
> > > Scott Nichol
> > >
> > > ----- Original Message -----
> > > From: "Indrasish N Basuroychowdhury"
> > > <in...@fanniemae.com>
> > > To: <so...@xml.apache.org>
> > > Sent: Wednesday, July 24, 2002 9:55 AM
> > > Subject: Re: Problems with complexType again
> > >
> > > > Sonia,
> > > >
> > > > .NET webservice by default uses literal/document type. Where as Apache
> > > uses
> > > > encoded type (RPC). You have to change the .NET service to use encoded
> > > type. That
> > > > can be done by adding [SoapRpcMethod] beside [WebMethod] while
> building
> > > .NET
> > > > webservice. This is valid only if you own the webservice.
> > > > If not you have two options:
> > > > 1. Follow Scotts suggestion of switching to Axis.
> > > > 2. Else, there is an example provided by Scott Sealy of Microsoft in
> which
> > > he
> > > > shows how to send and receive documents using Apache. You have to
> build
> > > Body,
> > > > Header, ClientHandler and the proxy by yourself. Tedious, but works.
> In
> > > fact that
> > > > is the only way I could send and receive Dataset.
> > > >
> > > > Thanks,
> > > >
> > > > Indrasish.
> > > >
> > > > s.vignaroli@tin.it wrote:
> > > >
> > > > > Hi, I'm here again...
> > > > > Indrasish,
> > > > > yesterday you told me that there is a solution, please tell me this
> > > solution.
> > > > > Yes, the webservice is written in .NET and client in Java, the
> > > webservice
> > > > > use MS.NET as SOAP implementation while i use Apache SOAP.
> > > > > Thanks
> > > > >
> > > > > --
> > > > > To unsubscribe, e-mail:
> <ma...@xml.apache.org>
> > > > > For additional commands, e-mail:
> <ma...@xml.apache.org>
> > > >
> > > >
> > > >
> > > > --
> > > > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > > > For additional commands, e-mail: <ma...@xml.apache.org>
> > > >
> > > >
> > >
> > > --
> > > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > > For additional commands, e-mail: <ma...@xml.apache.org>
> >
> >
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
> >
> >
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
Re: Problems with complexType again
Posted by Indrasish N Basuroychowdhury <in...@fanniemae.com>.
Scott,
Here we go.
http://support.microsoft.com/directory/article.asp?id=q308466&sd=msdn
You might have to serch for id=q308466 to get to the article. It has sample code
too.
Sonia,
You may like to look into this article too.
Thanks,
Indrasish.
Scott Nichol wrote:
> Indrasish,
>
> Do you recall more specifically? I grabbed the source for the article I
> found on MSDN, but discovered that it uses the Favorites service, which is
> rpc/encoded, not document/literal.
>
> Scott Nichol
>
> ----- Original Message -----
> From: "Indrasish N Basuroychowdhury"
> <in...@fanniemae.com>
> To: <so...@xml.apache.org>
> Sent: Wednesday, July 24, 2002 10:43 AM
> Subject: Re: Problems with complexType again
>
> > Scott,
> >
> > It is similar. But one I picked up is from yahoogroups.
> >
> > Thanks,
> >
> > Indrasish.
> >
> > Scott Nichol wrote:
> >
> > > Indrasish,
> > >
> > > Thanks for the info on the Scott Sealy article. Is the one of which you
> > > speak at
> > >
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservice/h
> > > tml/service08152001.asp?
> > >
> > > Scott Nichol
> > >
> > > ----- Original Message -----
> > > From: "Indrasish N Basuroychowdhury"
> > > <in...@fanniemae.com>
> > > To: <so...@xml.apache.org>
> > > Sent: Wednesday, July 24, 2002 9:55 AM
> > > Subject: Re: Problems with complexType again
> > >
> > > > Sonia,
> > > >
> > > > .NET webservice by default uses literal/document type. Where as Apache
> > > uses
> > > > encoded type (RPC). You have to change the .NET service to use encoded
> > > type. That
> > > > can be done by adding [SoapRpcMethod] beside [WebMethod] while
> building
> > > .NET
> > > > webservice. This is valid only if you own the webservice.
> > > > If not you have two options:
> > > > 1. Follow Scotts suggestion of switching to Axis.
> > > > 2. Else, there is an example provided by Scott Sealy of Microsoft in
> which
> > > he
> > > > shows how to send and receive documents using Apache. You have to
> build
> > > Body,
> > > > Header, ClientHandler and the proxy by yourself. Tedious, but works.
> In
> > > fact that
> > > > is the only way I could send and receive Dataset.
> > > >
> > > > Thanks,
> > > >
> > > > Indrasish.
> > > >
> > > > s.vignaroli@tin.it wrote:
> > > >
> > > > > Hi, I'm here again...
> > > > > Indrasish,
> > > > > yesterday you told me that there is a solution, please tell me this
> > > solution.
> > > > > Yes, the webservice is written in .NET and client in Java, the
> > > webservice
> > > > > use MS.NET as SOAP implementation while i use Apache SOAP.
> > > > > Thanks
> > > > >
> > > > > --
> > > > > To unsubscribe, e-mail:
> <ma...@xml.apache.org>
> > > > > For additional commands, e-mail:
> <ma...@xml.apache.org>
> > > >
> > > >
> > > >
> > > > --
> > > > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > > > For additional commands, e-mail: <ma...@xml.apache.org>
> > > >
> > > >
> > >
> > > --
> > > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > > For additional commands, e-mail: <ma...@xml.apache.org>
> >
> >
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
> >
> >
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Problems with complexType again
Posted by Scott Nichol <sn...@scottnichol.com>.
Indrasish,
Do you recall more specifically? I grabbed the source for the article I
found on MSDN, but discovered that it uses the Favorites service, which is
rpc/encoded, not document/literal.
Scott Nichol
----- Original Message -----
From: "Indrasish N Basuroychowdhury"
<in...@fanniemae.com>
To: <so...@xml.apache.org>
Sent: Wednesday, July 24, 2002 10:43 AM
Subject: Re: Problems with complexType again
> Scott,
>
> It is similar. But one I picked up is from yahoogroups.
>
> Thanks,
>
> Indrasish.
>
> Scott Nichol wrote:
>
> > Indrasish,
> >
> > Thanks for the info on the Scott Sealy article. Is the one of which you
> > speak at
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservice/h
> > tml/service08152001.asp?
> >
> > Scott Nichol
> >
> > ----- Original Message -----
> > From: "Indrasish N Basuroychowdhury"
> > <in...@fanniemae.com>
> > To: <so...@xml.apache.org>
> > Sent: Wednesday, July 24, 2002 9:55 AM
> > Subject: Re: Problems with complexType again
> >
> > > Sonia,
> > >
> > > .NET webservice by default uses literal/document type. Where as Apache
> > uses
> > > encoded type (RPC). You have to change the .NET service to use encoded
> > type. That
> > > can be done by adding [SoapRpcMethod] beside [WebMethod] while
building
> > .NET
> > > webservice. This is valid only if you own the webservice.
> > > If not you have two options:
> > > 1. Follow Scotts suggestion of switching to Axis.
> > > 2. Else, there is an example provided by Scott Sealy of Microsoft in
which
> > he
> > > shows how to send and receive documents using Apache. You have to
build
> > Body,
> > > Header, ClientHandler and the proxy by yourself. Tedious, but works.
In
> > fact that
> > > is the only way I could send and receive Dataset.
> > >
> > > Thanks,
> > >
> > > Indrasish.
> > >
> > > s.vignaroli@tin.it wrote:
> > >
> > > > Hi, I'm here again...
> > > > Indrasish,
> > > > yesterday you told me that there is a solution, please tell me this
> > solution.
> > > > Yes, the webservice is written in .NET and client in Java, the
> > webservice
> > > > use MS.NET as SOAP implementation while i use Apache SOAP.
> > > > Thanks
> > > >
> > > > --
> > > > To unsubscribe, e-mail:
<ma...@xml.apache.org>
> > > > For additional commands, e-mail:
<ma...@xml.apache.org>
> > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > > For additional commands, e-mail: <ma...@xml.apache.org>
> > >
> > >
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Re: Problems with complexType again
Posted by Scott Nichol <sn...@scottnichol.com>.
Indrasish,
Do you recall more specifically? I grabbed the source for the article I
found on MSDN, but discovered that it uses the Favorites service, which is
rpc/encoded, not document/literal.
Scott Nichol
----- Original Message -----
From: "Indrasish N Basuroychowdhury"
<in...@fanniemae.com>
To: <so...@xml.apache.org>
Sent: Wednesday, July 24, 2002 10:43 AM
Subject: Re: Problems with complexType again
> Scott,
>
> It is similar. But one I picked up is from yahoogroups.
>
> Thanks,
>
> Indrasish.
>
> Scott Nichol wrote:
>
> > Indrasish,
> >
> > Thanks for the info on the Scott Sealy article. Is the one of which you
> > speak at
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservice/h
> > tml/service08152001.asp?
> >
> > Scott Nichol
> >
> > ----- Original Message -----
> > From: "Indrasish N Basuroychowdhury"
> > <in...@fanniemae.com>
> > To: <so...@xml.apache.org>
> > Sent: Wednesday, July 24, 2002 9:55 AM
> > Subject: Re: Problems with complexType again
> >
> > > Sonia,
> > >
> > > .NET webservice by default uses literal/document type. Where as Apache
> > uses
> > > encoded type (RPC). You have to change the .NET service to use encoded
> > type. That
> > > can be done by adding [SoapRpcMethod] beside [WebMethod] while
building
> > .NET
> > > webservice. This is valid only if you own the webservice.
> > > If not you have two options:
> > > 1. Follow Scotts suggestion of switching to Axis.
> > > 2. Else, there is an example provided by Scott Sealy of Microsoft in
which
> > he
> > > shows how to send and receive documents using Apache. You have to
build
> > Body,
> > > Header, ClientHandler and the proxy by yourself. Tedious, but works.
In
> > fact that
> > > is the only way I could send and receive Dataset.
> > >
> > > Thanks,
> > >
> > > Indrasish.
> > >
> > > s.vignaroli@tin.it wrote:
> > >
> > > > Hi, I'm here again...
> > > > Indrasish,
> > > > yesterday you told me that there is a solution, please tell me this
> > solution.
> > > > Yes, the webservice is written in .NET and client in Java, the
> > webservice
> > > > use MS.NET as SOAP implementation while i use Apache SOAP.
> > > > Thanks
> > > >
> > > > --
> > > > To unsubscribe, e-mail:
<ma...@xml.apache.org>
> > > > For additional commands, e-mail:
<ma...@xml.apache.org>
> > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > > For additional commands, e-mail: <ma...@xml.apache.org>
> > >
> > >
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Problems with complexType again
Posted by Indrasish N Basuroychowdhury <in...@fanniemae.com>.
Scott,
It is similar. But one I picked up is from yahoogroups.
Thanks,
Indrasish.
Scott Nichol wrote:
> Indrasish,
>
> Thanks for the info on the Scott Sealy article. Is the one of which you
> speak at
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservice/h
> tml/service08152001.asp?
>
> Scott Nichol
>
> ----- Original Message -----
> From: "Indrasish N Basuroychowdhury"
> <in...@fanniemae.com>
> To: <so...@xml.apache.org>
> Sent: Wednesday, July 24, 2002 9:55 AM
> Subject: Re: Problems with complexType again
>
> > Sonia,
> >
> > .NET webservice by default uses literal/document type. Where as Apache
> uses
> > encoded type (RPC). You have to change the .NET service to use encoded
> type. That
> > can be done by adding [SoapRpcMethod] beside [WebMethod] while building
> .NET
> > webservice. This is valid only if you own the webservice.
> > If not you have two options:
> > 1. Follow Scotts suggestion of switching to Axis.
> > 2. Else, there is an example provided by Scott Sealy of Microsoft in which
> he
> > shows how to send and receive documents using Apache. You have to build
> Body,
> > Header, ClientHandler and the proxy by yourself. Tedious, but works. In
> fact that
> > is the only way I could send and receive Dataset.
> >
> > Thanks,
> >
> > Indrasish.
> >
> > s.vignaroli@tin.it wrote:
> >
> > > Hi, I'm here again...
> > > Indrasish,
> > > yesterday you told me that there is a solution, please tell me this
> solution.
> > > Yes, the webservice is written in .NET and client in Java, the
> webservice
> > > use MS.NET as SOAP implementation while i use Apache SOAP.
> > > Thanks
> > >
> > > --
> > > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > > For additional commands, e-mail: <ma...@xml.apache.org>
> >
> >
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
> >
> >
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Problems with complexType again
Posted by Indrasish N Basuroychowdhury <in...@fanniemae.com>.
Scott,
It is similar. But one I picked up is from yahoogroups.
Thanks,
Indrasish.
Scott Nichol wrote:
> Indrasish,
>
> Thanks for the info on the Scott Sealy article. Is the one of which you
> speak at
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservice/h
> tml/service08152001.asp?
>
> Scott Nichol
>
> ----- Original Message -----
> From: "Indrasish N Basuroychowdhury"
> <in...@fanniemae.com>
> To: <so...@xml.apache.org>
> Sent: Wednesday, July 24, 2002 9:55 AM
> Subject: Re: Problems with complexType again
>
> > Sonia,
> >
> > .NET webservice by default uses literal/document type. Where as Apache
> uses
> > encoded type (RPC). You have to change the .NET service to use encoded
> type. That
> > can be done by adding [SoapRpcMethod] beside [WebMethod] while building
> .NET
> > webservice. This is valid only if you own the webservice.
> > If not you have two options:
> > 1. Follow Scotts suggestion of switching to Axis.
> > 2. Else, there is an example provided by Scott Sealy of Microsoft in which
> he
> > shows how to send and receive documents using Apache. You have to build
> Body,
> > Header, ClientHandler and the proxy by yourself. Tedious, but works. In
> fact that
> > is the only way I could send and receive Dataset.
> >
> > Thanks,
> >
> > Indrasish.
> >
> > s.vignaroli@tin.it wrote:
> >
> > > Hi, I'm here again...
> > > Indrasish,
> > > yesterday you told me that there is a solution, please tell me this
> solution.
> > > Yes, the webservice is written in .NET and client in Java, the
> webservice
> > > use MS.NET as SOAP implementation while i use Apache SOAP.
> > > Thanks
> > >
> > > --
> > > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > > For additional commands, e-mail: <ma...@xml.apache.org>
> >
> >
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
> >
> >
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
Re: Problems with complexType again
Posted by Scott Nichol <sn...@scottnichol.com>.
Indrasish,
Thanks for the info on the Scott Sealy article. Is the one of which you
speak at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservice/h
tml/service08152001.asp?
Scott Nichol
----- Original Message -----
From: "Indrasish N Basuroychowdhury"
<in...@fanniemae.com>
To: <so...@xml.apache.org>
Sent: Wednesday, July 24, 2002 9:55 AM
Subject: Re: Problems with complexType again
> Sonia,
>
> .NET webservice by default uses literal/document type. Where as Apache
uses
> encoded type (RPC). You have to change the .NET service to use encoded
type. That
> can be done by adding [SoapRpcMethod] beside [WebMethod] while building
.NET
> webservice. This is valid only if you own the webservice.
> If not you have two options:
> 1. Follow Scotts suggestion of switching to Axis.
> 2. Else, there is an example provided by Scott Sealy of Microsoft in which
he
> shows how to send and receive documents using Apache. You have to build
Body,
> Header, ClientHandler and the proxy by yourself. Tedious, but works. In
fact that
> is the only way I could send and receive Dataset.
>
> Thanks,
>
> Indrasish.
>
> s.vignaroli@tin.it wrote:
>
> > Hi, I'm here again...
> > Indrasish,
> > yesterday you told me that there is a solution, please tell me this
solution.
> > Yes, the webservice is written in .NET and client in Java, the
webservice
> > use MS.NET as SOAP implementation while i use Apache SOAP.
> > Thanks
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Re: Problems with complexType again
Posted by Scott Nichol <sn...@scottnichol.com>.
Indrasish,
Thanks for the info on the Scott Sealy article. Is the one of which you
speak at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservice/h
tml/service08152001.asp?
Scott Nichol
----- Original Message -----
From: "Indrasish N Basuroychowdhury"
<in...@fanniemae.com>
To: <so...@xml.apache.org>
Sent: Wednesday, July 24, 2002 9:55 AM
Subject: Re: Problems with complexType again
> Sonia,
>
> .NET webservice by default uses literal/document type. Where as Apache
uses
> encoded type (RPC). You have to change the .NET service to use encoded
type. That
> can be done by adding [SoapRpcMethod] beside [WebMethod] while building
.NET
> webservice. This is valid only if you own the webservice.
> If not you have two options:
> 1. Follow Scotts suggestion of switching to Axis.
> 2. Else, there is an example provided by Scott Sealy of Microsoft in which
he
> shows how to send and receive documents using Apache. You have to build
Body,
> Header, ClientHandler and the proxy by yourself. Tedious, but works. In
fact that
> is the only way I could send and receive Dataset.
>
> Thanks,
>
> Indrasish.
>
> s.vignaroli@tin.it wrote:
>
> > Hi, I'm here again...
> > Indrasish,
> > yesterday you told me that there is a solution, please tell me this
solution.
> > Yes, the webservice is written in .NET and client in Java, the
webservice
> > use MS.NET as SOAP implementation while i use Apache SOAP.
> > Thanks
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Problems with complexType again
Posted by Indrasish N Basuroychowdhury <in...@fanniemae.com>.
Sonia,
.NET webservice by default uses literal/document type. Where as Apache uses
encoded type (RPC). You have to change the .NET service to use encoded type. That
can be done by adding [SoapRpcMethod] beside [WebMethod] while building .NET
webservice. This is valid only if you own the webservice.
If not you have two options:
1. Follow Scotts suggestion of switching to Axis.
2. Else, there is an example provided by Scott Sealy of Microsoft in which he
shows how to send and receive documents using Apache. You have to build Body,
Header, ClientHandler and the proxy by yourself. Tedious, but works. In fact that
is the only way I could send and receive Dataset.
Thanks,
Indrasish.
s.vignaroli@tin.it wrote:
> Hi, I'm here again...
> Indrasish,
> yesterday you told me that there is a solution, please tell me this solution.
> Yes, the webservice is written in .NET and client in Java, the webservice
> use MS.NET as SOAP implementation while i use Apache SOAP.
> Thanks
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Problems with complexType again
Posted by Indrasish N Basuroychowdhury <in...@fanniemae.com>.
Sonia,
.NET webservice by default uses literal/document type. Where as Apache uses
encoded type (RPC). You have to change the .NET service to use encoded type. That
can be done by adding [SoapRpcMethod] beside [WebMethod] while building .NET
webservice. This is valid only if you own the webservice.
If not you have two options:
1. Follow Scotts suggestion of switching to Axis.
2. Else, there is an example provided by Scott Sealy of Microsoft in which he
shows how to send and receive documents using Apache. You have to build Body,
Header, ClientHandler and the proxy by yourself. Tedious, but works. In fact that
is the only way I could send and receive Dataset.
Thanks,
Indrasish.
s.vignaroli@tin.it wrote:
> Hi, I'm here again...
> Indrasish,
> yesterday you told me that there is a solution, please tell me this solution.
> Yes, the webservice is written in .NET and client in Java, the webservice
> use MS.NET as SOAP implementation while i use Apache SOAP.
> Thanks
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>