Delphi 2007 web service import wsdl wozard not working
correctly

I have created a simple web service server with a data module with
adoConnection componet & two adoDataSet components & a dataProvider
connected to the first adoDataSet (returning a select query )& written a
simple function to return the number of records in a table(MS SQL Server)
with the second dataset
I now created a simple client to access the data using soapConnection
component
While I am able to view the data in a dbgrid using CDS,I am not able to
import the wsdl file using
http://venks/bin/testWebService.dll/wsdl/IdataTest where IDataTest is the
name of the data module
I am able to view the web service in a browserwith the above URL
I keep on getting an access violation error(both in delphi 2007 & delphi
2006)
What  am I doing wrong here ?I thought it should be pretty simple to access
the web service server's functions
Venkatesh

Hello Venkatesh,

Are you getting the Access Violation when importing the WSDL? If yes, it
might be related to the problem reported recently in this report:


http://groups.google.com/group/borland.public.delphi.webservices.soap/msg/cd0099
614a7524a1?hl=en

I have an updated importer that remedies. Please let me know if you think
the issues are related. If yes, I'd be happy to make the updated importer
available. Otherwise, I need a little more information to investigate. Does
IDataTest expose any methods? If yes, how many.

Cheers,

Bruneau.

Hi Jean
Thanks for quick repsonse
Please send me the updated importer ( venks@vsnl.com )
I ma getting access viloation while using the existing importer.It had one
method.I did not try with more methods since one method itself is giving
troubule
It also gave an error when I tried it with out any method
Venkatesh
"Jean-Marie Babet" <bbabet@borland.com> wrote in message
news:4664669d$1@newsgroups.borland.com...
> Hello Venkatesh,
>
> Are you getting the Access Violation when importing the WSDL? If yes, it
> might be related to the problem reported recently in this report:
>
>
>
http://groups.google.com/group/borland.public.delphi.webservices.soap/msg/cd
0099614a7524a1?hl=en
>
> I have an updated importer that remedies. Please let me know if you think
> the issues are related. If yes, I'd be happy to make the updated importer
> available. Otherwise, I need a little more information to investigate.
Does
> IDataTest expose any methods? If yes, how many.
>
> Cheers,
>
> Bruneau.
>
>

Thanks for the follow-up post.

Initially the SOAP runtime wanted to support many calling conventions but it
quickly became clear that, well, the runtime is not a compiler. It's a
nightmare to keep track of the rules the compiler uses for each parameter
type [built-in types/classes/floating-point values/etc], modifier
[const/var/out/etc] and calling convention permutation[fastcall, cdecl,
stdcall, etc]. The fact that we fabricate the thunks at runtime based on
RTTI is rather unnatural, to say the least.

I believe there's a note in the runtime to find a way to report unsupported
calling conventions. The RTTI is consulted and vtable constructed when
someone QI's the RIO. I had tried to return  an error (i.e. throw an
exception) when the RTTI reveals problems but I found out that it was not
safe to throw an exception from QueryInterface. And simply returning
E_NOINTERFACE was really confusing.

I'll look at this again when time allows.

Cheers,

Bruneau.

"Bob Swart" <b.swart@chello.nl> wrote in message
news:4666B065.6040501@chello.nl...
> Hi Jean-Marie,
>
> > Are you getting the Access Violation when importing the WSDL?
>
> FWIW, the problem has been solved now (see a thread in the non-technical
> newsgroup), and was due to the fact that the "stdcall" calling
> convention was not specified for the custom SOAP method in the DataSnap
> SOAP data module.
>
> With "stdcall" applied, everything worked fine again (according
to
> Venkatesh himself).
>
> > Bruneau.
>
> Groetjes,
>            Bob Swart
>
> -- 
> Bob Swart Training & Consultancy (eBob42.com)  Forever Loyal to Delphi
> Blog: http://www.drbob42.com/blog - RSS: http://drbob42.com/weblog.xml
> Delphi 2006 Courseware PDF manuals at http://www.eBob42.com/courseware

Hi Jean-Marie,

> Are you getting the Access Violation when importing the WSDL? 

FWIW, the problem has been solved now (see a thread in the non-technical 
newsgroup), and was due to the fact that the "stdcall" calling 
convention was not specified for the custom SOAP method in the DataSnap 
SOAP data module.

With "stdcall" applied, everything worked fine again (according to 
Venkatesh himself).

> Bruneau.

Groetjes,
           Bob Swart

-- 
Bob Swart Training & Consultancy (eBob42.com)  Forever Loyal to Delphi
Blog: http://www.drbob42.com/blog - RSS: http://drbob42.com/weblog.xml