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 181033

Summary:	java.net.UnknownHostException: www.springframework.org
Product:	xml	Reporter:	averri <averri>
Component:	Retriever	Assignee:	Svata Dedic <sdedic>
Status:	RESOLVED INCOMPLETE
Severity:	normal	CC:	pete911, slsap01
Priority:	P3
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:	165542
Attachments:	stacktrace stacktrace

Description averri 2010-02-22 06:35:42 UTC

This bug was originally marked as duplicate of bug 157850, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE Dev (Build 201002152000)
VM: Java HotSpot(TM) Client VM, 16.0-b13, Java(TM) SE Runtime Environment, 1.6.0_18-b07
OS: Windows Vista

User Comments:
averri: Editing Spring configuration file.




Stacktrace: 
java.net.UnknownHostException: www.springframework.org
   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)
   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
   at java.net.Socket.connect(Socket.java:525)
   at java.net.Socket.connect(Socket.java:475)
   at sun.net.NetworkClient.doConnect(NetworkClient.java:163)
   at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)

Comment 1 averri 2010-02-22 06:35:46 UTC

Created attachment 94386 [details]
stacktrace

Comment 2 Exceptions Reporter 2010-05-26 03:47:32 UTC

Created attachment 99469 [details]
stacktrace

Comment 3 Svata Dedic 2012-02-08 15:11:40 UTC

(In reply to comment #1)
> Created attachment 94386 [details]
> stacktrace

How did you get this stacktrace ? I've tried to invoke a completion on Spring context file while disconnected from the network (NetBeans 7.2 dev build) and no error appeared (at least not on screen). Unreachable schemas should not be reported in an error dialog indeed.
Please provide more info.

The stacktrace in comment #2 is not related to XML, it belongs to J2EE support; will not file a separate issue as the report is ~2 years old and is likely to be either reported or fixed already.