Hi Aaron,
I'm happy to cut a 1.2.2 TranQL release tomorrow night. However, and as
pointed out by Manu, there was also an OpenEJB impact. So, it seems that
we also need to re-cut an OpenEJB release. So far, I have checked in the
fix to trunk and I will port the fix to the v2_0 branch if we
Hi Manu,
Thanks for your debugging! This was a bug in IdentityDefinerBuilder,
which was wrongly trying to identify a compound PK based on the number
of primary key fields.
This is now fixed.
I will create a JIRA to track this issue tomorrow as it seems that JIRA
is down tonight.
Thanks,
Hi Gianny
Great to know its fixed. Will try it out after building geronimo from source.
Thanks
ManuOn 12/13/05, Gianny Damour [EMAIL PROTECTED] wrote:
Hi Manu,Thanks for your debugging! This was a bug in IdentityDefinerBuilder,which was wrongly trying to identify a compound PK based on the
Gianny,
Did the fix go into TranQL? Geronimo 1.0 is not using a TranQL
snapshot right now, so someone would need to cut a new TranQL release
for us to get the fix into Geronimo 1.0.
Thanks,
Aaron
On 12/13/05, Gianny Damour [EMAIL PROTECTED] wrote:
Hi Manu,
Thanks for your debugging!
Hi Manu,
This was a simple TranQL fix. So, you simply need to build TranQL and
drop it in your repo (you do not need a full rebuild of Geronimo).
Thanks,
Gianny
Manu George wrote:
Hi Gianny
Great to know its fixed. Will try it out after building geronimo from
source.
Thanks
Manu
On
Hi Gianny,
I get it.But the problem is if I put this jar in the repo
of my existing Geronimo Instance it fails to start due to
de-serialisation problems.
org.apache.geronimo.kernel.config.InvalidConfigException: Could not extract gbean data from configuation
at
Hi Gianny,
I have done all that you mentioned. I am still getting the error.I have
replicated the issue in a simple EJB,the example CMP in Ed Roman's book Mastering EJB. I am attaching the stack trace
and the plans below
17:02:05,211 WARN [SystemExceptionInterceptor] Product
