[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1409?page=c...
]
Max Rydahl Andersen commented on HHH-1409:
------------------------------------------
fyi build.xml already contains the jar task for building the same
hibernate-client.jar...but not finalized yet (so just for testing) .....feel free to give
feedback on it.
Packaging of Hibernate binaries
-------------------------------
Key: HHH-1409
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1409
Project: Hibernate3
Type: Improvement
Components: build
Reporter: Markus Jessenitschnig
Priority: Minor
We are using Hibernate in a typical client/server environment. Up to now we need to have
the hibernate.jar file on the classpath of both JVMs because on the client side, Hibernate
Exception classes as well as Collection classes needs to be found at runtime. Well, it
would be possible to take care, that all exceptions are converted into application
exceptions (no hibernate exceptions set as cause) and all collections are copied into
collections of type java.util.Collection. Obviously this will remove the need of a
hibernate.jar file on the client side, but the advantages of e.g. persistent collections
are lost.
To keep the size of the client side distribution small, it would be nice to have only
classes on the client side classpath which are really needed (I'm not sure if
exception and collection classes are enough). For that reason I would suggest to split the
hibernate3.jar of the distribution into two parts. A hibernate-common.jar which contains
classes needed on the client and the server side of the application, and a
hibernate-server.jar which only contains classes needed on the server side of the
application.
kind regards
Markus Jessenitschnig
--
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