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 32093 - HTTP Javadoc filesystems not connecting
Summary: HTTP Javadoc filesystems not connecting
Status: RESOLVED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Javadoc (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords: RELNOTE
Depends on:
Blocks:
 
Reported: 2003-03-18 14:53 UTC by John Jullion-ceccarelli
Modified: 2004-08-13 12:11 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Jullion-ceccarelli 2003-03-18 14:53:46 UTC
On Win2K, jdk1.4.1

Go to Javadoc manager and mount any HTTP Javadoc
filesystem, like the default netbeans one. The
Javadoc manager gets stuck on (scanning...), never
completes scanning or throws error that it can't
complete scanning. Javadoc is not available.
Comment 1 Milan Kubec 2003-03-18 15:33:58 UTC
John, please adjust version ('curent' doesn't say much). Thanks

Dummy question: did you set your proxy properly?
Comment 2 John Jullion-ceccarelli 2003-03-18 15:54:44 UTC
Yup, the proxy's set. Sorry, wish it was that easy :-)
Comment 3 Milan Kubec 2003-03-18 15:57:08 UTC
It seems that it really doesn't work, increasing prio to P2. However,
I didn't get any error.
Comment 4 Milan Kubec 2003-03-28 12:28:30 UTC
This can be reproduced only when connecting through proxy and/or
firewall. Cannot be reproduced on "local" http server, even on huge
javadoc set (JDK 1.4 API javadoc).
Comment 5 Milan Kubec 2003-03-31 06:52:21 UTC
Lowering prio, since I tried direct connection through public internet
and I couldn't reproduce the problem.
Comment 6 Patrick Keegan 2003-04-07 15:32:51 UTC
Milan, do you have any idea with it's just a problem with our proxies or whether it's a general problem 
with proxies? Proposed relnote:

"If you access the Web through a proxy, using the Javadoc Manager to mount Javadoc as an HTTP filesystem 
does not work."
Comment 7 Milan Kubec 2003-04-07 15:58:23 UTC
I cannot say for sure where is the problem, if it's just our SWAN
proxy or it's general proxy problem. Your note seems correct to me,
maybe you could add a bit of uncertainity :-).
Comment 8 Patrick Keegan 2003-04-07 16:19:35 UTC
OK, adding to release notes with "might not" instead of "does not".
Comment 9 _ pkuzel 2003-09-05 11:04:58 UTC
I'm taking responsibility for JavaDoc module.
Comment 10 rcoup 2003-12-16 22:14:17 UTC
Nb3.5.1/WinXP/jdk1.4.2/IE6 or Firebird 0.7

Confirmed under either browser using ide.cfg SOCKS proxy settings
(-J-DsocksProxyHost= & -J-DsocksProxyPort=). When the IDE is using the
above switches (eg. to make the update center work) then viewing
documentation via View...Documentation Indices... does not work. Take
away the proxy switches and the documentation works fine.
Comment 11 _ pkuzel 2004-03-24 10:47:16 UTC
[batch] Giving up javadoc issues exclusive ownership.
Comment 12 Jan Pokorsky 2004-06-28 14:44:24 UTC
Closing as WONTFIX since the option to mount javadoc from an http
location is not part of the product any more.