Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 10 Jan 2013 22:51:10 +0100] rev 8672
[repository sources] copy source configuration: source's __init__ modify it while config.sources() return a cached dictionary which shouldn't be modified
This causes pb since f8aa87a773b2 (though it's unclear why it hasn't been a problem before).
Closes #2521848
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 10 Jan 2013 22:50:34 +0100] rev 8671
cleanup repository connect doc: cnxtype is now deprecated / base_url has never been given that way. Follow #2521848
Aurelien Campeas <aurelien.campeas@logilab.fr> [Tue, 22 Jan 2013 18:16:20 +0100] rev 8670
prefix "tcp://" zmq uris with "zmqpickle" (closes #2574114)
* it turns "tcp://" into "zmqpickle-tcp://"
* will leave room for future non-pickling communications using zmq
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 21 Jan 2013 18:01:25 +0100] rev 8669
[db-api/configuration] simplify db-api and configuration so that all the connection information is in the repository url, closes #2521848
eg no more specific option of pyro ns host, group, etc. This also fixes broken ZMQ
sources.
Changes:
* dropped pyro-ns-host, pyro-instance-id, pyro-ns-group from client side config, in
favor of repository-uri. No migration done, supposing there is **no web-only config**
in the wild. Also stop discovering the connection method through the repo_method class
attribute of the configuration, varying according to the configuration class. This is
a first step on the way to a simpler configuration handling. Notice those pyro options
are still available for repository only / all-in-one configurations as they are needed
to configure the pyro server.
* stop telling connection method using ConnectionProperties, this is so boring. Also,
drop _cnxtype from Connection and cnxtype from Session. The former is replaced by a
is_repo_in_memory property and the later is totaly useless.
* deprecate in_memory_cnx which becomes useless, use _repo_connect instead
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 10 Jan 2013 23:05:45 +0100] rev 8668
[ldap test] ensure slapdd launch went fine and move ldapfeed setUp to parent class, as all ldap sources deal with url
Aurelien Campeas <aurelien.campeas@logilab.fr> [Thu, 10 Jan 2013 18:11:33 +0100] rev 8667
[web/uihelper,uicfg] transform uihelper functions into uicfg objects methods (closes #2543949)
Florent Cayré <florent.cayre@logilab.fr> [Mon, 21 Jan 2013 16:34:09 +0100] rev 8666
make ui configurations selectable (closes #2406609)
* introduce a new 'uicfg' registry (storing instances)
* use the relevant new APIs from lgc.registry to manage the new
registrable uicfg objects
* cw event manager useage is gone; instead thze standard registry
reloading mechanism is used
* ensure i18n commands still work (devctl)
* introduce dynamic uicfgs use whenever possible (various views), even
though sometimes the classic 'static' usage remains
Aurelien Campeas <aurelien.campeas@logilab.fr> [Thu, 10 Jan 2013 18:34:10 +0100] rev 8665
[uicfg] uicfg.py moves from web/ to web/views/ (prepares #2406609)
We are about to make uicfg selectable. Registrable / selectable views
and helpers live in web/views. Hence the move.
Backward compat is put in place. However CubicWeb imports of uicfg are
updated to the new location.
Aurelien Campeas <aurelien.campeas@logilab.fr> [Thu, 10 Jan 2013 13:03:38 +0100] rev 8664
[appobject] introduce RegistrableObject base class (prepares #2406609)
Aurelien Campeas <aurelien.campeas@logilab.fr> [Mon, 21 Jan 2013 13:55:25 +0100] rev 8663
[cwvreg] introduce lgc version 0.59 and remove unneeded method redefinition (prepares #2406609)
The new logilab.common.registry makes this moot.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 23 Nov 2012 18:27:35 +0100] rev 8662
[BFSS] mark fs_imported value as uncachable
This will finally fix the `test_bfss_fs_importing_transparency` pass again.
Regression was introduced by 4ba11607d84a
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 18 Jan 2013 18:48:15 +0100] rev 8661
[entity] add a "repo_side" parameter to `_cw_dont_cache_attribute`
This parameter (defaulting to `False`) is used to inform cubicweb that we really
really do not want to cache a value during creation or update. This will be used
by a storage that may do very specific processing on attribute values that result
in a stored value different than the provided one (e.g. BFSS `fs_importing`
mode).