Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Date: Fri, 27 Feb 2004 16:17:47 -0500
To: Bertrand Delacretaz <bdelacretaz@apache.org>
Cc: dev@cocoon.apache.org
Subject: Re: [RT] Cocoon Input Model
Message-ID: <20040227211747.GD9643@maribor.izzy.net>
References: <403CC415.2020302@nada.kth.se>
	<16A20B3A-67B2-11D8-8E8F-000393CFE402@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <16A20B3A-67B2-11D8-8E8F-000393CFE402@apache.org>
User-Agent: Mutt/1.4.1i
From: Alan <alan-cocoon@engrm.com>
Mail-Followup-To: bdelacretaz@apache.org,
	dev@cocoon.apache.org

* Bertrand Delacretaz <bdelacretaz@apache.org> [2004-02-25 16:46]:
> Le Mercredi, 25 f?v 2004, ? 16:49 Europe/Zurich, Daniel Fagerstrom a 
> ?crit :
> 
> <snip-plenty-of-good-stuff/>
> 
> >...But in many cases using SAX based XML as in pipelines is not enough 
> >we need a data structure i.e. DOM. This leads to flowscript components 
> >that reads some input format to DOM and from DOM to some output format 
> >or some store. We also will need flowscript components that go from 
> >DOM to DOM...
> 
> Just trying to understand from a practical point of view, does this 
> mean something like
> 
> <map:generate type="request"/>
> <map:transform src="prepare-query-for-user-preferences"/>
> <map:transform type="sql"/>
> <map:call function="myFlow()" dom-input="domIn"/>
> 
> At which point myFlow() is called with a "domIn" variable containing 
> the current pipeline XML as a DOM?
> 
> And maybe the opposite:
> <map:call function="myFlow()" dom-output="domOut"/>
> meaning that myFlow() is expected to write a DOM structure to domOut 
> for insertion in the pipeline?

(Note that I still have a lot to learn about sitemaps. My examples
    might have some glaring conceptual errors.)

As long as we are talking in sitemap:

<map:match pattern="registration/login-info-submit">

  <map:generate type="c-forms" src="form/registration.xml"/>

  <map:validate type="relax-ng" src="relax-ng/registration.xml"
                                failure="registration-error"/>

  <map:muliplex failure="registration-error"
                success="registration-choose-lists">
    <map:channel>
      <map:transform src="stylesheets/registration-ldap.xslt"/>
      <map:store type="ldap" dest="(some sort of ldap url)"/>
    </map:channel>
    <map:channel>
      <map:transform src="stylesheets/xupdate/registration-momento.xslt"/>
      <map:store type="momento" dest="momento/e-mail-service.mx"/>
    </map:channel>
    <map:channel>
      <map:transform src="stylesheets/xupdate/registration-session.xslt"/>
      <map:store type="session"/>
    </map:channel>
  </map:multiplex>

</map:match>

<map:match pattern="registration-choose-lists">
  <map:aggregate element="page">
    <map:part src="momento/registration-chose-lists.xslt"/>
    <map:part src="session:/"/>
  </map:aggregate>
  <map:transform src="stylesheets/document-to-html.xslt"/>
  <map:serialize type="html"/>
</map:match>

Now that I look at the above, I see that I really want to be able to
    do something like this from within stylesheets.

    <xsl:param name="user-name"
               select="document('session://')/session/user-name"/>

-- 
Alan / alan@engrm.com / http://engrm.com/
    aim/yim: alanengrm - icq: 228631855 - msn: alanengrm@hotmail.com