I don't think it's a framework problem but Chenillekit problem. Imagine for example you are building an application with Oracle database via JDBC but you are not using the regular published JDBC interfaces that everybode else does, but some internal class that is part of the exact implementation of the JDBC oracle driver. And Oracle decides to implement it's own driver in a different way so your application will be dead. Not a problem of Oracle.
On 10/19/2010 02:24 PM, Inge Solvoll wrote: > This is a big problem for third party libraries. I already removed equanda > from my application to avoid these situations, now I'm tempted to let > chenillekit go too. I only use it to a very limited extent. It's been a > couple of months now with a rather stable 5.2, third parties should have had > plenty of time to sort out trivial compatibility issues. > > I know you guys are all volunteers, and you do a great job. This is a > framework issue too, that version bumps cause third party libs to stop > working...
smime.p7s
Description: S/MIME Cryptographic Signature
