The time when IBM UK's "Java Evangelist" was telling me that the Java environment was the interesting thing, that the Java language would co-exist with other, more interesting ones, such as Eiffel.
The time when Java looked like a usefully platform-neutral technology to roll into the distributed systems that we already knew very well how to build using CORBA. The time when Java looked as if it would play well with others.
What happened was that a bunch of Java technologies for doing web front-ends (servlets: quite nice in their way), and for implementing the servers behind them (EJB, JDBC: a waking nightmare) got rolled together under the Java 2 Enterprise Edition rubric. This many-headed hydra was picked up by many of the dot-com's and suddenly became (for political and marketing reasons) the must have technology for any large corporation producing a web offering.
One of the goals of the original Java project was to produce a language in which it would be safe for people to download executables from the 'net written by any old developer, and any old developer who wasn't very good, either. As a side effect this produced a language that the IT drones in those same large corporations, and also wet-behind-the-ears Comp. Sci graduates could learn very quickly.
Sun began to promote themsleves as "the dot in dot-com", and to allow systems that made the grade to bear the "100% pure Java" livery. And also to sell huge servers by the skip-load, since EJB performed very, very badly in its early incarnations. The net result was that any interest in the other languages that run on the JVM dropped to zero, and any interest in inter-operating Java components with any non-Java components (except business critical legacy ones) also dropped to zero.
And thus most opportunities for interesting, innovative work were eliminated in the majority of large programming shops; many commerical developers had their minds turned to jelly by a weak and flabby language; and I hightailed it to the embedded sector. Not that I'm bitter ;-)