By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,612 Members | 1,632 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,612 IT Pros & Developers. It's quick & easy.

Problem add Web Reference for CSTA WSDL

P: n/a
Hi,

I am trying to create a Web Reference for CSTA using the URL
http://www.ecma-international.org/st...perations.wsdl

Visual .Net complains that:
"
The document was understood, but it could not be processed.
- The WSDL document contains links that could not be resolved.
- There was an error downloading
'http://www.ecma-international.org/standards/ecma-348/csta-wsdl/csta.xsd'.
- The request failed with HTTP status 404: Not Found.
"
In the WSDL, csta.xds in at http://www.ecma.ch/standards/ecma-323/csta/ed2
and it surely exists.

What have I done wrong?

Thank you very much,
Nov 12 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
"trexim" <tr****@hotmail.com> wrote in message news:2r*************@uni-berlin.de...
- There was an error downloading
'http://www.ecma-international.org/standards/ecma-348/csta-wsdl/csta.xsd'.
- The request failed with HTTP status 404: Not Found.
"
In the WSDL, csta.xds in at http://www.ecma.ch/standards/ecma-323/csta/ed2
and it surely exists.

What have I done wrong?


If you look closely, Visual Studio .NET is complaining that a file in
the "ecma-348" folder could not be found. Meanwhile, you say
the file exists in the "ecma-323" folder. I think you have a typo
in the WSDL where it says "ecma-348" when it meant to state
"ecma-323".
Derek Harmon
Nov 12 '05 #2

P: n/a

"Derek Harmon" <lo*******@msn.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...
"trexim" <tr****@hotmail.com> wrote in message

news:2r*************@uni-berlin.de...
- There was an error downloading
'http://www.ecma-international.org/standards/ecma-348/csta-wsdl/csta.xsd'. - The request failed with HTTP status 404: Not Found.
"
In the WSDL, csta.xds in at http://www.ecma.ch/standards/ecma-323/csta/ed2 and it surely exists.

What have I done wrong?


If you look closely, Visual Studio .NET is complaining that a file in
the "ecma-348" folder could not be found. Meanwhile, you say
the file exists in the "ecma-323" folder. I think you have a typo
in the WSDL where it says "ecma-348" when it meant to state
"ecma-323".
Derek Harmon


Sorry,

I should have been clearer in the question:

In the wsdl file, the type is imported:

<xs:schema
targetNamespace="http://www.ecma-international.org/standards/ecma-348/csta-w
sdl">
<xs:import namespace="http://www.ecma.ch/standards/ecma-323/csta/ed2"
schemaLocation="csta.xsd" />
</xs:schema>

It seems that Visual Studio .NET insists on looking for "csta.xsd" in
"http://www.ecma-international.org/standards/ecma-348/csta-wsdl" (does not
exist), but the wsdl has specified the correct place which is
"http://www.ecma.ch/standards/ecma-323/csta/ed2"

Is that a VS .NET resticrion or just a mistake in CSTA WSDL, or they are
just not compatible?

Thanks,
Nov 12 '05 #3

P: n/a
Trexim,

The problem is that the schemaLocation reference to csta.xsd is
relative, therefore wsdl.exe (and Visual Studio) append the path
location of the referencing wsdl document -- which I would assume to be
the default behavior.

Unfortunately, you can't provide a "search path" for included documents,
so your best bet is to download the wsdl and all references schemas, put
them into a single folder on your disk and run wsdl.exe (or the Add Web
Reference wizard).

HTH,
Christoph Schittko
MVP XML
-----Original Message-----
From: trexim [mailto:tr****@hotmail.com]
Posted At: Monday, September 20, 2004 9:10 AM
Posted To: microsoft.public.dotnet.xml
Conversation: Problem add Web Reference for CSTA WSDL
Subject: Re: Problem add Web Reference for CSTA WSDL
"Derek Harmon" <lo*******@msn.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...
"trexim" <tr****@hotmail.com> wrote in message news:2r*************@uni-berlin.de...
- There was an error downloading

'http://www.ecma-international.org/standards/ecma-348/csta-wsdl/csta.xsd
'.
- The request failed with HTTP status 404: Not Found.
"
In the WSDL, csta.xds in at http://www.ecma.ch/standards/ecma-323/csta/ed2 and it surely exists.

