From: Markus J. (JIRA) <no...@at...> - 2006-01-28 08:54:44
|
Packaging of Hibernate binaries ------------------------------- Key: HHH-1409 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1409 Project: Hibernate3 Type: Improvement 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Steve E. (JIRA) <no...@at...> - 2006-01-28 11:46:42
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1409?page=all ] Steve Ebersole updated HHH-1409: -------------------------------- Component: build > 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Alexander Z. (JIRA) <no...@at...> - 2006-06-09 08:33:35
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1409?pa= ge=3Dcomments#action_23304 ]=20 Alexander Zynevich commented on HHH-1409: ----------------------------------------- Just my 0.02=C2=A3: It would be good if this client side jar contained no only collection\excep= tion but also evrything required to "support" proxy on client side (i.e. se= rialization of proxy, ability to call getId() on proxy without opening sess= ion). I know about hibernate-client.jar @jBoss, but it is better to have it= in hibernate project. > Packaging of Hibernate binaries > ------------------------------- > > Key: HHH-1409 > URL: http://opensource.atlassian.com/projects/hibernate/browse/H= HH-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 becaus= e on the client side, Hibernate Exception classes as well as Collection cla= sses needs to be found at runtime. Well, it would be possible to take care,= that all exceptions are converted into application exceptions (no hibernat= e exceptions set as cause) and all collections are copied into collections = of type java.util.Collection. Obviously this will remove the need of a hibe= rnate.jar file on the client side, but the advantages of e.g. persistent co= llections are lost.=20 > 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 reas= on 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 on= ly contains classes needed on the server side of the application. > kind regards > Markus Jessenitschnig --=20 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= .jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |