is finalized.
-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
On Thu, 16 Feb 2006 10:29:46 +0100, Adrian Brock [EMAIL PROTECTED]
wrote:
On Thu, 2006-02-16 at 03:26, Max Rydahl Andersen wrote:
Regardless, I think this discussion just
further pushes for a unified javassist based proxy framework sometime
before ejb3 is finalized.
Hibernate 3.2 is
On Thu, 2006-02-16 at 04:37, Max Rydahl Andersen wrote:
JBoss Remoting has a notion of remote classloading that does
not require all the baggage of the RMI solution, like opening an http
port to make the class downloadable.
It simply requests the class over the transport you are already
On Thu, 2006-02-16 at 03:26, Max Rydahl Andersen wrote:
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 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
is finalized.
-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
]
[mailto:[EMAIL PROTECTED] On
Behalf Of Steve Ebersole
Sent: Thursday, February 16, 2006 10:10 AM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] client libraries on EJB3
Well unfortunately serialization is used in two distinct
scenarios that have vastly different
Sent: 14 February 2006 21:09
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] client libraries on EJB3
Look at this issue, on CVS history:
http://jira.jboss.com/jira/browse/EJBTHREE-440?page=vcs
I had to change build.xml to add the libraries on the client-path
On Tue, Feb 14, 2006 at 12:09:59PM -0600, Clebert Suconic wrote:
If you write an EJB3 remote application application, it's very likely
you will have to add cglib, asm and hibernate3 to the classpath of your
application.
This sounds extremely fat. Can this be reduced to the absolutely
needed
To: jboss-development@lists.sourceforge.net
Subject: Re: [JBoss-dev] client libraries on EJB3
On Tue, Feb 14, 2006 at 12:09:59PM -0600, Clebert Suconic wrote:
If you write an EJB3 remote application application, it's very likely
you will have to add cglib, asm and hibernate3 to the classpath
: RE: [JBoss-dev] client libraries on EJB3
IMO we need to add the whole asm, cglib and hibernate.proxy
into hibernate3-client.
These packages are required on any lazy relationship.
Clebert
---
This SF.net email is sponsored by: Splunk
Of Clebert Suconic
Sent: Wednesday, February 15, 2006 1:22 PM
To: jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] client libraries on EJB3
IMO we need to add the whole asm, cglib and hibernate.proxy
into hibernate3-client.
These packages are required on any lazy relationship
Title: Re: [JBoss-dev] client libraries on EJB3
we are not propagating
relationships across JVM boundaries.
But if you have a lazy relationship, you
need CGLIB and ASM on the client side.
So, if you don't have CGLib, ASM and
Hibernate and using a lazy relationship you will get
Title: Re: [JBoss-dev] client libraries on EJB3
Can this enhanced proxy be replacedduring
serialization to avoid this? If these classes cannot be used in a functional
manner by a client, they should not be exposed to the client. Just replace the
proxy with a wrapper around the lazy load
Title: Re: [JBoss-dev] client libraries on EJB3
Well...
I'm not sure what would happen if the lazy
relationship is filled.
I guess you would get the
ClassNotFoundException on any Lazy Relationship if hibernate.proxy is not
availble. Bill? Kabir?
I only tested without activating a Lazy
Title: Re: [JBoss-dev] client libraries on EJB3
I'm asking if we can replace the proxy with one that throws
the lazy loading exception on any method access without leaking dependencies on
the proxy related classes.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Title: Re: [JBoss-dev] client libraries on EJB3
we will need a proxy
framework anyways, right?
if we replace cglib by something else (aop,
javassist maybe) I guess it would be the same on that point, and besides it
would require some work.
From:
[EMAIL PROTECTED] on behalf of Scott M
Title: Re: [JBoss-dev] client libraries on EJB3
For the remote proxies and associated aspects yes, but
I don't want proxy stuff leaking for no good reason. A proxy that can only be
used to cause an exception to be thrown is not a good reason to introduce a new
library dependency
To: jboss-development@lists.sourceforge.net;
jboss-development@lists.sourceforge.net
Subject: RE: [JBoss-dev] client libraries on EJB3
we will need a proxy framework anyways, right?
if we replace cglib by something else (aop, javassist maybe) I
If you write an EJB3 remote application application, it's very likely
you will have to add cglib, asm and hibernate3 to the classpath of your
application.
I don't know if we already had a discussion about this, but shouldn't
these jars be under /client in our distribution.
I know we have
@lists.sourceforge.net
Subject: RE: [JBoss-dev] client libraries on EJB3
The hibernate-client.jar is being created by the ejb3 build, but should
really be done by hibernate.
Can you send me or let me know where the testcase is, so I can update
the
files that go in there?
-Original Message-
From
21 matches
Mail list logo
