I\'m currently working on the project where this discussion came and I wanted to ask others what do they think about this.
I have a DAO infrastructure as follows: StoreDao, CouponDao, PersonDao. All these extend from a GenericDao which has the bulk of the functionality(using Java Generics).
I have a DAO recordset that gets created fine and I can transfer the records from the set to a table, this is done row by row and works well but I am transfering a large amount of data at once so this
I already have an application implemented in Struts. I am trying to move it to Spring so I am doing everything step by step. First plan is to implement IOC (DI). now I got my DAOs fixed, i got my appl
I am working on a java web application that calls database backend through hibernate.I use servlets,jsp and tomcat for test/deployment.Most books on java-ee suggested using Dao classes for database ca
In my web application(jsp+hibernate+hsqldb on tomcat) code, I am using couple of Dao implementations.The base class Dao implementation contains all the session open,close logic.A number of domain spec
I tried to google the answer, but I am still puzzled about their relationship. I speculate Hibernate is a kind of DAO.
Since the classic OOP model is broken anyway, despite all the goodies of ORM, why do I need to annotate the following two example attributes in my entity class:
I want to export some data in one recordset in Access to Excel. I know the DoCmd.TransferSpreadsheet command but it works only with stored queries, and in my case it\'s a runtime-filtered record开发者
I just started learning OOP and I\'m finding it really hard to decide where functionality belongs. Let\'s use a down vote in SO for our example:
加载中,请稍侯......