Hi there,
I'm currently in "try to explode in unique responsibility components"
lenya-core (in svn/trunk).
I get now a lenya-repository and lenya-publication components (with many
others).
-- The problem
But they are both really linked with session concept :
- one session impl in repository (o.a.l.cms.repository.session)
- one another session impl in publication (o.a.l.c.publication.session)
- wrappers to pass from one session impl to another.
This situation create hard dependencies between repository, publication
and sessionS implementations.
And so most function signatures of repository and publication api need
session... and some functions take a repository.session and output a
publication.session (or the inverse)...
-- The solution ?
Thanks to Spring and his scope and injection management, I think we can
have a solution.
I imagine this scenario ( A --> B indicate A depend on B ):
repository-impl new-session publication-impl
| | | |
--> repository-api <-- --> publication-api <--
With this :
1) we don't have dependency between repository and publication
2) repository and publication not still stick to session
3) new-session can use the good instance of repository-impl or
publication-impl with well scoped bean injection.
-- One step further ?
On the other hand, I find that the session concept don't fit really well
with the effective session goal and usage inside lenya :
Here session help to keep the identity of the user and an "history" of
what he done, would like to do (work unit).
So I would like to rename the new-session into "user" (don't have better
idea for now), that sound to me more understandable and close to goals
and aims of this component.
WDYT about all of this ?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
