Yes, I believe that is a good approach, though I'm no expert on the subject. Often one creates a customized EJB facade for each form on the UI, which provides the required services for that form....
Type: Posts; User: arikkfir; Keyword(s):
Yes, I believe that is a good approach, though I'm no expert on the subject. Often one creates a customized EJB facade for each form on the UI, which provides the required services for that form....
Actually - this would make a nice project to write. We could use annotations in the domain objects, and dynamically create DTOs (via cglib/dynamic proxies). These generated DTOs will automatically...
Regarding relations, well..we don't ;-) If a relation from a model is requested, and the data for that relation was not brought to the client, there are three alternatives:
1) Throw an exception -...
AFAIK, this has never been resolved. I believe the Hibernate team focuses on the server and not on the network/client and therefor do not address this, though I might be wrong here.
What we are...
I agree - JDK1.5 Generics even make this more beaufiful:
public interface BaseDao<T> {
T findByPrimaryKey(Key<T> pKey);
List<T> findAll();
...
}
I'm talking about a scenario where a domain object is serlialized to the client tier, where I don't (nor shouldn't I believe) have the Hibernate runtime or access to the database.
How else would...
I think there should always be a facade (usually thin) layer between the UI and the DAOs. That's because requirements shift and change constantly, and what appears as a simple request for some...
An idea:
Why not create an AOP BeanPostProcessor which accepts some sort of mapping between properties and other bean-id's methods, so that when the client calls an uninitialized field, the AOP...