|
> From: Bartell, Aaron L. (TC) > > I agree with you. I think where business logic could be use though is > with OO Interfaces. Thoughts? I think there are two cases: In certain instances you may have to materialize an entity from your RDB in your Java code. This is not a regular occurrence, but there may be cases when it's better to cache certain information in Java objects. In that case, the objects should be wrappered inside a Factory that implements persistence through calls to server programs. Second is a pure OO call to a server. This would be done through a proxy object whose sole purpose is to format the request to send to the server then reformat the response for the caller. Again, this is not a regular occurrence, and I think it would be primarily used in JDBC-based queries that need access to derived fields that are best done via a business logic server. I don't have a good, real-world example of either case. Joe
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.