[
http://opensource.atlassian.com/projects/hibernate/browse/EJB-255?page=co...
]
Emmanuel Bernard commented on EJB-255:
--------------------------------------
Yes this is a class of problem we are thinking about for a long time now.
But it can be solved by either:
- a regular JDBC call from your "client" to the DB (ie your client talk to the
DB)
- a "remote" JDBC (remote JDBC driver) call if you're concerned about the
number of concurrent DB connections
The remote solutions (Remote JDBC or remote EM) put some interesting distributed
transaction challenges into the equation.
Remember that an ORM already tries to minimize traffic / nbr of roundtrips between the
application and the DB, why would you want to duplicate that effort in another layer.
Remoting capabilities
---------------------
Key: EJB-255
URL:
http://opensource.atlassian.com/projects/hibernate/browse/EJB-255
Project: Hibernate Entity Manager
Type: New Feature
Reporter: Dimitry Voytenko
I came across Kodo's implementation of remote persistent managers for both JPA and
JDO:
http://www.solarmetric.com/Software/Documentation/3.2.0RC2/docs/ref_guide...
http://www.solarmetric.com/Software/Documentation/3.2.0RC2/docs/ref_guide...
The solution looks pretty ellegant. The main idea behind it is that server and client
communicate b/w each other using object graphs (no proxies and no object serialization
required) and thus working with JDO/JPA objects on client looks exactly the same as on the
server, removing necessity of DTO objects in the majority of cases.
Have you ever thought about including similar functionality for Hibernate? I do believe
it could be a great peformance booster for many types of applications.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira