On Wed, Nov 17, 2004 at 02:39:59PM +0100, Erik Bruchez wrote:
I have to say that I am almost as confused as you are. I would personally consider this behavior a bug, which somehow is leveraged by enter-pin-view.xsl. At the very least if we really want this behavior, we should document it clearly.
The ATM example *relies* on this behavior... I had assumed that the usual way to pass information from a validate step to the page model is via a session serializer/generator (is this correct?), until I saw the ATM example way of doing this. A way that looks very strange indeed, and as soon as you specify a model document/pipeline attribute for the page, the action output is not accessible anymore, it seems.
I would rather use the Scope generator and serializer and pass data through the _request_ (the Session generator / serializer are deprecated), rather than the session. Using the session would pollute other requests using the same session, e.g. different windows or tabs in the same web browser (the rule I follow is to _never_ use the session unless the information is really related to the actual user of the application).
http://www.orbeon.com/ois/doc/processors-generators#scope-generator http://www.orbeon.com/ois/doc/processors-serializers#scope-serializer
This will work, but maybe what we need is just an optional "action" input for the model and possibly the view, in the same way that the XForms instance can be read by the model and the view. This would be consistent and reasonably intuitive.
-Erik
------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ orbeon-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/orbeon-user
