On Fri, 2004-07-30 at 04:07, Johan Wasserman - BCX - Infrastructure Services wrote: > You're right, it does render the output exactly like in your example. > Only it doesn't help if the HTML output says <bean:message key="foo"/>. > bean:message should do it's job and do the lookup for foo, that doesn't > happen. > > When I do a view source on the page I see <bean:message key="foo"/>, I > need to see "FooResult". > > Application.properties file: > ---------------------- > Foo=FooResult
My (incorrect) assumption was that you were using an XSLT transform to generate a JSP page which would be processed separately. If the XSLT results are the final output, then you need to do something like this: myPage.jsp generates myPage.xml, which is transformed by myPage.xslt , resulting in myPage.html myPage.jsp: <foo><bean:message key="foo"/></foo> myPage.xml (output of myPage.jsp) <foo>FooResult</foo> myPage.xslt <xsl:template match="foo"> <bar>the value of foo was:<xsl:value-of select="."/></bar> </xsl:template> myPage.html (the output of the transform) <bar>the value of foo was:FooResult</bar> Alternatively, you could have a static xml source, and use jsp to generate the XSLT: myPage.xml <foo><bar>Baz</bar></foo> myPage.jsp <xsl:template match="foo"> <bar>the value of foo was:<bean:message key="foo"/></bar> </xsl:template> myPage.xslt (the output of myPage.jsp) <xsl:template match="foo"> <bar>the value of foo was:FooResult</bar> </xsl:template> myPage.html (the output of the transform) <bar>the value of foo was:FooResult</bar> You could of course combine these approaches, and have both dynamic XML and dynamic XSLT, also. Since this is getting further and further away from Struts as a topic, feel free to mail me off list for more info. Let me know what your process is - where does the XSLT fit in, where does it get it's source xml, etc... -Matt --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
