Hello James,
I just tried out the nightly build. I have still a problem, which I have
no idea to solve it:
If I pass a parameter like
<xtags:param name="response" value="{$response}"/>
I get the follwing error message:
Error in tag library at: 'xtags': for tag 'param', property 'value' of tag
handler class 'org.apache.taglibs.xtags.xslt.ParamTag', the property value
must be a runtime expression "<%=...%>", since we cannot do an automatic
convertion from "$response" to type 'java.lang.Object'
The problem is probably the conversion from a XPath Expression to a Java
Object?
If I pass the the parameter in <%= %> Notation
<xtags:param name="response" value="<%= response %>"/>
the toString representation of the response object is taken and I get an
error that java.lang.String does not provide a encodeURL Method:
javax.xml.transform.TransformerException: java.lang.NoSuchMethodException:
For e
xtension function, could not find method
java.lang.String.encodeURL([ExpressionC
ontext,] #STRING).
Do you have any idea of how to solve this dilemma?
Thank you -- Tobias
PS: The stylesheet itself works. Just to be sure I did the transformation
directly via the javax.xml.transform.Transformer and the setParameter
Method.
"James Strachan" <[EMAIL PROTECTED]>
23.11.2001 15:23
Bitte antworten an "Tag Libraries Users List"
An: "Tag Libraries Users List" <[EMAIL PROTECTED]>
Kopie:
Thema: Re: Antwort: Re: XTags: Passing non String Parameters to a Stylesheet?
----- Original Message -----
From: "Shawn Bayern" <[EMAIL PROTECTED]>
> On Fri, 23 Nov 2001, James Strachan wrote:
>
> > Shawn, do you want to apply a similar patch to the XML tags in JSTL,
> > to allow a parameter value to be an Object? I'll do it if you like?
> > Basically Transformer.setParameter(String name, Object value) can take
> > a value of Object rather than just a String. It would need a change to
> > the param tag in JSTL to support supplying a value...
> >
> > <x:transform ...>
> > <x:param name="foo" value="$bar"/>
> > </x:transform>
>
> James & Tobias -- Thanks, this is exactly the sort of feedback that
makes
> early-access especially useful.
>
> While this change is pretty minor, it would still require a modification
> to the functional description of the tags, so I'll bounce the issue up
to
> the spec leads. The "standard" taglib (the RI) is spec-driven, so it
> shouldn't initiate the change.
Agreed.
PS - I think I just beat you to it and bouced it up just before you ;-)
James
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
