geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder" <>
Subject Re: Builders and jpa
Date Thu, 02 Nov 2006 20:15:05 GMT
Instead of leaving it up to GBeans to handle, do you think we should
just put a hook into the Configuration where you can specify byte code
transformers that it will apply to the Configuration ClassLoader?  Now
that the transformer API is there, I'm surmising that JPA may not be
the only area where this specific issue may crop up.


On 11/2/06, David Jencks <> wrote:
> I'm working on support for runtime class enhancement for jpa and have
> run into a gbean start order issue.
> The PersistenceProvider implementation class can install a byte code
> transformer that will enhance the classes used in the app for jpa
> PersistenceCapable.  This needs to be done before any application
> classes are loaded.  I think the gbean that starts the
> PersistenceProvider needs to be in the same configuration as the app,
> so I think it needs to be arranged that that gbean starts more or
> less first.
> Dain suggested that we could implement this by giving GBeanData a
> priority order and starting them consistent with the priority order.
> The dependencies will still override the priority order but this will
> provide easier hints about the desired start order.  GBeanInfo can
> include a default priority order.  We can eventually let you set the
> priority order in a gbean plan.
> I've opened GERONIMO-2541 to track this.

View raw message