On Thu, 16 Feb 2006 09:07:49 +0100, Scott M Stark <[EMAIL PROTECTED]>
wrote:
But here we are talking about what exists after the object in question
has been serialized outside of the jvm. Does what your talking about
still apply in that situation?
If I understand your question correctly, then yes and maybe no ;)
yes, in the case of hibernate because the serialized object is detached and
thus can be sent back to the client for the purpose of being
reattached/made persistent again,
here the PersistentCollection and proxied objects with its internal id is
relevant.
maybe no, because EJB3 does not seem to have the possibility to reattach,
it only
supports merge. But that still makes it required/needed that a lazy object
can be represented
as something that looks and feels like an object (e.g. for
child.setParent(proxiedParent) and to get
an exception for proxiedParent.getName())
Regardless, I think this discussion just
further pushes for a unified javassist based proxy framework sometime
before ejb3 is finalized.
Hibernate 3.2 is fully working on javaassist now so that is good ;)
Doesn't jboss have client side aop based interceptors running ?
Do they work without the proxy framework (javaassist.jar) ?
/max
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Max Rydahl Andersen
Sent: Wednesday, February 15, 2006 11:56 PM
To: jboss-development@lists.sourceforge.net
Cc: Steve Ebersole
Subject: Re: [JBoss-dev] client libraries on EJB3
Hi guys,
Just bumping in here to tell the "whole" story about the
needed dependencies.
Here are the reasons for ever neededing any hibernate
specific stuff on a "client" side:
1. Managing persistent collections
To track how a collection mutates so when the object
comes back to the server
hibernate can be more efficient when detecting and
executing changes.
2. Handle lazy loaded objects
If lazy="true" on a class (it is by default) the object
can be a simple proxied
shell only containing the id. This allows us to use the
object in associations
without loading it (e.g. child.setParent(proxiedParent);)
and to throw an exception
if it is accessed without being previously loaded or in a
session (e.g.
proxiedParent.getName() goes boom)
#1 does not require proxy libraries AFAIK but I have not tested it.
#2 requires the proxy libraries (in 3.2 either javaassist or
cglib), I don't know if it is feasible
to generate something that is not dependent on the proxy
library and still be able to reassociate it
when it comes back to the server.
These are important issues that should be handled in
Hibernate 3.2 if at all possible. (cc'ed steve)
/max
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
JBoss Inc
[EMAIL PROTECTED]
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
