That means that both of the generic catch clauses in there are not
quite right. I'll refix both of them.

On Fri, May 23, 2008 at 4:46 PM, Eoghan Glynn <[EMAIL PROTECTED]> wrote:
>
> Benson Margulies wrote:
>>
>> Fix committed on trunk.
>>
>
>
> Thanks Benson, I just picked up your change.
>
> Slight tweak required, as the catch clause on Exception that you added
> around the factory.setBuilder() call doesn't catch AbstractMethodError.
>
> But switching to a more generic catch Throwable and I'm back in business,
> the problematic test no longer blows up :)
>
> Thanks again!
>
> /Eoghan
>
>
>> On Fri, May 23, 2008 at 4:23 PM, Benson Margulies <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> Hmm. Bug still there. I'll make a fix.
>>>
>>> On Fri, May 23, 2008 at 4:21 PM, Benson Margulies <[EMAIL PROTECTED]>
>>> wrote:
>>>>
>>>> Are you sure you got this on the trunk? The setFeature error is a
>>>> dependency on a recent Xerces that Dan and I fixed up some weeks ago.
>>>> It's not related to XmlSchema or Spring.
>>>>
>
> ----------------------------
> IONA Technologies PLC (registered in Ireland)
> Registered Number: 171387
> Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
>

Reply via email to