Hi all! > If a bean (a.k.a. a Java class) is written 'properly' i.e. > after formal > analysis and design it should not > change very often at all. Would you have confidence in a > database that kept > changing it's table structure? and the DBA who kept having to > migrate from > one version to the next? > > Perhaps you are taking a sub-optimal approach to your use of > Java? If you > really need to cope with dynamic > meta-data you should look for a design 'pattern' that meets > your needs more > appropriately. Perhaps you could describe your requirements > more fully so > that we could be more helpful? I am talking about classes that I'm still programming on. Do you have a more appropriate way of testing classes than testing them in the surrounding that they a supposed to work in? -- Steffen Vo�, Splendid Consulting GmbH & Co KG Skandinaviendamm 212, 24109 Kiel, Germany fon: 0431-660 97-0, fax: 0431-660 97-20 mailto:[EMAIL PROTECTED], http://www.splendid.de =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". Some relevant FAQs on JSP/Servlets can be found at: http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.html http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