What have I done wrong?


If you look closely, Visual Studio .NET is complaining that a file in the "ecma-348" folder could not be found. Meanwhile, you say
the file exists in the "ecma-323" folder. I think you have a typo
in the WSDL where it says "ecma-348" when it meant to state
"ecma-323".
Derek Harmon


Sorry,

I should have been clearer in the question:

In the wsdl file, the type is imported:

<xs:schema
targetNamespace="http://www.ecma-international.org/standards/ecma-
348/csta-w
sdl">
<xs:import

namespace="http://www.ecma.ch/standards/ecma-323/csta/ed2" schemaLocation="csta.xsd" />
</xs:schema>

It seems that Visual Studio .NET insists on looking for "csta.xsd" in
"http://www.ecma-international.org/standards/ecma-348/csta-wsdl" (does not exist), but the wsdl has specified the correct place which is
"http://www.ecma.ch/standards/ecma-323/csta/ed2"

Is that a VS .NET resticrion or just a mistake in CSTA WSDL, or they are just not compatible?

Thanks,

Nov 12 '05 #4

P: n/a
Thank you for your reply.

I tried that too (quite tedious, with the downloading of 229 .xsd files). I
no longer get the error message while using the "Add Web Reference" wizard,
but VS .Net couldn't generate any codes and complains that:
"
Custom tool warning: DiscoCodeGenerator unable to initialize code generator.
No code generated.
Custom tool warning: Ignore duplicate schema document
'file:///C:/csta_wsdl_docs/accept-call.xsd' with TargetNamespace
'http://www.ecma.ch/standards/ecma-323/csta/ed2'.
"

Obviously this could be a brand new type of error.

I am just surpised that searching the Web and news-group for similar
problem, I couldn't find any entry. As if nobody ever tried this csta.wsdl
with Visual Studio .NET. ECMA does not have (it seems) a developer forum or
anything like that. Microsoft is using some CSTA standard (for voice
application in particular) and appears to be moving away from TAPI.
Hopefully, I am still posting something in topic here.

Any reply/advice/pointer are greatly appreciated.

Thank you very much,
"Christoph Schittko [MVP]" <IN**********@austin.rr.com> wrote in message
news:Ow*************@TK2MSFTNGP10.phx.gbl...
Trexim,

The problem is that the schemaLocation reference to csta.xsd is
relative, therefore wsdl.exe (and Visual Studio) append the path
location of the referencing wsdl document -- which I would assume to be
the default behavior.

Unfortunately, you can't provide a "search path" for included documents,
so your best bet is to download the wsdl and all references schemas, put
them into a single folder on your disk and run wsdl.exe (or the Add Web
Reference wizard).

HTH,
Christoph Schittko
MVP XML
-----Original Message-----
From: trexim [mailto:tr****@hotmail.com]
Posted At: Monday, September 20, 2004 9:10 AM
Posted To: microsoft.public.dotnet.xml
Conversation: Problem add Web Reference for CSTA WSDL
Subject: Re: Problem add Web Reference for CSTA WSDL
"Derek Harmon" <lo*******@msn.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...
"trexim" <tr****@hotmail.com> wrote in message

news:2r*************@uni-berlin.de...
> - There was an error downloading
>

'http://www.ecma-international.org/standards/ecma-348/csta-wsdl/csta.xsd
'.
> - The request failed with HTTP status 404: Not Found.
> "
> In the WSDL, csta.xds in at

http://www.ecma.ch/standards/ecma-323/csta/ed2
> and it surely exists.
>
> What have I done wrong?

If you look closely, Visual Studio .NET is complaining that a file in the "ecma-348" folder could not be found. Meanwhile, you say
the file exists in the "ecma-323" folder. I think you have a typo
in the WSDL where it says "ecma-348" when it meant to state
"ecma-323".
Derek Harmon


Sorry,

I should have been clearer in the question:

In the wsdl file, the type is imported:

<xs:schema
targetNamespace="http://www.ecma-international.org/standards/ecma-
348/csta-w
sdl">
<xs:import

namespace="http://www.ecma.ch/standards/ecma-323/csta/ed2"
schemaLocation="csta.xsd" />
</xs:schema>

