<![CDATA[<!-- Begin Anonymizer Control Bar -->
<center><form method="POST" action="/" target="_top">
<table width="600" border="0" bgcolor="#9999FF" cellpadding="2" cellspacing="0"><tr><td>
<table width="100%" cellpadding="1" cellspacing="0" bgcolor="#000099"><tr><td>
<b><font color="#FFFFFF">Please visit the Anonymizer's Sponsors:</font></b><br>
<!-- BEGIN LINKEXCHANGE CODE --><center>
<a href="/" target="_blank">
</a><br>
<a href="/" target="_blank">
</a>
</center><!-- END LINKEXCHANGE CODE -->
</td></tr><tr><td>
<table width="100%" border="0" bgcolor="#000099" frame="BELOW" cellpadding="1" cellspacing="0">
<tr><td nowrap align="center" valign="middle" width="35%">
<font color="#FFFFFF">
<small>
<input name="signup" id="signup" value="Sign Up for a Premium Account!" type="Submit">
</small>
</font>
</td>
<td nowrap width="65%" valign="middle" align="left">
<table border="0" width="100%" valign="middle" align="left">
<tr><td colspan="2"><center><b><font color="#FFFFFF" face="Sans-Serif">
Page loaded anonymously by Anonymizer.com
</font></b></center></td></tr>
<tr><td width="35%" nowrap>
<font color="#FFFFFF">
<small>
<input onclick="if (query.value == "") query.value="http://"; do_it.value="Go!"" type="RADIO" name="action" id="action" value="go" checked> Jump anonymously to this site:<br>
<input onclick="if (query.value == "http://" || query.value == "https://") query.value=""; do_it.value="Find!"" type="RADIO" name="action" id="action" value="search"> Search anonymously for:
</small>
</font>
</td><td width="65%" align="left" nowrap>
<font color="#FFFFFF">
<small>
<input type="HIDDEN" id="engine" name="engine" value="Default">
<input type="TEXT" id="query" name="query" value="http://" size="30">
<input type="Submit" name="do_it" id="do_it" value="Go!"><br>
</small>
</font>
</tr></td>
</table>
</td></tr>
<tr><td colspan="2">
<center><hr>
<small><font color="white">
URL Encryption: <font color="yellow">Disabled</font>
Safe Cookies: <font color="yellow">Disabled</font>
Page Delay: <font color="yellow">On</font>
Banner Ads: <font color="yellow">On</font>
</font></small></center>
</td></tr></table>
</td></tr></table>
</td></tr></table>
</form>
</center>
<br>
<!-- End Anonymizer Control Bar -->
<h2>Find out where JavaWorld readers want Sun to house JDK's GUI component set.</h2><br>
<frameset rows="*,39" border="0">
<frame src="/" name="One">
<frame src="/" name="BottomNavBar" scrolling="no" marginwidth="0" marginheight="0" noresize="yes">
<noframes>
<!-- table 1 -->
<table border="0" cellpadding="0" cellspacing="0" width="100%" bgcolor="#336699">
<tr>
<td valign="TOP"><img src="../../../invis.free-sub/javaworld/icons-rd/ul-blue.gif" alt="" width="8" height="8" align="BOTTOM" border="0" alt=""></td>
<td align="CENTER" valign="CENTER">
<table cellpadding="0" cellspacing="0" border="0">
<tr>
<td>
<font color="#cccccc" size="-1" face="Arial,Helvetica,Sans-serif">
Advertisement: Support JavaWorld, click here!</font><br>
<nolayer>
<iframe src="/" height="60" width="468" marginwidth="0" marginheight="0" hspace="0" vspace="0" frameborder="0" scrolling="no"><a href="/"></a></iframe>
</nolayer>
<ilayer id="ph1" visibility="hide" height="60" width="468"></ilayer>
</td>
</tr>
</table>
</td>
<td width="1%" align="RIGHT" valign="TOP"><img src="../../../invis.free-sub/javaworld/icons-rd/ur-blue.gif" alt="" width="8" height="8" border="0" alt=""></td>
</tr>
</table>
<!-- end table 1 -->
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr>
<td rowspan="1" bgcolor="#336699"><img src="../../../invis.free-sub/javaworld/icons-rd/dot_clear.gif" alt="" width="2" height="1" align="BOTTOM" border="0"></td>
<td valign="TOP" bgcolor="#CCCCCC"><img src="../../../invis.free-sub/javaworld/icons-rd/blue-grey-ul.gif" alt="" width="8" height="8" align="TOP" border="0"></td>
<td valign="TOP" bgcolor="#CCCCCC">
<font face="Arial,Helvetica,Sans-serif">
<img src="../../../invis.free-sub/javaworld/icons-rd/dot_clear.gif" alt="" width="1" height="6" border="0"><br>
<center>
<strong>September 1998</strong><br>
<a href="/"><img src="../../../invis.free-sub/javaworld/icons-rd/jwlogo-132.gif" alt="" vspace="5" width="132" height="41" border="0"></a><br>
<font size="-1">
<strong>FUELING INNOVATION</strong>
</font>
</center>
<p>
<table width="125" cellspacing="0" cellpadding="2" border="0">
<tr>
<td align="CENTER"><a href="/"><img src="../../../invis.free-sub/javaworld/icons-rd/house.gif" alt="" width="14" height="14" align="BOTTOM" border="0"></a></td>
<td>
<font face="Arial,Helvetica,Sans-serif">
<a href="/">Home</a>
</font>
</td>
</tr>
<tr>
<td align="CENTER"><a href="/"><img src="../../../invis.free-sub/javaworld/icons-rd/envelope.gif" alt="" width="14" height="9" border="0"></a></td>
<td>
<font face="Arial,Helvetica,Sans-serif">
<a href="/">Mail this Article</a>
</font>
</td>
</tr>
<tr>
<td align="CENTER" valign="TOP"><a href="/"></a></td>
<td>
<font face="Arial,Helvetica,Sans-serif">
<a href="/">Printer-Friendly Version</a>
</font>
</td>
</tr>
</table>
<p>
<font face="Arial,Helvetica,Sans-serif"><strong><u>Search</u></strong></font>
<form action="/" method="GET" name="seek">
<table border="0" cellspacing="0" cellpadding="3">
<tr>
<td rowspan="1" colspan="1">
<input type="HIDDEN" name="col" size="-1" value="jw">
<!-- This is the text box for search terms -->
<!--See above-->
<input type="TEXT" name="qt" size="12" maxlength="2047">
<input type="image" value="search" src="../../../anon.free-sub/javaworld/icons-rd/button_blue.gif" border="0" width="27" height="25" alt="GO">
</td>
</tr>
</table>
</form>
<p>
<strong>
<a href="/">Topical index</a><br>
<a href="/">Net News Central</a><br>
<a href="/">Developer Tools Guide</a><br>
<a href="/">Book Catalog</a><br>
<a href="/">Writers Guidelines</a><br>
<a href="/">Privacy Policy</a><br>
<a href="/">Copyright</a><br>
<a href="/">ITcareers</a>
</strong>
<p>
<div align="LEFT">
<a href="/"><img src="../../../invis.free-sub/javaworld/icons-rd/jw-subscribe.gif" alt="" width="120" height="25" align="BOTTOM" border="0" hspace="3"></a><br>
</div>
<p>
<strong><u>Advertisement</u></strong><br>
<nolayer>
<iframe src="/" height="125" width="125" marginwidth="0" marginheight="0" hspace="0" vspace="0" frameborder="0" scrolling="no"><a href="/"></a></iframe>
</nolayer>
<ilayer id="ph2" visibility="hide" height="125" width="125"></ilayer>
<p>
<nolayer>
<iframe src="/" height="125" width="125" marginwidth="0" marginheight="0" hspace="0" vspace="0" frameborder="0" scrolling="no"><a href="/"></a></iframe>
</nolayer>
<ilayer id="ph3" visibility="hide" height="125" width="125"></ilayer>
<p>
<nolayer>
<iframe src="/" height="125" width="125" marginwidth="0" marginheight="0" hspace="0" vspace="0" frameborder="0" scrolling="no"><a href="/"></a></iframe>
</nolayer>
<ilayer id="ph4" visibility="hide" height="125" width="125"></ilayer>
<p>
<nolayer>
<iframe src="/" height="125" width="125" marginwidth="0" marginheight="0" hspace="0" vspace="0" frameborder="0" scrolling="no"><a href="/"></a></iframe>
</nolayer>
<ilayer id="ph5" visibility="hide" height="125" width="125"></ilayer>
<p>
<nolayer>
<iframe src="/" height="125" width="125" marginwidth="0" marginheight="0" hspace="0" vspace="0" frameborder="0" scrolling="no"><a href="/"></a></iframe>
</nolayer>
<ilayer id="ph6" visibility="hide" height="125" width="125"></ilayer>
<p>
</font>
</td>
<td align="RIGHT" valign="TOP" bgcolor="#CCCCCC"><img src="../../../invis.free-sub/javaworld/icons-rd/blue-grey-ur.gif" alt="" width="8" height="8" align="TOP" border="0"></td>
<td rowspan="1" bgcolor="#336699"><img src="../../../invis.free-sub/javaworld/icons-rd/dot_clear.gif" alt="" width="2" height="1" align="BOTTOM" border="0"></td>
<td valign="TOP" colspan="1"><img src="../../../invis.free-sub/javaworld/icons-rd/white-blue-bl4.gif" alt="" width="4" height="4" align="BOTTOM" border="0"></td>
<td valign="TOP" rowspan="2">
<br>
<h1 align="CENTER">
Developers say Sun should keep its Swing package promise for JDK 1.2
</h1>
<h3 align="CENTER">
Find out where <em>JavaWorld</em> readers want Sun to house JDK's GUI component set
</h3>
<strong>By Michael O'Connell and Jenni Aloi</strong>
<p>
<img src="../../../invis.free-sub/javaworld/icons/blue.gif" alt="" width="100%" height="2">
<p>
<!-- begin body text -->
<img align="LEFT" width="40" height="29" src="../../../invis.free-sub/javaworld/abcs/W.gif" alt="W">hen
<em>JavaWorld</em> followed the suggestion of several readers to run a
poll in early August asking "Where would you like to see Swing
packaged for use with JDK 1.2?" we thought it would generate lots
of attention. But the number of votes and comments we've received over the
past two weeks exceeded even our less-than-modest expectations. The
packaging of Swing -- the broad set of GUI components at the heart of
Sun's Java Foundation Classes software (JFC) -- is <em>definitely</em> a hot
topic among Java developers.
<p>
<table bgcolor="#FFFF66" align="right" cellpadding="4" border="1">
<tr>
<td>
Help us keep up on<br>
the issues crucial<br>
to Java developers.<br>
<a href="/">Send in your poll ideas</a>!
</td>
</tr>
</table>
<p>
Three out of four respondents (76%) said they want Swing to reside
where Sun originally intended: java.awt.swing. Roughly one out of
seven (15%) preferred that Swing remain in its current place,
com.sun.java.swing. Other respondents suggested alternative
homes, such as java.swing, javax.swing, java.jfc.swing, or jfc.swing.
<p>
As stated in the background of the poll, Sun says its decision to
house Swing in com.sun.java.swing benefits developers who have already
developed, or are developing, products using JDK 1.1. It will
also simplify the migration of products to a JDK 1.2 code base.
(JDK 1.1-compatible browsers cannot download classes from
the java.* package hierarchy, due to security issues.)
<p>
Sun also says, "Swing is core to JDK 1.2."
<p>
"The package name does not define what's core," explains Onno Kluyt,
Sun senior product manager for JFC. Though he agrees that, in
principle, core components should reside in the java.* hierarchy, Kluyt
contends that in some cases -- like Swing, or the CORBA package
(org.omg.corba) which is also considered core by Sun -- it may be
better to put components outside the java.* hierarchy for reasons such
as "compatibility with existing solutions" and the need to retain an
"association with an industry standard."
<p>
"Swing has been part of the core design of JDK 1.2 right from the start,
notes Kluyt. "The Swing implementation was ready before JDK 1.2 would
be available. So at the time we decided to make Swing available for
JDK 1.1 environments in the com.sun.awt.swing package and announced
that the package would be in java.awt.swing for JDK 1.2. This was
reflected in JDK 1.2 Beta 3.
<p>
"Our main objective with the current naming scheme (com.sun.java.swing
for core and unbundled versions of Swing) is for the package name to
be identical in both cases," Kluyt said. "javax.swing and java.swing
would create a third-name candidate for the Swing package and force
everybody to migrate. Additionally, the javax.* namespace is
reserved for standard extensions. Putting Swing, a core package,
in that namespace would create confusion [about] whether Swing is
core and whether or not standard extensions like InfoBus and JAF
are core."
<p>
Kluyt says that Java licensees must adhere to Sun's definition of core,
which is not inherently limited to java.* components. He says many
people may have based their votes in part on confusion about the
definition of <em>core,</em> and acknowledges that Sun must better
educate the Java community about this important distinction. "We need
to [explain] what core means. I don't think this package name
[com.sun.java.swing] necessarily increases the risk of
incompatibilities on the platforms."
<p>
Apparently, education indeed is in order, and should extend not only to
licensees and the Java developer community, but to Sun's own staff.
Even Tom Ball, a veteran Java engineer at Sun, recently wrote in a <a href="/">commentary
about Swing packages</a> that "Being in core requires that classes be
in the java.* hierarchy -- no way to wiggle around that requirement."
<p>
(Ball now says that when he wrote his March commentary,
his understanding of core was based on a false assumption
shared by the rest of Engineering. "It didn't actually
jibe with what the lawyers have been putting in all
the contracts ... Onno is right." )
<p>
Kluyt says Sun based its current position on input from developers.
Sun continues to look at the feedback and wants "to make sure
we do what's best for the Java community," he says. "We always have and
continue to really value the sentiments [of developers]." Readers who did not
provide comments via the <em>JavaWorld</em> poll may submit their
suggestions regarding Swing to <em>swing-feedback@java.sun.com.</em>
<p>
<font size="+1"><strong>Poll details</strong></font><br>
More than 2,500 developers took the time to respond to the question. Here's a look at the actual voter breakdown:
<p>
<ul>
<li>76% said they would like to see Swing packaged in java.awt.swing for use with JDK 1.2
<p>
<li>15% said they would like to see Swing packaged in com.sun.java.swing for use with JDK 1.2
<p>
<li>9% were unsure, or offered a different opinion
</ul>
<p>
Below is a representative sample of the comments collected in the
poll. To see all comments from this and other <em>JavaWorld</em>
reader polls, head to <a href="/">our
archive of past polls</a>. And, of course, don't forget to voice your
opinion in <a href="/">our
latest poll</a>.
<p>
<strong>I would like to see Swing packaged in java.awt.swing for use with JDK 1.2 (76%):</strong><br>
<p>
<blockquote>
<em>
<p>
Just call it com.microsoft.awt.swing. And the next new package might be
called com.ibm.awt.* or maybe com.xerox.*. Lets see...Java is an ISO
standard...not a Sun proprietary language. Microsoft will have a good
laugh over this one.
<p>
Sun should forget justifying future bad decisions using past mistakes.
This is far too common in this industry.
<p>
It seems that Sun is just asking for trouble from Microsoft by putting
the <em>crucial</em> Swing package in the vendor-specific hierarchy
com.sun.*.
<p>
The vast majority of Swing-enabled applications aren't written yet --
and for these the transition wouldn't be a problem at all. By changing
the package name Sun is: 1) making a huge opportunity for Microsoft and co.
to try to evade the library, if not by law at least in court of public
opinion; 2) making a precedent of not naming a core library with the
prefix java.* (and I'm afraid this one won't be the last, thus making
it hard for developers to remember what is core and what isn't); 3)
making an ugly aesthetic exception to the naming scheme; 4) not making
it preferable for users to migrate to Java 1.2 as fast as possible; 5)
missing an opportunity to make a coherent library with the rest of the
API. In a few years nobody will remember Java 1.1 or before
(thus the naming exception will be short-lived), but the
inconsistent naming will remain forever. As a developer, I urge Sun to reconsider
the recent decision and do the right thing -- name it java.awt.swing!
<p>
Do it right. Don't kludge for compatibility; it will come back and bite you
later.
<p>
It's very important that Swing is a core component of the Java API and
therefore should be packaged that way. It breaks all the rules to have
a com.sun.* package part of the core API, and will inevitably lead to
problems.
<p>
It seems to break the standard naming conventions, is confusing, and is
detrimental to the Java platform's simplicity in the name of backward
compatibility, not to mention opening the way for future nonstandard
naming! I think it is wrong, and that complete backward compatibility
should wait until Java is a solid stable platform that doesn't
change every few months!
<p>
Not having the package in java.awt.swing will make it too easy for
Microsoft to claim it's not really core, no matter what Sun says, and
omit it from its VM.
<p>
The effort of migrating existing software to a different package name
is a blink of an eye compared to complexity added by introducing
unnecessary exceptions to an otherwise simple and precise rule.
<p>
With the advent of the Java Lobby and initiatives such as Kaffe, Guava
and Kore, there is no reason the Java community should support Sun
in any effort to make Java more proprietary. It seems to
me that conversion utilities can't be all that difficult to build, and
the Java Lobby and Wooden Chair are offering a Swing package converter
right now. Besides, with the likely growth of many thousands of
packages, developers are going to expect repackaging and refactoring
tools as part of their development environments. The biggest issues
with repackaging and refactoring of third-party code concern
compatibility with yet other third-party code using and/or expecting the
original packaging and behavior. I shudder to think about the
proliferation of package wrapper packages. This will certainly not be
an obvious or easy issue to resolve, but keeping all the core Java
classes under the java or javax packages certainly makes a lot of sense
to me and postpones any need to address this type of problem for the core classes.
<p>
Migration problems? Swing was a beta. If you used it without
considering the consequences, it's your problem. Don't ask everyone else
to suffer forever because of your poor software construction practices.
This lazy mentality is why the software industry "enjoys" its
(deserved) reputation for poor quality products.
<p>
It appears to be a short-sighted short-termed solution just to enable
people to use Swing in Java code running in browsers.
<p>
I feel that Sun ought to release the Swing package as soon as possible
to perpetuate the momentum of developers using Swing (Swing is cool),
but it needs to be in the core. Sun should make a transition release
and then provide a migration path for the package to be added to the
core (the migration tool should be free). Sun should provide some guidelines
to developers so that the migration tool will work correctly. In
fact, it could call the non-core release a "deprecated" section.
<p>
If Swing is to be considered part of the core Java API, it really
<em>must</em> be included under the java.* hierarchy. Otherwise, there
will be no end of argument on the part of Microsoft and others as to whether
or not their VM implementations need to bundle it.
</em>
</blockquote>
<p>
<strong>I would like to see Swing packaged in com.sun.java.swing for use with JDK 1.2 (15%):</strong>
<p>
<blockquote>
<em>
Since Swing seems to be receiving huge amounts of criticism, and is
clearly not living up to initial expectations, there would seem to be
good reason to exclude it from java.awt.
<p>
Keep the core light. The Java core should be light and all other fancy
APIs should be in a separate package. This will allow us to use or not use Swing or
a maybe-compatible-tomorrow UI API from someone else!
<p>
Finally, Sun has taken some action that is actually in the best
interests of developers. Compatibility with JDK 1.1 is key, because of
the advanced level of adoption of JDK 1.1. I think that Sun also
realized that java.awt.swing would have been a non-event in the marketplace,
because there is no way the classes will make it into the
Microsoft VM. Whether these classes are "core" is something the market
will decide!
<p>
Graphical user interfaces can be a personal, even religious, thing. I
think Java should be treated as a foundational, enabling
technology. That which exists in java.awt.* is the basic code to tie
basic GUI components to the underlying operating system. That
should be in the core Java hierarchy. The Swing components are a
Sun-ism. By housing Swing under com.sun.java.swing, Sun acknowledges
that it is a contributing company as well as a creating company. By
this I mean that if other companies, groups, etc., wish, for whatever
reason, to create their own GUI package, neither they nor those using the package
will think it must be part of the core to have a functional and
robust implementation. Sun sets a precedence for extensibility.
<p>
I'd like to see Swing labeled a standard extension, which would 1)
allow bare-bones VMs to leave out swingall.jar; 2) allow Sun to release
Swing updates and patches separately from the rest of the JDK; and 3)
make it easier for other products to compete on equal footing. That
means a third choice is required: javax.swing. But since a large number
of apps already use it, com.sun.java.swing will probably have to stay.
<p>
Rewriting apps when you upgrade the JRE is not part of the agenda for
Java. And as I am presently deploying a large financial application for
java worldwide, the thought of going to my line manager and saying
we need to rewrite the code (change the import statements) when we
upgrade to 1.2 will not go down well!
<p>
Leaving it where it is will be easiest for migration reasons when moving from JDK1.1 to 1.2. However, I personally would rather see Swing in the javax.* hierarchy. It's a <em>big</em> package and a lot of baggage if you don't need it, but I feel it is more central to Java than the com.sun.* package implies.
<p>
The whole idea of naming packages with the domain name is that the
owner of the domain name can put whatever he or she likes there. This applies
to Sun as much as it does to the rest of us. There was a big outcry when
Sun originally announced it was going to move Swing when 1.2
was released. This decision shows that Sun has early adopters' concerns
at heart and I applaud it.
<p>
It seems that the majority of people have overlooked the main problem
here: Java's packaging mechanism. As long as we hard-code package
names, changes like these are going to be painful and expensive. I
think some kind of "package map" is required. This could be supplied
to class loaders, and would describe how classes should be packaged.
Hence, class-name ambiguity is resolved at runtime.
<p>
</em>
</blockquote>
<p>
<strong> Don't know/No opinion (9%):</strong><br>
<p>
<blockquote>
<em>
<p>
java.swing or java.jfc seems to be the most reasonable
location to me. Updating existing code is no big deal (and Sun could
probably easily provide a tool if it wished to), but there would seem
to be some need to provide a mechanism whereby one could run 1.1
Swing code under the 1.2 JRE without making the changeover, as we
will undoubtedly end up encountering both 1.1 and 1.2 JREs in browsers
or on desktops for a significant while.
<p>
I think Swing should replace the AWT completely. The AWT is such a load
of crap, why make Swing a part of it? I vote for java.swing.*!
<p>
Neither package name seems correct to me: Swing is part of JFC, and
thus should be added to the JFC hierarchy.
<p>
Swing is a great idea but not ready yet for the big league. Stuffing Swing into java.awt simply sets the stage for yet another version upgrade in a short time. Code compatibility is a non-issue, as so many workarounds have been offered, so there is no longer any legitimate reason to consider com.sun.*. I think java.swing or javax.swing make sense until java.awt can lend itself to the dynamic addition and deletion of classes.
<p>
How about com.crappy.language.design.swing?
<p>
</em>
</blockquote>
<!-- end body text -->
<br><br>
</td>
</tr>
<tr>
<td width="2" bgcolor="#336699"><img src="../../../invis.free-sub/javaworld/icons-rd/dot_clear.gif" alt="" width="2" height="1" align="BOTTOM" border="0" alt=""></td>
<td valign="BOTTOM" bgcolor="#CCCCCC"><img src="../../../invis.free-sub/javaworld/icons-rd/blue-grey-bl.gif" alt="" width="8" height="8" align="BOTTOM" border="0"></td>
<td valign="BOTTOM" bgcolor="#CCCCCC">
<br>
</td>
<td align="RIGHT" valign="BOTTOM" bgcolor="#CCCCCC"><img src="../../../invis.free-sub/javaworld/icons-rd/blue-grey-br.gif" alt="" width="8" height="8" align="BOTTOM" border="0"></td>
<td bgcolor="#336699"><img src="../../../invis.free-sub/javaworld/icons-rd/dot_clear.gif" alt="" width="1" height="1" align="BOTTOM" border="0" alt=""></td>
<td valign="BOTTOM" bgcolor="#FFFFFF"> <br><img src="../../../invis.free-sub/javaworld/icons-rd/white-blue-ul4.gif" alt="" width="4" height="4" align="BOTTOM" border="0"></td>
</tr>
<tr>
<td height="6" colspan="7" bgcolor="#336699"><img src="../../../invis.free-sub/javaworld/icons-rd/dot_clear.gif" alt="" width="1" height="1" align="BOTTOM" border="0"></td>
</tr>
</table>
<p>
<div align="CENTER">
<font face="Arial,Helvetica,Sans-serif">
<a href="/">Home</a> |
<a href="/">Mail this Story</a> |
<!-- print -->
<a href="/">Printer-Friendly Version</a>
<!-- end_print -->
</font>
</div>
<p>
<table width="100%" bgcolor="#336699" cellpadding="5" cellspacing="0" border="0">
<tr>
<td align="CENTER">
<table cellpadding="0" border="0">
<tr>
<td>
<font color="#cccccc" size="-1" face="Arial,Helvetica,Sans-serif">
Advertisement: Support JavaWorld, click here!</font><br>
<nolayer>
<iframe src="/" height="60" width="468" marginwidth="0" marginheight="0" hspace="0" vspace="0" frameborder="0" scrolling="no"><a href="/"></a></iframe>
</nolayer>
<ilayer id="ph7" visibility="hide" height="60" width="468"></ilayer>
</td>
</tr>
</table>
</td>
</tr>
</table>
<p align="CENTER">
<a href="/">(c) Copyright 1998 ITworld.com, Inc., an IDG Communications company</a>
</p>
Feedback:
<a name="jweditors" href="/">jweditors@javaworld.com</a><br>
Technical difficulties:
<a name="webmaster" href="/">webmaster@javaworld.com</a><br>
URL: http://www.javaworld.com/jw-09-1998/jw-09-pollresults.html
<br>
Last modified: Tuesday, April 18, 2000
<layer src="http://invis.free.anonymizer.com/http://ad.doubleclick.net/adl/idg.jw.com/archives;sz=468x60" visibility="hide"></layer>
<layer src="http://invis.free.anonymizer.com/http://ad.doubleclick.net/adl/idg.jw.com/archives;sz=125x125;tile=1" visibility="hide"></layer>
<layer src="http://invis.free.anonymizer.com/http://ad.doubleclick.net/adl/idg.jw.com/archives;sz=125x125;tile=2" visibility="hide"></layer>
<layer src="http://invis.free.anonymizer.com/http://ad.doubleclick.net/adl/idg.jw.com/archives;sz=125x125;tile=3" visibility="hide"></layer>
<layer src="http://invis.free.anonymizer.com/http://ad.doubleclick.net/adl/idg.jw.com/archives;sz=125x125;tile=4" visibility="hide"></layer>
<layer src="http://invis.free.anonymizer.com/http://ad.doubleclick.net/adl/idg.jw.com/archives;sz=125x125;tile=5" visibility="hide"></layer>
<layer src="http://invis.free.anonymizer.com/http://ad.doubleclick.net/adl/idg.jw.com/archives;sz=468x60" visibility="hide"></layer>
]]>
Other Stories:
Braving uncharted waters: global directories
Deutsche Telekom's results hit by competition
China's PC sales grow in first half of '98
Users: Put focus on 'mindshare'
Oracle8i aimed at outmaneuvering Windows Everywhere
Sybase, Abaco join forces to mobilize ERP apps
Compaq unveils AP500 workstation with 450-MHz Pentium II
NT 5.0 hits the halfway mark
Windows NT 5.0 gets bigger & later
Microsoft moves closer to NT 5.0
Story index for IDG.Net
This is a computer-edited content for no-frames display browsers or clawlers.
To see the fully formated content, get a frames-capable browser and surf to http://www.javaworld.com/jw-09-1998/jw-09-pollresults.html