you
might want to think about using the jsp _expression_ language if you can use
it.
it's
available with jstl
-----Original Message-----
From: Joseph Kesselman [mailto:[EMAIL PROTECTED]
Sent: Friday, April 04, 2003 8:15 AM
To: Liviu Casapu
Cc: [EMAIL PROTECTED]
Subject: Re: Unable to generate JSP output with Xalan -- CORRECTION
From: Joseph Kesselman [mailto:[EMAIL PROTECTED]
Sent: Friday, April 04, 2003 8:15 AM
To: Liviu Casapu
Cc: [EMAIL PROTECTED]
Subject: Re: Unable to generate JSP output with Xalan -- CORRECTION
>Is there any particular reason why we are not allowed to use elements as
>content for HTML attributes ?
That's not a concept defined in either HTML or XML. Hence, it's not a concept architected into XSLT.
You could try taking this up with the W3C's XSLT Working Group, but I think they're going to tell you that the XML Infoset says the content of an attribute is Text and therefore it's up to you to generate it as Text.
>What happens if the name of the localized
>resource itself (resName) is a variable coming from the XML document ?
Exit the xsl:text after the quote, call an xsl:value to retrieve the variable's contents as a string, start a new xsl:text to close the quotes and finish the element.
______________________________________
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"may'ron DaroQbe'chugh vaj bIrIQbej" ("Put down the squeezebox and nobody gets hurt.")
