Still, that's not to say we couldn't find some way to fix it. Do you
know where the ACEGI code is and maybe we can try to figure out what's
it's doing?
Thanks,
Aaron
On 4/2/06, Dennis Cartier <[EMAIL PROTECTED]> wrote:
> Just to follow up on this. After scanning the ACEGI forum, I found
> that Websphere has the exact same issue with FilterToBeanProxy not
> finding the FilterChainProxy class in the classloader.
>
> So with two different app containers hitting the exact same issue, it
> would tend to make me think the fault lies in the ACEGI code rather
> than anything in Geronimo.
>
> Dennis
>
