You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by David Blevins <da...@visi.com> on 2007/04/24 00:14:54 UTC
Re: svn commit: r530626 - in /incubator/openejb/trunk/openejb3: container/openejb-core/src/main/java/org/apache/openejb/assembler/classic/ container/openejb-core/src/main/java/org/apache/openejb/config/ container/openejb-core/src/main/java/org/apache/opene...
Ok, this is definitely fixed now and tested. You won't need to
update OpenEJB if you have yesterday's fix, but you will need to
update your G tree to get my last two commits.
-David
On Apr 23, 2007, at 6:59 AM, Kevan Miller wrote:
>
> On Apr 23, 2007, at 9:05 AM, Rick McGuire wrote:
>
>> Unfortunately, I believe it was the 10PM fix that caused the TCK
>> breakages. The problems first appeared for me after I rebuilt
>> saturday morning, and are still there this morning.
>
> The 10 PM fix that David is referring to is Geronimo RC 531336
> which was committed at 10PM left-coast time last night (Sunday) or
> 1 AM right-coast time. Unfortunately, RC 531336 doesn't fix the
> problem. David did you verify the fix by testing?
>
> Rick,
> I think you'll find that if you revert 530626 in OpenEJB, the
> problem goes away. You'd probably have to revert 531336 from
> Geronimo, also.
>
> --kevan
>
>
Re: svn commit: r530626 - in /incubator/openejb/trunk/openejb3: container/openejb-core/src/main/java/org/apache/openejb/assembler/classic/
container/openejb-core/src/main/java/org/apache/openejb/config/ container/openejb-core/src/main/java/org/apache/opene...
Posted by Rick McGuire <ri...@gmail.com>.
David Blevins wrote:
> Ok, this is definitely fixed now and tested. You won't need to update
> OpenEJB if you have yesterday's fix, but you will need to update your
> G tree to get my last two commits.
My problems with the naming exceptions finally appear to be fixed.
Rick
>
> -David
>
> On Apr 23, 2007, at 6:59 AM, Kevan Miller wrote:
>
>>
>> On Apr 23, 2007, at 9:05 AM, Rick McGuire wrote:
>>
>>> Unfortunately, I believe it was the 10PM fix that caused the TCK
>>> breakages. The problems first appeared for me after I rebuilt
>>> saturday morning, and are still there this morning.
>>
>> The 10 PM fix that David is referring to is Geronimo RC 531336 which
>> was committed at 10PM left-coast time last night (Sunday) or 1 AM
>> right-coast time. Unfortunately, RC 531336 doesn't fix the problem.
>> David did you verify the fix by testing?
>>
>> Rick,
>> I think you'll find that if you revert 530626 in OpenEJB, the problem
>> goes away. You'd probably have to revert 531336 from Geronimo, also.
>>
>> --kevan
>>
>>
>
>
Re: svn commit: r530626 - in /incubator/openejb/trunk/openejb3: container/openejb-core/src/main/java/org/apache/openejb/assembler/classic/ container/openejb-core/src/main/java/org/apache/openejb/config/ container/openejb-core/src/main/java/org/apache/opene...
Posted by David Blevins <da...@visi.com>.
On Apr 23, 2007, at 8:40 PM, Kevan Miller wrote:
>
> On Apr 23, 2007, at 6:14 PM, David Blevins wrote:
>
>> Ok, this is definitely fixed now and tested. You won't need to
>> update OpenEJB if you have yesterday's fix, but you will need to
>> update your G tree to get my last two commits.
>
> Unfortunately, looks like we're still broken. Rick reported that he
> was still seeing errors, also...
>
Looks like my fix worked for business interfaces but not old-style
remote/home. I've built/tested/checked-in another patch.
The tck smoke tests don't all pass for me due to a seemingly "setup"
related issue -- more on the tck list about that.
-David
Re: svn commit: r530626 - in /incubator/openejb/trunk/openejb3: container/openejb-core/src/main/java/org/apache/openejb/assembler/classic/ container/openejb-core/src/main/java/org/apache/openejb/config/ container/openejb-core/src/main/java/org/apache/opene...
Posted by Kevan Miller <ke...@gmail.com>.
On Apr 23, 2007, at 6:14 PM, David Blevins wrote:
> Ok, this is definitely fixed now and tested. You won't need to
> update OpenEJB if you have yesterday's fix, but you will need to
> update your G tree to get my last two commits.
Unfortunately, looks like we're still broken. Rick reported that he
was still seeing errors, also...
--kevan