On Apr 26, 2007, at 1:49 PM, David Jencks wrote:
Thanks for all the comments, I've learned a lot.
1. I have a classloader scanning strategy written and apparently
working, however it is rather slow at least in geronimo. Is anyone
interested in it, seeing as how its not an appropriate
]
Sent: Wednesday, April 25, 2007 3:55 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: More questions on runtime schema generation
The general solution to this problem lies in a crisper
definition of classloader domains in the app server. IIUC,
each app server has its own policies in terms
On Apr 25, 2007, at 12:26 PM, Patrick Linskey wrote:
However IIUC this dissects the system property
java.class.path and only parses stuff on that. This might be
reasonable for a command line tool (although I have some
doubts) but it seems to me that for any other situation a
scan of the
questions on runtime schema generation
On Apr 25, 2007, at 12:26 PM, Patrick Linskey wrote:
However IIUC this dissects the system property java.class.path and
only parses stuff on that. This might be reasonable for a command
line tool (although I have some
doubts) but it seems
The general solution to this problem lies in a crisper definition of
classloader domains in the app server. IIUC, each app server has its
own policies in terms of where various components get loaded and when.
I think we need to engage the server spec team on this, otherwise we
will end up
@incubator.apache.org
Subject: Re: More questions on runtime schema generation
The general solution to this problem lies in a crisper
definition of classloader domains in the app server. IIUC,
each app server has its own policies in terms of where
various components get loaded and when.
I think
