Does anyone use the “swingx” extensions to Swing?

问题:

I've seen "swingx" mentioned and referred to here.

However, every time I try to visit the site:

http://swinglabs.org/

It's down! Is this still an active, viable project? Or is it outdated and abandoned?

回答1:

the assumed dead are most likely to live on: announcement of SwingX 1.6 And as one the owners of the project, I can assure you that it's very much alive and very much kicking.

Update Aug. 2012

And still alive and kicking, current version is 1.6.4

回答2:

According to the SwingLabs SwingX project page, the project is still active and, actually, the project team seems to be preparing the release of Swingx 1.6 so it doesn't look like dead.

回答3:

I use it.

It's down now (Sun Sep 20 20:04:37 CDT 2009) because "Maximum Connections Reached: 4096 -- Retry later" I'm guessing too many people use it. The swingx subproject page is up though https://swingx.dev.java.net/. I must say that swinglabs has never, until now, been down for me. It has always been very slow, but never unreachable.

Swingx recently went to 1.0. People sing java 1.5 should not expect further updates and swinglab's effort is going to be placed in unifying their sorting/filtering with java 1.6 sorting/filtering.

回答4:

you can check this link which contains the statement:

Important note: SwingX 1.0 is the last release targeted at Java 5 (JDK 1.5, "Tiger"). Immediately after the release, the codebase was - in fact, still is - moved to target Java 6 (JDK 1.6, "Mustang").

the recent activity on the forum indicates that there are in fact many current users.

回答5:

Swinglabs website has been down at least since july (google "swinglabs down") Despite the assurances here, I will assume it's dead and move on.

回答6:

"Each HTTP listener has an associated connection queue where requests that are waiting to be serviced are placed. The requests are taken out of the queue and serviced by one of the available processing threads. As expected, as the number of requests waiting to be serviced increases, the response times for those requests also increase. Additionally, the server will reject new requests if the number of items in the queue has reached a maximum configured value (default is 4096). The various parameters that can be configured for the connection queue and their default values are given below":

http://blogs.oracle.com/binublog/entry/glassfish_tuning_http_connection_queue