click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Malcolm Edgar (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CLK-606) Remove Click core's dependency on Velocity
Date Tue, 16 Mar 2010 19:44:27 GMT

     [ https://issues.apache.org/jira/browse/CLK-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Malcolm Edgar updated CLK-606:
------------------------------

    Comment: was deleted

(was: >If Babelfish did a good job: get well soon! If not: translation needed... 
Yes, It did.
But May I recommend  http://www.translate.ru

Example:

Since March, 9th I will spend some days in hospital where I can not
To check mail and to respond to letters.

As soon as for me possibility will be presented, I will respond at once to your letter.

Thanks!

===I think a bit better!

My comment above is just Gmail's Vacation responder.
Please, somebody, remove it...

I am still in hospital, so Vacation responder can do it again ;-(
)

> Remove Click core's dependency on Velocity
> ------------------------------------------
>
>                 Key: CLK-606
>                 URL: https://issues.apache.org/jira/browse/CLK-606
>             Project: Click
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 2.1.0, 2.1.0 RC1
>         Environment: click-nodeps-2.1.0-RC1-incubating.jar , click-extras-2.1.0-RC1-incubating.jar,
ognl-2.6.9.jar, freemarket2.3.16.jar
>            Reporter: Andrey Rybin
>            Assignee: Malcolm Edgar
>            Priority: Minor
>             Fix For: 2.2.0
>
>
> I use freemarker and dependencies in separate jars. 
> I haven't 'velocity' in my classpath.
> So I found bug: common click core depends on Velocity.
> Namely:
> org.apache.click.ClickServlet.java
> org.apache.click.util.ErrorReport.java
> They both depend on
> org.apache.velocity.exception.ParseErrorException   (search:
> instanceof ParseErrorException)
> and require Velocity be present in classpath even if freemarker are used.
> My workaround:
> I made fake public class ParseErrorException extends Exception {}.
> But you can make generic solution, for example:
> TemplateService
> + boolean isParseErrorException (Exception e)
> + Map<String, Object> describeParseErrorException (Exception e)
> or your own ClickTemplateException to wrap low level velocity/freemarker exceptions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message