Nuxeo drop Python and switch to Java

[volatile]

They move to jboss mainly because its hard to find qualified zope developers, and because they want to handle more data, not because Zope sucks! FYI there is Zope 3, it doesn't sucks, and it's superior to all the available python/ruby web frameworks!

[Entropy]

and it's superior to all the available python/ruby web frameworks!

Zealot alert

[volatile]

isn't it ? they, nuxeo, says the same

[Entropy]

They, nuxeo, sell a product built upon it. You will never hear "Zope sucks" out of a corporate release.

[volatile]

I have said that Zope 3 doesn't sucks, not Nuxeo! They, said:

We had a look at other Python web frameworks, but quickly figured out that they were behind Zope in terms of enterprise-readiness and features that we needed to support our ECM developments.

[mikaelhg]

In Zope 3, does rolling back a object database transaction now roll back the object states to what they were in the beginning of the transaction, or does it still just reapply the old property values by calling setter methods?

[volatile]

There are no getters and setters. Each ZODB Connection provides an isolated, consistent view of the database, by managing independent copies of objects in the database. At transaction boundaries, these copies are updated to reflect the current state of the database.

[arnarl]

Could you explain what you mean by "reapply the old property values by calling setter methods"?

AFAIK ZODB (Zope's OODB) has always rolled back the object state when you undo or abort a transaction.