Hi All, After analyzing the code of the CassandraPersistenceManager, Angelo and I discussed the existence of the ColumnFamilyAvailable service. This service is instantiated automatically when a certain ColumnFamily is available and some bundle wants to define a service dependency on its availability. This could be improved however, similar to the keyspace approach already used for the CassandraPersistenceManager. A CassandraPersistenceManager instance should not only exist per keyspace but also per set of ColumnFamily's (the ColumnFamily's available in that keyspace). So each keyspace will have one associated CassandraPersistenceManager, with service properties that hold the keyspace and all ColumnFamily's contained by it. Service dependencies can then be defined on a CassandraPersistenceManager for not only a certain keyspace but also for one or more ColumnFamily's. This would be a better approach. Anyone that does not agree?
Regards, Ivo and Angelo GX | Ivo Ladage-van Doorn | Product Architect | Wijchenseweg 111 | 6538 SW Nijmegen | The Netherlands | T +31(0)24 - 388 82 61 | F +31(0)24 - 388 86 21 | ivo.ladage-vandoorn at gxsoftware.com<mailto:ivo.ladage-vandoorn at gxsoftware.com> | www.gxsoftware.com<http://www.gxsoftware.com> | twitter.com/GXSoftware<http://twitter.com/GXSoftware> -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.amdatu.org/pipermail/amdatu-developers/attachments/20101008/ac58333f/attachment.html
