> Reverting back to a previous tapestry snapshot or 5.0.11 (for ioc,
>>> core, and hibernate) fixes the problem. Anyone know what happened? Do
>>> I need a new approach or is this a regression bug?
>>>
>>> Thanks,
>>>
>>> J
>>>
>>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/tapestry-hibernate-breakage-in-Apr-6-5.0.12-SNAPSHOT-tp16531440p16533312.html
Sent from the Tapestry -
5.0.11 (for ioc,
> core, and hibernate) fixes the problem. Anyone know what happened? Do
> I need a new approach or is this a regression bug?
>
> Thanks,
>
> J
>
>
>
> ---------
> To unsubscribe,
The latest snapshot changed something with tapestry-ioc or tapestry-
hibernate.
I had an ApplicationInitializer in my AppModule:
public static void
contributeApplicationInitializer
(OrderedConfiguration configuration,
org.hibernat