hibernate client jar

[scesbron]

Hi,

In this post http://forum.hibernate.org/viewtopic.php?t=946665
on the hibernate forum, max from the hibernate team said that somebody in the jboss ejb3 team is working on an hibernate-client.jar. Thus kind of jar would be very helpful when working with a swing gui.

Does somebody can give me some details on the availability of such a jar

Thanx

Seb

[elkner]

Actually there is already a hibernate-client.jar in jboss/client/. However, this is not sufficient when using lazy stuff (because of the missing hibernate*Proxy) and that's why you still need hibernate3.jar and may forget hibernate-client.jar ... :(((

[maxandersen]

if it is not enough for lazy stuff we should fix that (i guess). Did you open a jira issue somewhere with a failing testcase for it ?

[elkner]

No, I haven't since JBoss Team said, problems should be posted to discussion forums first.

However, reproduction is easy:
1) Create an entity, which has a property represented by a lazy fetched collection
2) Get the remote entity with the lazy collection (i.e. server side does not fetch it)

Than, you get:

17:30:21,213 [AWT-EventQueue-0] ERROR (SocketClientInvoker.java:256) - Got marshalling exception, exiting
java.lang.ClassNotFoundException: org.hibernate.proxy.SerializableProxy
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
...
at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.resolveClass(ObjectInputStreamWithClassLoader.java:102)
...
at org.jboss.aop.joinpoint.InvocationResponse.readExternal(InvocationResponse.java:107)
...
at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:73)
at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:242)
at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:112)
at org.jboss.remoting.Client.invoke(Client.java:226)
at org.jboss.remoting.Client.invoke(Client.java:189)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:41)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:46)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:40)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:41)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:88)
at $Proxy1.getTopLevelProductGroups(Unknown Source)
at foo.bar.article.CatalogTreeModel.getTopLevelChildren(CatalogTreeModel.java:232)

Client side libs (vanilla 4.0.3SP1):

asm-attrs.jar
asm.jar
cglib-2.1.2jboss.jar
commons-logging.jar
concurrent.jar
ejb3-persistence.jar
hibernate-client.jar
javax.servlet.jar
jboss-annotations-ejb3.jar
jboss-aop-jdk50-client.jar
jboss-aspect-jdk50-client.jar
jboss-client.jar
jboss-common-client.jar
jboss-ejb3-client.jar
jboss-ejb3x.jar
jboss-j2ee.jar
jboss-remoting.jar
jboss-transaction-client.jar
jbossmq-client.jar
jbosssx-client.jar
jmx-invoker-adaptor-client.jar
jnp-client.jar
nlog4j-1.2.14.jar

[maxandersen]

looks like a bug to me.

providing a failing testcase and put it in jira will speed things up even more ;)