[Opensource] Future Code for Expresso 5.1 and beyond [LONG THINK TANK ARTICLE]

[Tino Dai]

Just when I though I understood Expresso..........
On Sat, 2002-11-02 at 23:20, Michael Rimov wrote:
> SO!  Let's discuss where to go:
> 
> I've been doing some look at how Apache Avalon and some other frameworks do 
> things, and have been coming up with my own ideas:
> 
> 1 - Most component metadata should be removed from code and stored in 
> configurations [whether database, XML files, property files, 
> etc].  Examples of such metadata are:
> 		-dbobject.setupFields()
> 		-Configuration settings.
> 		-Controller state definitions.
> 		-Schema definitions.
When you say metadata in reference to component metadata? What is that
and where is it stored? Could you please give an example

Also, in my dealing with the expresso framework, I have notice something
that may or may not be there. Is there a mechanism in Expresso that
forbids the collision of table names in the underlying database? For
example, there is a table name in Econtent called ATTRIBUTE. There could
be another application with the TABLE name of ATTRIBUTE. Is there a way
for these two to co-exist? 

Thanks,
Tino