This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 191736 - [70cat] WSDL rejected without warning
Summary: [70cat] WSDL rejected without warning
Status: RESOLVED INVALID
Alias: None
Product: webservices
Classification: Unclassified
Component: Code (show other bugs)
Version: 7.0
Hardware: PC Linux
: P3 normal (vote)
Assignee: Denis Anisimov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-08 16:25 UTC by gholmer
Modified: 2010-11-10 14:09 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
stack trace (15.00 KB, text/plain)
2010-11-08 18:36 UTC, gholmer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description gholmer 2010-11-08 16:25:09 UTC
[ JDK VERSION : 1.6.22 ]

I am trying to create a web service client from a WSDL whose location
is secured with SSL. Under 6.9.1, I get this message:

"Unable to verify the identity of ... as a trusted site."
"Accept this certificate?" (with Yes/No buttons)

but with 201011070000, it just fails, saying "Problem with downloading
wsdl or schema file", and there's a trace in the log (see attachment).

Steps to reproduce:
1) Right-click project node, select New, Web Service Client.
2) Specify the WSDL by URL, e.g. https://api.bronto.com/v4?wsdl
3) Leave package name blank, click Finish.
Comment 1 gholmer 2010-11-08 18:36:32 UTC
Created attachment 102849 [details]
stack trace
Comment 2 Denis Anisimov 2010-11-10 11:35:28 UTC
I'm not able to reproduce this issue with pointed https URL.
The wsdl is successfully downloaded and all classes are generated for me.
May be there was a real temporary problem with remote server...

Could you please recheck this issue ?
Related WS client source code is not changed since 6.9.1.
So the problem could be in the retriever module source code if it really exist.
Comment 3 gholmer 2010-11-10 14:09:59 UTC
I think you are right. Later in the day we had network problems, I believe this was related. Setting to INVALID.