It is very simple, cglib must define proxy in
application classloader (the same as domain class
loader), it doe's not mater how you find this
clasloader, but it must be the same for proxy and for
domain class (delegation to package visibility method
throws IllegalAccessError if classes are in diff
On Jun 16, 2005, at 8:31 PM, Emmanuel Bernard wrote:
This complexify the annotations (user experience, not the binding
code), so I'm wondering whether I should allow this kind of
structure or not.
Also check: http://opensource.atlassian.com/projects/hibernate/browse/
HHH-539
Yep, used i
Title: [Hibernate] Mixing and
yes - i remember some
mapping support case that had this.
Just cant remember the case ;)
/max
From:
[EMAIL PROTECTED] on behalf of Emmanuel
BernardSent: Thu 16-06-2005 20:31To:
hibernate-devel@lists.sourceforge.netSubject: [Hibernate] Mixing
and
Hi
Hi guys,
Have you ever seen a mix and match between formulas and columns in a
mapping.
foo2 + bar
This complexify the annotations (user experience, not the binding code),
so I'm wondering whether I should allow this kind of structure or not.
Emmanuel
The class loading structure of a j2ee app is vendor specific. For any
given component the correct starting point is the thread context class
loader. That class loader should have visibility into parent class
loaders as needed.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMA
--- Max Rydahl Andersen <[EMAIL PROTECTED]>
wrote:
>
>
> > I do not think it is possible to find the the best
> way
> > for this stuff, but we expected hibernate (and
> cglib)
> > classes will be in the same or in the parent
> > classloader (asumption is based on j2ee container
> > class loadi
I do not think it is possible to find the the best way
for this stuff, but we expected hibernate (and cglib)
classes will be in the same or in the parent
classloader (asumption is based on j2ee container
class loading stuff). It must be better to use this
asumption, it has more chances to be ma
I do not think it is possible to find the the best way
for this stuff, but we expected hibernate (and cglib)
classes will be in the same or in the parent
classloader (asumption is based on j2ee container
class loading stuff). It must be better to use this
asumption, it has more chances to be mainta