Andreas Hartmann schrieb:
J. Wolfgang Kaltz wrote:
(...)
AFAIK BXE doesn't allow to change the BX_xmlfile parameter after each
"save" action, which would be necessary to pass the continuation ID
from request to request.
A workaround could be to add the continuation ID to the session.
+1,
I don't think that would be a workaround, but a feature (see below)
Another option is to write the XML to a temporary source and copy this
temp source to the original source when the user exits BXE.
If we would do it like that, would that mean that a editing in Lenya is
a 3-step process instead of a 2-step process ? I guess that would be ok
and generalizable to all editors
To be honest, I don't really understand the new locking / checking out
mechanisms on the objects (talking about objects as in instances of
classes, not talking about the rc checkout here).
I started some docs, feel free to add your questions / comments:
http://wiki.apache.org/lenya/OverviewRepository
Yes, thx a lot, it is an important theme to document.
(...)
- (design question): would it not be easier to explicitly separate
read and potential write accesses ? i.e. reading could be possible
without a unit of work,
It is possible without a unit of work ... what do you mean?
OK, maybe I simply misunderstood ... I need to delve into document
access again (that was the starting point in the internals of my long
round trip to resource type to metadata to creator).
Regarding editor & continuations,
I am +1 to store the continuation IDs in the session instead of in
request parameters. This is IMO the only way we will able to provide a
generic edit interface.
I see in cocoon.xconf there is a <continuations-manager> entry, with a
parameter session-bound-continuations="false"
Reading the Cocoon docs
http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/components/flow/ContinuationsManagerImpl.html
this should be set to "true" for Web apps in any case (for security
reasons).
IIUC the only pb with setting this to true is that all accesses to Lenya
continuations would then require to live inside a session. I guess for
current needs this is in fact what we want (i.e. a feature, not a bug).
WDYT ?
--
Wolfgang
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
