This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: xml & forms revisited
Hi Eric,
Very cool. Probably it is the best possible 'pure'
and 'clean' way to get the environment passed to
XSLT without dirty tricks.
PXSLServlet ( dirty trick by definition ) solves this
problem in another way, attaching the environment
variables into XML *source* document.
That means in the stylesheet we have only
<xsl:value-of select="/request/variable"/>
or something like that. ( It is flexible - S2X Template
determines the actual names for 'request' and 'variable'. )
Of course, that's because in PXSLServlet's universe
there is "S2X magician", responsiple for grabbing
XML data from the outher space ( mostly
SQL database), and because environment of http request
is "yet-another-data-source" - those data are pulled
into source XML by S2X template and do not go to the
stylesheet. "stylesheet is about processing, S2X template
is about the dataflow ( XML-to-process )".
In the absence of S2X 'magician' there is no way to
compose the desired source XML on the fly, so
your solution is perfect from my point of view.
Just wanted to explain what I meant yesterday saying
that "in PXSLServlet, XML is about the data and XSL is about
the processing"
- in your universe some data are jumping into the text of stylesheet
- in PXSLServlet universe - data are jumping into XML source, stylesheet
assumes the data are already in the XML-document-to-be-processed
( the stylesheet tries to be 'ideal' ;-)
My universe has a lot of other problems of course ;-) Also your 'jumping'
of data into the stylesheet is very compact - just a couple of lines.
That means I realy don't think my universe is in any way 'better' than
your's - just wanted to show some other point of view ( BTW, the PXSLServlet's
tactics with the environment variables explained above is just a side-effect of
SQL -> XML mapping).
I realy enjoyed your code.
Rgds.Paul.
>
> It's not that simple with XSLT ;=)
>
> Having said this, you'll find on our web an example showing how one can,
> with XT, handle part of the request context as a tree fragment.
>
> http://downloads.dyomedea.com/java/examples/xslservlet/result-tree/
>
> Hope this helps.
>
> Eric
>
> "Kari M. Scott" wrote:
> >
> > First, thanks to everyone who has patiently answered my newbie xml
> > questions.
> >
> > Today's question concerns capturing form submit results in another xml
> > file for another sql query. More specifically, when I submit a form, I
> > designate results.xml as the action. In results.xml, however, I haven't a
> > clue as to how I can grab the form values. What I need is similar to this
> > line in Perl:
> >
> > $VALUE = $in{'VALUE'};
> >
> > Any syntax examples would be greaty appreciated!
> >
> > Thanks,
> > -Kari
> >
> > Kari M. Scott
> > Berbee
> > 5520 Research Park Drive
> > Madison, WI 53711-5377
> > kmscott@berbee.com
> > 608.288.3000 ext. 1223
> > 608.298.1223 direct dial
> > 608.288.3037 fax
> >
> > Berbee...putting the E in business
> >
> > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
> --
> ------------------------------------------------------------------------
> Eric van der Vlist Dyomedea
>
> http://www.dyomedea.com http://www.ducotede.com
> ------------------------------------------------------------------------
>
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list