That's right. Isn't that "attacking"? It means that if you build a
Java Bean, you have the choice of embedding yourself in any kind of
container. By picking ActiveX, you're stuck on Wintel. That's a
pretty compelling reason to build Beans and not OCXs, I'd say.
>Or even better... move to a fully realized component model where any
>component can send messages to any other component, in any container,
How about a java.ii package? 8-)
You II folks should bug Waldo et al at Javasoft East and try and
get early access to JavaSpaces. Looks extremely cool. The second
alpha draft spec came out a few weeks back.
>See, I read that members of the OpenDoc team were shopping around for a
>new home. Maybe they'll end up at Javasoft.
Things still have to settle down from the IBM/Sun/Oracle/Novell(!)
get-together. I'm sure they're working on the big picture, but I
have no idea what form it might take. But with all that CommonPoint
and OpenDoc knowledge, I'm betting it'll be good.
I've got an efriend at Sunsoft who appears to be right in the middle
of all this stuff. He created "Visual Java Beans", which is bundled
with Solstice Workshop. It's supposed to be an incremental improvement
on BDK 1.0, but I honestly haven't had any time to look at it in detail
to see what's new.
-- Mark Baker, Ottawa Ontario CANADA. Java, CORBA, OpenDoc, Beans email@example.com, firstname.lastname@example.org http://www.iosphere.net/~markb
Will distribute business objects for food.