I definitely understand the motivation for
the performance fix. But the result is a regression from WTP 1.0: we now have a
project node visible by default.
Could we revert the perf fix (or hide the
node by default) in the 1.5 stream?
In the 2.0 line, a programmatic
enable/disable call would be good, but again I think the key is that the node
should be hidden by default.
wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf Of Chuck Bridgham
Sent: Wednesday, May 09, 2007 7:06
To: General discussion of
project-wide or architectural issues.
Subject: Re: [wtp-dev] Web
Services node in the Project Explorer
Hi - not sure if I missed some of the discussion here -
but I agree we should have a programatic way to disable this node if desired.
change was done after realizing a severe startup performance issue populating this
node (scans the entire workspace regardless of size).
this was done on a background thread, if still slowed overall statup
performance, and was deemed severe enough to change the behavior
laziliy search for webservices after users expand the tree node. We
needed to make this node visible to do this.
Rational Java Enterprise
Tooling Team Lead
IBM Software Lab - Research Triangle
Phone: 919-254-1848 (T/L: 444)
"Raev, Kaloyan" <kaloyan.raev@xxxxxxx>
05/07/2007 03:27 AM
"General discussion of project-wide or architectural issues."
[wtp-dev] Web Services node in the Project
the last I-build, I have noticed new node in the Project Explorer -
"JSR-109 Web Services".
I know that users can hide it from the Customized View dialog and I suggest that
adopters can do this by default.
But I am wondering what is the purpose of this node and isn't it some kind of
reviving of look and feel from WTP 1.0?
NW AS JS TOOLS JEE (BG)
SAP Labs Bulgaria
wtp-dev mailing list