On 07/02/2010 05:31 PM, Jan Provaznik wrote: > On 07/02/2010 08:23 AM, Jan Provaznik wrote: >> On 07/01/2010 07:17 PM, Tomas Sedovic wrote: >>> Hey everyone, >>> >>> The current Core and Aggregator versions are not working with each >>> other. I started looking at it, but couldn't finish it today. Since I >>> won't get to it before Wednesday July 7, here's what I found in case >>> anybody wants to pick it up. >>> >>> If not, I'll resume working on it on Wednesday. >>> >> >> Hi, >> great work. I'll look on compatibility issues today and report >> a progress (if any) to this thread this evening. >> >> Jan > > Some notes about issues I found: > major problem with new client lib is conflict with names of some > methods/classes. > > Client overrides some rails methods like classify, camelize, > singularize,... I suggest to wrap it by method_defined?. Attached patch > replaces Tomas core patch (singularize method rename). > > Unfortunately another problem is class names conflict. > Client dynamically adds classes (like HardwareProfile), which conflict > with our model names. But I didn't figure out why, code in client seems > to be correct on first look (see define_class method at the end) - it > creates classes in DeltaCloud module. But in fact it overrides > model class. Provider is then created, but hardware profiles properties > are not saved. > > I'll discuss it with Michal next Wednesday. > > Jan >
I sent patch in another thread (subject is "Core and Aggregator compatibility" too). Jan _______________________________________________ deltacloud-devel mailing list [email protected] https://fedorahosted.org/mailman/listinfo/deltacloud-devel
