|
>Sounds to me like you don't really want to store the CLASS in the database ... but the OBJECT. No, actually I do want to store the class. Let's say we implement the document generator with the ability to ask TextBox, Date and TextArea questions. Then we want to add the ability to ask DropDownList questions. We'd create a class that knew how to draw the HTML for Drop Down Lists and add it into the system and we'd be all set. You're right, we need a way to store the data (object) too, but that's covered via a method on the TemplateFieldTypeGeneratorInterface we've defined. I'm really looking for a way to store classes in the DB. Think of them as plug-ins. You can develop plug-ins for this system and upload them to the system. I want to store the plug-in in a database, but the plug-in is a java class. -Walden ------------ Walden H Leverich III Tech Software (516) 627-3800 x3051 WaldenL@xxxxxxxxxxxxxxx http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.)
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
