How to cope with non-static database schemes

[Fabian Kurth <fa...@bluewin.ch>]

As part of an application that I'm thinking about, users may specify new db 
tables which are then added to the database. The names of such tables, as 
well as the number and data types of their fields, are chosen by the user 
himself (step 1). Following the creation of a new table, the user should be 
presented an appropriate input form, allowing him to enter data (step 2). 
(How) is it possible to provide the corresponding form beans and action 
classes and (how) do they have to be registered in struts-config.xml? 
Compared to working with a static db scheme, what's the difference in 
approach? -- Thanks a lot, Fabian 



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org