Caching in M5 With JDK 1.4.2.0x [message #115766] |
Mon, 04 July 2005 12:25 |
Alain Marc Pannetier Messages: 26 Registered: July 2009 |
Junior Member |
|
|
Dear all,
Resource Caching introduced in M5 is a welcome addition. However I had
(and solved) a weird problem with SUN JDK 1.4.2.06.
Not sure what the root cause is...
If someone can shed some light on that one...
0 - I'm behind a firewall/proxy.
1 - Preferences - I configured my JDKs/JREs, XDoclet, my proxy, re-enabled
caching (I really believe this check box should be unchecked by default).
2 - New Dynamic web project wizard... Stuck. After the usual "fiddling
with settings" delay. Hard kills of Java processes etc... I had to see
things running under debug. So I imported some plugins with source
(namely
- org.apache.xerces
- org.eclipse.wst.common.uriresolver
- org.eclipse.wst.internet.cache
- org.eclipse.wst.internet.proxy
- org.eclipse.wst.validation
- org.eclipse.wst.validation.ui
- org.eclipse.wst.xml.core)
and run the workbench under debug.
All what the internet proxy plugin does is, in the earlyStartup callback,
to
define the wellknown system properties http.proxyHost, http.proxyPort in
various combinations according to the preferences in the prefs store.
That should be good enough.
As it turned out in my 1.4.2.06 JDK at least,
sun.net.www.http.HttpClient.java did not honour correctly these properties
(only with the workbench though, other test programs were doing just fine).
I discovered this weird behaviour once I had rebuilt rt.jar with a version
of HttpClient.java pulled out of the SUN COMMUNITY SOURCE LICENSE distro.
Finally I also installed 1.4.2.08 and everything worked perfectly right
from the start (a little length the first time of course but then XML
validation was lightening fast after once the cache is populated).
I might have done something wrong in the first place but can't really see
what now.
However if anybody experience the same pb, the quick fix is to upgrade to
1.4.2.08 (or another JDK for that matter).
Otherwise, thx to the WTP committers, quality is improving. And I really
love the XSD editor. Now I'll test the JST side...
Alain Pannetier
|
|
|
Re: Caching in M5 With JDK 1.4.2.0x [message #115781 is a reply to message #115766] |
Mon, 04 July 2005 13:08 |
Eclipse User |
|
|
|
Originally posted by: hcs33.egon.gyaloglo.hu
Hi,
It is maybe related to java bug 5019401
(http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5019401) which has been
fixed in JDK 1.4.2_07 ("ServerSocket(Proxy) and Socket(Proxy) do not work
with sun one proxy server").
Regards,
Csaba
Alain Pannetier wrote:
> Dear all,
>
> Resource Caching introduced in M5 is a welcome addition. However I had
> (and solved) a weird problem with SUN JDK 1.4.2.06.
> Not sure what the root cause is...
> If someone can shed some light on that one...
>
> 0 - I'm behind a firewall/proxy.
> 1 - Preferences - I configured my JDKs/JREs, XDoclet, my proxy, re-enabled
> caching (I really believe this check box should be unchecked by default).
> 2 - New Dynamic web project wizard... Stuck. After the usual "fiddling
> with settings" delay. Hard kills of Java processes etc... I had to see
> things running under debug. So I imported some plugins with source
> (namely
> - org.apache.xerces
> - org.eclipse.wst.common.uriresolver
> - org.eclipse.wst.internet.cache
> - org.eclipse.wst.internet.proxy
> - org.eclipse.wst.validation
> - org.eclipse.wst.validation.ui
> - org.eclipse.wst.xml.core)
> and run the workbench under debug.
>
> All what the internet proxy plugin does is, in the earlyStartup callback,
> to
> define the wellknown system properties http.proxyHost, http.proxyPort in
> various combinations according to the preferences in the prefs store.
> That should be good enough.
>
> As it turned out in my 1.4.2.06 JDK at least,
> sun.net.www.http.HttpClient.java did not honour correctly these properties
> (only with the workbench though, other test programs were doing just
> fine).
>
> I discovered this weird behaviour once I had rebuilt rt.jar with a version
> of HttpClient.java pulled out of the SUN COMMUNITY SOURCE LICENSE distro.
>
> Finally I also installed 1.4.2.08 and everything worked perfectly right
> from the start (a little length the first time of course but then XML
> validation was lightening fast after once the cache is populated).
>
> I might have done something wrong in the first place but can't really see
> what now.
>
> However if anybody experience the same pb, the quick fix is to upgrade to
> 1.4.2.08 (or another JDK for that matter).
>
> Otherwise, thx to the WTP committers, quality is improving. And I really
> love the XSD editor. Now I'll test the JST side...
>
> Alain Pannetier
|
|
|
|
Powered by
FUDForum. Page generated in 0.03295 seconds