[Resin-interest] Error Handling on Per Directory Basis?
I've got a sub folder under a main folder that handles a mobile version of our site. In resin.conf I've got For the main site, but what I need to do is have a different location for the mobile site: (something like) In apache I'd put it in a tag or put a line in an apache .htaccess file in that folder, but that won't work here. Is there an equivalent tag or method for Resin? Thanks in advance! (PS - running resin 2.1.4 - yeah I know, it's old, but it works great!) -- View this message in context: http://www.nabble.com/Error-Handling-on-Per-Directory-Basis--tp24855159p24855159.html Sent from the Resin mailing list archive at Nabble.com. ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] Non-interpreted EL expressions?
On Aug 6, 2009, at 2:13 AM, Mattias Jiderhamn wrote:
> Is there a way to make Resin not try interpreting EL expressions in
> JSP
> pages (while still using fast jstl)?
>
> We have custom tags with string attributes which are evaluated as EL
> expressions using the Apache Taglibs implementation. After updating to
> 4.0, Resin refuses to treat these attributes as Strings.
I've added a bug report and will need to check on that. Some of the
Resin 4.0 was changed to pass the JSP TCK, and that looks like one of
the cases we updated.
But taglibs really shouldn't be evaluating EL itself any more, since
EL is integrated with JSP. If you need a deferred expression, you
should be using javax.servlet.jsp.el.ValueExpression as the attribute
parameter type.
-- Scott
>
> Example:
>> com.caucho.jsp.JspLineParseException: /html/partners/
>> partner_addressEdit.jsp:30: EL expression '$
>> {defaultAddress.address}' is only allowed for attributes with
>> rtexprvalue='true'.
>>
>> ...
>> 30:
>> ...
>>
>> at com.caucho.jsp.java.JspNode.error(JspNode.java:1883)
>> at com.caucho.jsp.java.JspNode.error(JspNode.java:1872)
>> at com.caucho.jsp.java.JspNode.generateParameterValue(JspNode.java:
>> 1292)
>> ...
>>
>
> When adding true to the .tld, Resin will
> evaluate the expression and pass the String value of the result as the
> attribute of the tag. The tag will then try to evaluate this String
> value as if it was an EL expression (using the Apache) implementation,
> which of course does not give the expected result.
>
> Do we have to change the implementation of all the tags to use
> com.caucho.el.Expr instead, or is there another way?
>
> --
>
>
>
>
>
> ___
> resin-interest mailing list
> resin-interest@caucho.com
> http://maillist.caucho.com/mailman/listinfo/resin-interest
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] Non-interpreted EL expressions?
Is there a way to make Resin not try interpreting EL expressions in JSP
pages (while still using fast jstl)?
We have custom tags with string attributes which are evaluated as EL
expressions using the Apache Taglibs implementation. After updating to
4.0, Resin refuses to treat these attributes as Strings.
Example:
> com.caucho.jsp.JspLineParseException:
> /html/partners/partner_addressEdit.jsp:30: EL expression
> '${defaultAddress.address}' is only allowed for attributes with
> rtexprvalue='true'.
>
> ...
> 30:
> ...
>
> at com.caucho.jsp.java.JspNode.error(JspNode.java:1883)
> at com.caucho.jsp.java.JspNode.error(JspNode.java:1872)
> at com.caucho.jsp.java.JspNode.generateParameterValue(JspNode.java:1292)
> ...
>
When adding true to the .tld, Resin will
evaluate the expression and pass the String value of the result as the
attribute of the tag. The tag will then try to evaluate this String
value as if it was an EL expression (using the Apache) implementation,
which of course does not give the expected result.
Do we have to change the implementation of all the tags to use
com.caucho.el.Expr instead, or is there another way?
--
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
