>- fix NotSerializable Exceptions If this is related to NestableException not implementing Serializable, I know that the commons-lang project has made this change, so a fix here should be as easy as including the most recent version of commons-lang. >- make compression optional I need to make this change, and I would prefer do some useful work than give in to base instinct and eviscerate -- unlike some superpowers that I am familiar with. If you can check something in, or send me changes, I will be happy to do this work. It will also give me head start finer grained cache control and useServer on a repository basis... >- implement compression for all three servers (Socket, Server EJB) >- implement all currently unimplemented PB methods for C/S mode >- fix all other upcoming problems so that C/S mode runs again without >fialures and errors. > -----Urspr�ngliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] > Gesendet: Montag, 14. Oktober 2002 13:30 > An: OJB Users List > Betreff: Antwort: AW: proxy collections in client / server mode > > > ok. for now, i will disable collection proxies, because > without them, it > seems to work. maybe you can specify what has to be done, so > maybe i could > do some fixes. > > juergen > > > > Hi J�rgen, > > If I remember correctly, I did a full regression test for the > C/S mode > with > 0.9.4. There had been no errors or failures then. (At that time proxy > collectiosn were already integrated.) > > But since the 0.9.5 refactoring there are several problems > with C/S mode. > I'm currently working on a fix. Currently things look very > ugly and I have > no idea how long it will take to fix these issues. > > cheers, > Thomas > > > -----Urspr�ngliche Nachricht----- > > Von: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]] > > Gesendet: Montag, 14. Oktober 2002 12:35 > > An: [EMAIL PROTECTED] > > Betreff: proxy collections in client / server mode > > > > > > hi! > > are proxy collections tested in client /server ? since we use > > this feature > > (proxy collections), we have lots of troubles on the server > > side. i get > > lots of NPE's in PersistenceBrokerImpl, e.g. calling method > > close(), but > > connectionManager is null. also in method > > > > private ManageableCollection getCollectionByQuery(Class > > collectionClass, > > Class itemClass, Query query) > > throws ClassNotPersistenceCapableException, > > PersistenceBrokerException > > i got a npe because descriptorRepository is null. i did a logging > > message, that was invoked when the PB isClosed(), and this > > message was > > printed. so is it legal, to do anything on a closed > > PersistenceBroker? is > > there a bug? > > > > juergen > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > >
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