It seems that Visual Studio .NET insists on looking for "csta.xsd" in
"http://www.ecma-international.org/standards/ecma-348/csta-wsdl" (does

not
exist), but the wsdl has specified the correct place which is
"http://www.ecma.ch/standards/ecma-323/csta/ed2"

Is that a VS .NET resticrion or just a mistake in CSTA WSDL, or they

are
just not compatible?

Thanks,


Nov 12 '05 #5

P: n/a
The new error sounds like it's legitimate. Any chance another file
besides 'file:///C:/csta_wsdl_docs/accept-call.xsd' defines the
namespace 'http://www.ecma.ch/standards/ecma-323/csta/ed2' where if
should reference it via an import or an include?

HTH,
Christoph Schittko
MVP XML .NET
-----Original Message-----
From: trexim [mailto:tr****@hotmail.com]
Posted At: Monday, September 20, 2004 3:37 PM
Posted To: microsoft.public.dotnet.xml
Conversation: Problem add Web Reference for CSTA WSDL
Subject: Re: Problem add Web Reference for CSTA WSDL

Thank you for your reply.

I tried that too (quite tedious, with the downloading of 229 .xsd files). I
no longer get the error message while using the "Add Web Reference"
wizard,
but VS .Net couldn't generate any codes and complains that:
"
Custom tool warning: DiscoCodeGenerator unable to initialize code
generator.
No code generated.
Custom tool warning: Ignore duplicate schema document
'file:///C:/csta_wsdl_docs/accept-call.xsd' with TargetNamespace
'http://www.ecma.ch/standards/ecma-323/csta/ed2'.
"

Obviously this could be a brand new type of error.

I am just surpised that searching the Web and news-group for similar
problem, I couldn't find any entry. As if nobody ever tried this csta.wsdl with Visual Studio .NET. ECMA does not have (it seems) a developer forum or
anything like that. Microsoft is using some CSTA standard (for voice
application in particular) and appears to be moving away from TAPI.
Hopefully, I am still posting something in topic here.

Any reply/advice/pointer are greatly appreciated.

Thank you very much,
"Christoph Schittko [MVP]" <IN**********@austin.rr.com> wrote in message news:Ow*************@TK2MSFTNGP10.phx.gbl...
Trexim,

The problem is that the schemaLocation reference to csta.xsd is
relative, therefore wsdl.exe (and Visual Studio) append the path
location of the referencing wsdl document -- which I would assume to be the default behavior.

Unfortunately, you can't provide a "search path" for included documents, so your best bet is to download the wsdl and all references schemas, put them into a single folder on your disk and run wsdl.exe (or the Add Web Reference wizard).

HTH,
Christoph Schittko
MVP XML
-----Original Message-----
From: trexim [mailto:tr****@hotmail.com]
Posted At: Monday, September 20, 2004 9:10 AM
Posted To: microsoft.public.dotnet.xml
Conversation: Problem add Web Reference for CSTA WSDL
Subject: Re: Problem add Web Reference for CSTA WSDL
"Derek Harmon" <lo*******@msn.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...
> "trexim" <tr****@hotmail.com> wrote in message
news:2r*************@uni-berlin.de...
> > - There was an error downloading
> >

'http://www.ecma-international.org/standards/ecma-348/csta-wsdl/csta.xsd '.
> > - The request failed with HTTP status 404: Not Found.
> > "
> > In the WSDL, csta.xds in at
http://www.ecma.ch/standards/ecma-323/csta/ed2
> > and it surely exists.
> >
> > What have I done wrong?
>
> If you look closely, Visual Studio .NET is complaining that a file
in
> the "ecma-348" folder could not be found. Meanwhile, you say
> the file exists in the "ecma-323" folder. I think you have a
typo > in the WSDL where it says "ecma-348" when it meant to state
> "ecma-323".
>
>
> Derek Harmon
>

Sorry,

I should have been clearer in the question:

In the wsdl file, the type is imported:

<xs:schema
targetNamespace="http://www.ecma-international.org/standards/ecma-
348/csta-w
sdl">
<xs:import

namespace="http://www.ecma.ch/standards/ecma-323/csta/ed2"
schemaLocation="csta.xsd" />
</xs:schema>

It seems that Visual Studio .NET insists on looking for "csta.xsd" in "http://www.ecma-international.org/standards/ecma-348/csta-wsdl"

