Hi, I started a new message for this topic and copied in some of the text from the messages so that we get a new thread in the message archive.
I personally believe that "beans" is a totally stupid name, created by some developers trying to be too-cute-by-half (a "bean" is a little piece of Java/coffee), and it is Java-centric. The marketing people at Sun must have had nightmares trying to figure out how to convince Corporate technology purchasers that "Java Beans" is a serious technology. Furthermore, Sun created extra confusion by having "Java Beans", most often used for user interface widget development, and "Enterprise Java Beans", dealing primarily with entity object access on the server. I think Gunther's suggestion is a fine one (-0), because he is simply saying that the Sun people did a decent job in overcoming those obstacles, and now the term has reasonable traction in the marketplace. So I don't really have a better suggestion than his. If people still want to discuss this, have at it. I think it is premature, and nothing will really get resolved until we have code that does something. Then we can give it a good name that is descriptive of what it does rather than being a cutesy name. Stephen At 07:46 PM 11/16/2001 +0800, you wrote: >I think in this case although all this bantering is quite fun, I prefer >bean because it is a fairly standard term that people will pick up on even >if they don't know Java. Oysters and other such things will just be confusing. > >Later, > Gunther > >At 06:54 PM 11/16/2001, Greg McCarroll wrote: >>* Randall Marbach ([EMAIL PROTECTED]) wrote: >> > Now that we have a name for p5ee, are we going to call >> > the components "beans" or "pearls" or ???? >> >>I've always thought they would be called Oysters and I think I've seen >>Paul Kulchenko use that term as well. >> >>Why Oyster? Because an Oyster sometimes has a Pearl inside. And the >>equivalent of a bean will be something used to hold Perl objects >>(which may or may not have significant code attached). >> >>On this note, I started some experimental work on a container type >>system for Oysters recently and I called it a Pot, as in Oyster Pot. >>
