Components, Objects, and Beans

There is an ongoing debate on Spring Python's usage of the term "component". There is associated baggage with this term.

Spring Java, as many are aware, uses the term "bean", since they are founded on POJO programming practices, making bean a simple solution at the time.

Spring.NET uses the term "object".

Considering Spring Python is still young and more importantly, pre-1.0, if you had a choice in picking a name for a managed POPO (plain old python object), what would you call it?

Hi,
I think object is the way to go, component is so overloaded a term, it might make people think Spring is doing more that it really is, i.e. some old school component model etc. which tend to be tied via inheritance to some technology etc. BTW, versions of spring in action-script also use the <object> notation.
my 2cents.
Mark

Based on feedback both in this forum and through private email, I have decided to migrate Spring Python from "components" to "objects".