(does not
exist), but the wsdl has specified the correct place which is
"http://www.ecma.ch/standards/ecma-323/csta/ed2"

Is that a VS .NET resticrion or just a mistake in CSTA WSDL, or
they are
just not compatible?

Thanks,


Nov 12 '05 #6

P: n/a
I have about 230 ".xsd" files, all of them start with:

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="http://www.ecma.ch/standards/ecma-323/csta/ed2"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:csta="http://www.ecma.ch/standards/ecma-323/csta/ed2"
elementFormDefault="qualified" attributeFormDefault="unqualified">
.........
.........
</xsd:schema>

Is that redefition?

The wsdl file has this:

<types>
<xs:schema
targetNamespace="http://www.ecma-international.org/standards/ecma-348/csta-w
sdl">
<xs:import namespace="http://www.ecma.ch/standards/ecma-323/csta/ed2"
schemaLocation="csta.xsd"/>
</xs:schema>
</types>
------------

For example, "accept-call.xsd" ia:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="http://www.ecma.ch/standards/ecma-323/csta/ed2"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:csta="http://www.ecma.ch/standards/ecma-323/csta/ed2"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<xsd:annotation>
<xsd:documentation>CSTA-accept-call</xsd:documentation>
</xsd:annotation>
<xsd:include schemaLocation="call-connection-identifiers.xsd"/>
<xsd:include schemaLocation="device-feature-types.xsd"/>
<xsd:include schemaLocation="extension-types.xsd"/>
<xsd:element name="AcceptCall">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="callToBeAccepted" type="csta:ConnectionID"/>
<xsd:element ref="csta:correlatorData" minOccurs="0"/>
<xsd:element ref="csta:userData" minOccurs="0"/>
<xsd:element ref="csta:extensions" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="AcceptCallResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="csta:extensions" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
---------------------------------------------------------------
While "agent-busy-event.xsd" is:

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="http://www.ecma.ch/standards/ecma-323/csta/ed2"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:csta="http://www.ecma.ch/standards/ecma-323/csta/ed2"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<xsd:annotation>
<xsd:documentation>CSTA-agent-busy-event</xsd:documentation>
</xsd:annotation>
<xsd:include schemaLocation="event-cause.xsd"/>
<xsd:include schemaLocation="device-identifiers.xsd"/>
<xsd:include schemaLocation="status-reporting.xsd"/>
<xsd:include schemaLocation="device-feature-types.xsd"/>
<xsd:include schemaLocation="extension-types.xsd"/>
<xsd:element name="AgentBusyEvent">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="csta:monitorCrossRefID"/>
<xsd:element name="agentDevice" type="csta:SubjectDeviceID"/>
<xsd:element name="agentID" type="csta:AgentID" minOccurs="0"/>
<xsd:element name="acdGroup" type="csta:DeviceID" minOccurs="0"/>
<xsd:element name="pendingAgentState" type="csta:PendingAgentState"
minOccurs="0"/>
<xsd:element ref="csta:cause" minOccurs="0"/>
<xsd:element ref="csta:extensions" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>

----------------------------------------------------------------------------
-

By the way, I have 320 error message like the below one for each file (not
only for accept-call.xsd):

- Custom tool warning: Ignore duplicate schema document
'file:///C:/csta_wsdl_docs/accept-call.xsd' with TargetNamespace
'http://www.ecma.ch/standards/ecma-323/csta/ed2'.
- Custom tool warning: Ignore duplicate schema document
'file:///C:/csta_wsdl_docs/agent-busy-event.xsd' with TargetNamespace
'http://www.ecma.ch/standards/ecma-323/csta/ed2'.
- Custom tool warning: Ignore duplicate schema document
'file:///C:/csta_wsdl_docs/agent-logged-off-event.xsd' with TargetNamespace
'http://www.ecma.ch/standards/ecma-323/csta/ed2'.

....... and so on .....

Thanks,


"Christoph Schittko [MVP]" <IN**********@austin.rr.com> wrote in message
news:OA**************@TK2MSFTNGP15.phx.gbl...
The new error sounds like it's legitimate. Any chance another file
besides 'file:///C:/csta_wsdl_docs/accept-call.xsd' defines the
namespace 'http://www.ecma.ch/standards/ecma-323/csta/ed2' where if
should reference it via an import or an include?

