Re, During my code reading, it's seems clear to me that repository is a singleton : one unique instance during all the app live.
For publication, this seems pretty much unclear. As I understand, there is a publication manager that create an instance of publication class for each publication in lenya, and each of this instance keep alive. If that true (?), What about the spring scope ? I first think about the prototype scope. But in fact, with this scope a new instance will be created at each call... that we don't want (and this is not the now implemented way). We want a unique instance for each publication during all the application live. So I think about spring bean like this : "o.a.l.publication/publication_id." This bean have to be created dynamically (not write down in an xml configuration file), in order to be able to add publications without restart and xml bean configuration. The publication manager will be responsible for create such bean...I don't know really how (what will be the code ?), but I fell that spring will allow that ! :) Open to comment. ++ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lenya.apache.org For additional commands, e-mail: dev-h...@lenya.apache.org
