| Author |
Webservice reference problem .. plz help !
|
|
| Abhishek 2005-04-12, 2:49 am |
| Hi! ,
I am trying to invoke a Webservice method from my orchestration. The
method accepts Typed Dataset as a parameter. I am not able to Add
reference to this web service from my Biztalk project. It throws an
error while adding a web reference saying -
"Could not generte Biztalk files.
xyz.xyz.xyzRowChangedEventHandler cannot be serialized because it does
not have a default public constructor."
Can anybody help me out with this ?
Thanks
Abhishek Saraswat
| |
| Saravana Kumar 2005-04-12, 7:48 am |
| The error explains the problem correctly.
Before a web service is called Orchestration will initialize the web
service. In order to do that you need to have a default contructor.
On your web service. Create a default construtor .
Example:
public class Service1 : System.Web.Services.WebService
{
public Service1()
{
//CODEGEN: This call is required by the ASP.NET Web Services Designer
InitializeComponent();
}
--
Cheers
Saravana [MCP - Biztalk Server 2004]
http://saravanakumarmv.blogspot.com
"Abhishek" <abhisheksaraswat@gmail.com> wrote in message
news:cfc59162.0504112336.79499871@posting.google.com...
> Hi! ,
>
> I am trying to invoke a Webservice method from my orchestration. The
> method accepts Typed Dataset as a parameter. I am not able to Add
> reference to this web service from my Biztalk project. It throws an
> error while adding a web reference saying -
>
> "Could not generte Biztalk files.
> xyz.xyz.xyzRowChangedEventHandler cannot be serialized because it does
> not have a default public constructor."
>
> Can anybody help me out with this ?
>
> Thanks
> Abhishek Saraswat
| |
| Abhishek 2005-04-13, 2:50 am |
| Sarvana
The error is not about the Webservice construtor. If you read it
attentively you can see that error is about the an EventHandler which
is not a class but a delegate and since delegate cannot have any
default constructor the error gets raised while serializing it.
By the way just to share with you. I do have an alternate solution for
the problem, that is to pass an XMLDocument object as parammeter
rather than passing the Typed Dataset and this works fine with the
Biztalk. But I cannot change the parameter type of webservices and
using typed dataset does not works. I don't know whether they are
supported by Biztalk or not.
Has any body used typed dataset as Biztalk parameter before or have
faced problem like this ?
Thanks
Abhishek
"Saravana Kumar" <saravana@hotmail.co.uk> wrote in message news:<uO02ffzPFHA.604@TK2MSFTNGP10.phx.gbl>...[vbcol=seagreen]
> The error explains the problem correctly.
>
> Before a web service is called Orchestration will initialize the web
> service. In order to do that you need to have a default contructor.
>
> On your web service. Create a default construtor .
> Example:
>
> public class Service1 : System.Web.Services.WebService
>
> {
>
> public Service1()
>
> {
>
> //CODEGEN: This call is required by the ASP.NET Web Services Designer
>
> InitializeComponent();
>
> }
>
>
> --
> Cheers
> Saravana [MCP - Biztalk Server 2004]
> http://saravanakumarmv.blogspot.com
>
>
> "Abhishek" <abhisheksaraswat@gmail.com> wrote in message
> news:cfc59162.0504112336.79499871@posting.google.com...
| |
| Susmitha Kothari 2005-04-14, 5:53 pm |
| This is a known limitation in BTS 2004. Strongly typed datasets are not
supported (they try to import a schema).
Regards,
Susmitha Kothari
Microsoft BizTalk Server
This posting is provided "AS IS" with no warranties, and confers no rights.
| |
| Abhishek 2005-04-19, 2:47 am |
| Sushmita
Do you know of any workaround solution for this ?
Abhishek
skothari@online.microsoft.com (Susmitha Kothari) wrote in message news:<pVguL7RQFHA.16764@TK2MSFTNGXA01.phx.gbl>...
> This is a known limitation in BTS 2004. Strongly typed datasets are not
> supported (they try to import a schema).
>
> Regards,
> Susmitha Kothari
> Microsoft BizTalk Server
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
| |
| Susmitha Kothari 2005-05-27, 5:50 pm |
| You need to replace the import statement of the schema in the wsdl by
actually specifying the schema inline in the wsdl.
Regards,
Susmitha Kothari
Microsoft BizTalk Server
This posting is provided "AS IS" with no warranties, and confers no rights.
|
|
|
|