HTH,
Christoph Schittko
MVP XML .NET
-----Original Message-----
From: trexim [mailto:tr****@hotmail.com]
Posted At: Monday, September 20, 2004 3:37 PM
Posted To: microsoft.public.dotnet.xml
Conversation: Problem add Web Reference for CSTA WSDL
Subject: Re: Problem add Web Reference for CSTA WSDL

Thank you for your reply.

I tried that too (quite tedious, with the downloading of 229 .xsd

files).
I
no longer get the error message while using the "Add Web Reference"
wizard,
but VS .Net couldn't generate any codes and complains that:
"
Custom tool warning: DiscoCodeGenerator unable to initialize code
generator.
No code generated.
Custom tool warning: Ignore duplicate schema document
'file:///C:/csta_wsdl_docs/accept-call.xsd' with TargetNamespace
'http://www.ecma.ch/standards/ecma-323/csta/ed2'.
"

Obviously this could be a brand new type of error.

I am just surpised that searching the Web and news-group for similar
problem, I couldn't find any entry. As if nobody ever tried this

csta.wsdl
with Visual Studio .NET. ECMA does not have (it seems) a developer

forum
or
anything like that. Microsoft is using some CSTA standard (for voice
application in particular) and appears to be moving away from TAPI.
Hopefully, I am still posting something in topic here.

Any reply/advice/pointer are greatly appreciated.

Thank you very much,
"Christoph Schittko [MVP]" <IN**********@austin.rr.com> wrote in

message
news:Ow*************@TK2MSFTNGP10.phx.gbl...
Trexim,

The problem is that the schemaLocation reference to csta.xsd is
relative, therefore wsdl.exe (and Visual Studio) append the path
location of the referencing wsdl document -- which I would assume to be the default behavior.

Unfortunately, you can't provide a "search path" for included documents, so your best bet is to download the wsdl and all references schemas, put them into a single folder on your disk and run wsdl.exe (or the Add Web Reference wizard).

HTH,
Christoph Schittko
MVP XML

> -----Original Message-----
> From: trexim [mailto:tr****@hotmail.com]
> Posted At: Monday, September 20, 2004 9:10 AM
> Posted To: microsoft.public.dotnet.xml
> Conversation: Problem add Web Reference for CSTA WSDL
> Subject: Re: Problem add Web Reference for CSTA WSDL
>
>
> "Derek Harmon" <lo*******@msn.com> wrote in message
> news:%2****************@TK2MSFTNGP11.phx.gbl...
> > "trexim" <tr****@hotmail.com> wrote in message
> news:2r*************@uni-berlin.de...
> > > - There was an error downloading
> > >
>
'http://www.ecma-international.org/standards/ecma-348/csta-wsdl/csta.xsd '.
> > > - The request failed with HTTP status 404: Not Found.
> > > "
> > > In the WSDL, csta.xds in at
> http://www.ecma.ch/standards/ecma-323/csta/ed2
> > > and it surely exists.
> > >
> > > What have I done wrong?
> >
> > If you look closely, Visual Studio .NET is complaining that a file in
> > the "ecma-348" folder could not be found. Meanwhile, you say
> > the file exists in the "ecma-323" folder. I think you have a typo > > in the WSDL where it says "ecma-348" when it meant to state
> > "ecma-323".
> >
> >
> > Derek Harmon
> >
>
> Sorry,
>
> I should have been clearer in the question:
>
> In the wsdl file, the type is imported:
>
> <xs:schema
> targetNamespace="http://www.ecma-international.org/standards/ecma-
> 348/csta-w
> sdl">
> <xs:import
namespace="http://www.ecma.ch/standards/ecma-323/csta/ed2"
> schemaLocation="csta.xsd" />
> </xs:schema>
>
> It seems that Visual Studio .NET insists on looking for "csta.xsd" in > "http://www.ecma-international.org/standards/ecma-348/csta-wsdl" (does not
> exist), but the wsdl has specified the correct place which is
> "http://www.ecma.ch/standards/ecma-323/csta/ed2"
>
> Is that a VS .NET resticrion or just a mistake in CSTA WSDL, or they are
> just not compatible?
>
> Thanks,


Nov 12 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.