tag:blogger.com,1999:blog-35020569.post115999121505820416..comments2007-04-05T20:11:55.685-07:00Andrés Testihttp://www.blogger.com/profile/16389222274573646435noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-35020569.post-1170770580169940082007-02-06T06:03:00.000-08:002007-02-06T06:03:00.000-08:00mmmm iqual to LinQ.::[Tomas]::.http://www.blogger.com/profile/16961593900367521825noreply@blogger.comtag:blogger.com,1999:blog-35020569.post-1160442653064155222006-10-09T18:10:00.000-07:002006-10-09T18:10:00.000-07:00I think "virtual field" is a better name.<BR/>Do you think so?fkpwolfhttp://www.blogger.com/profile/09657068234938776019noreply@blogger.comtag:blogger.com,1999:blog-35020569.post-1160064568443905512006-10-05T09:09:00.000-07:002006-10-05T09:09:00.000-07:00Interesting post. Not sure whether I have understood everything, but doesn't your feature request boil down to the more general case of Domain Driven Development ?<BR/><BR/>(http://www.amazon.com/Domain-Driven-Design-Tackling-Complexity-Software/dp/0321125215)<BR/><BR/>Basically, the idea is that the core classes (that are also persisted) are intelligent, and have the behavior built-in. <BR/><BR/>However, it doesn't mean that technical code is written inside the domain. It is possible to use Frameworks such as Spring 2 and AspectJ integration to inject dependencies to domain objects..<BR/><BR/>So, for your case, you would have the specific queries implemented inside DAOs, or other technical classes, independant of the implementation, and the reference to the DAos would be injected to the domain classes.samokkhttp://www.blogger.com/profile/02516363962443653875noreply@blogger.com