jakarta-taglibs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eduardo Pelegri-Llopart <Eduardo.Pelegrillop...@eng.sun.com>
Subject Re: [Enhancement] XSL Taglib
Date Mon, 18 Dec 2000 21:00:13 GMT
I guess I'd go with the some variation of the second so you can reuse
the concept in other tags later on.

BTW, I am assuming your second looks like:

 <util:params name="...">
   <util:param> ...
 </util:params>

with "util:param" instead of "param"

or maybe even
 <util:params name="....">
   <util:param name="xxx" value="...."/>
   <....
 </util:params>

Some of the core tags use your 1st approach, but we didn't want to add
any more concepts to the core tags in 1.{0,1,2} and instead left new
concepts for futher experimentation elsewhere.

	- eduard/o

Luca Orlandi wrote:
> 
> I've greatly appreciated the xsl taglib (I've developed myself something
> similar using a simple servlet hierarchy ) and I would like to enhance it
> introducing the support for parametric xsl.
> I'm in doubt about the best interface for it:
> 
> <xsl:apply ...>
>         <xsl:params>
>                 <param name="xxx">value1</param>
>                 ...
>         </xsl:params>
> </xsl:apply>
> 
> This could be a solution but somehow collides with the "nested xml" syntax:
> 
> <xsl:apply xsl="/xml/employeeList.xsl">
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <employees>
>   <employee id="123">
>     <first-name>John</first-name>
>     <last-name>Doe</last-name>
>     <telephone>800-555-1212</telephone>
>   </employee>
> </employees>
> </xsl:apply>
> 
> So a better solution could be forcing the uso of a "parameter bean"
> 
> <xsl:params name="mypar">
>         <param name="xxx">value1</param>
>         ...
> </xsl:params>
> 
> Tha bean can then countain a hash of params to be used prior to process-ing
> the XSL+XML.
> 
> Any suggestions?
> 
> ---
> Luca Orlandi  - Inferentia Spa MI (I)
> Phone: +39 0259928451 - Fax: +39 02 59928221

Mime
View raw message