Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / June 2004

Tip: Looking for answers? Try searching our database.

cannot generate a proxy for the .ashx file in the customXmlSecToken sample.

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Jagdeep - 18 Jun 2004 06:17 GMT
Hi

I am getting a error trying to generate a proxy for a virtual file that is
in the customXmlSecToken sample (installs with the WSE 2.0 setting tool).
The error is
"The WSDL doccument contains links that could not be resolved.
   - There was an error downloading
http:\\schemas.xmlsoap.org/ws/2004/04/trust
   - The underlying connection was closed.
The remote reference could not be resolved.

Any help is appreciated.

Regards

Jagdeep
Lucien - 19 Jun 2004 01:12 GMT
Do you have access to http:\\schemas.xmlsoap.org/ws/2004/04/trust (I was
able to access it fine)?
I added a web reference to
http://localhost/CustomXmlSecTokenCodeService/CustomXmlSecTokenCodeService.asmx
and had no errors (also WseWsdl2 worked for me).

> Hi
>
[quoted text clipped - 12 lines]
>
> Jagdeep
Jag - 20 Jun 2004 12:53 GMT
Hi lucien

I was trying to create a proxy to the virtual file
http://localhost/CustomXmlSecTokenCodeTokenIssuer/requestXmlServer.ashx
and this results in the error as stated earlier. I am to access
http:\\schemas.xmlsoap.org/ws/2004/04/trust.

Jagdeep

> Do you have access to http:\\schemas.xmlsoap.org/ws/2004/04/trust (I was
> able to access it fine)?
[quoted text clipped - 18 lines]
> >
> > Jagdeep
Softwaremaker - 20 Jun 2004 13:52 GMT
Hi Jag,

There is no
http://localhost/CustomXmlSecTokenCodeTokenIssuer/requestXmlServer.ashx file
and thats why you cannot create a proxy to this virtual file.

Like what Lucien said, you have to create a proxy to this physical file
http://localhost/CustomXmlSecTokenCodeService/CustomXmlSecTokenCodeService.asmx
and then from the proxy created, change the Me.URL setting (if you are on
VB.NET) to the
http://localhost/CustomXmlSecTokenCodeTokenIssuer/requestXmlServer.ashx
endpoint.

hth

Signature

Thank you very much

Warmest Regards,
Softwaremaker
Architect | Evangelist | Consultant

Microsoft Regional Director
http://www.microsoft.com/rd

+++++++++++++++++++++++++++++++++

> Hi lucien
>
[quoted text clipped - 8 lines]
> > able to access it fine)?
> > I added a web reference to

http://localhost/CustomXmlSecTokenCodeService/CustomXmlSecTokenCodeService.asmx
> > and had no errors (also WseWsdl2 worked for me).
> >
[quoted text clipped - 14 lines]
> > >
> > > Jagdeep

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.