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

Daniel Sun updated GROOVY-10715:
--------------------------------
    Description: 
{{StreamingTemplateEngine}} creates a new ClassLoader instance each time it 
tries to create a template instance. As a result, we can not reuse the class 
cache of {{GroovyClassLoader}} and save the time of compilation.

{{GStringTemplateEngine}} supports option 
{{groovy.GStringTemplateEngine.reuseClassLoader}} to reuse 
{{{}GroovyClassLoader{}}}, we can do the same thing for 
{{{}StreamingTemplateEngine{}}}, e.g. 
{{groovy.StreamingTemplateEngine.reuseClassLoader}}

  was:
{{StreamingTemplateEngine}} creates a new ClassLoader instance each time it 
tries to create a template instance. As a result, we can not reuse the class 
cache of {{GroovyClassLoader}} and save the time of compilation.

{{GStringTemplateEngine}} supports option 
{{groovy.GStringTemplateEngine.reuseClassLoader}} to reuse 
{{GroovyClassLoader}}, we do the same thing for {{StreamingTemplateEngine}}, 
e.g. {{groovy.StreamingTemplateEngine.reuseClassLoader}}


> Make StreamingTemplateEngine support reusing ClassLoader
> --------------------------------------------------------
>
>                 Key: GROOVY-10715
>                 URL: https://issues.apache.org/jira/browse/GROOVY-10715
>             Project: Groovy
>          Issue Type: Improvement
>            Reporter: Daniel Sun
>            Priority: Major
>             Fix For: 5.0.0-alpha-1, 4.0.5
>
>
> {{StreamingTemplateEngine}} creates a new ClassLoader instance each time it 
> tries to create a template instance. As a result, we can not reuse the class 
> cache of {{GroovyClassLoader}} and save the time of compilation.
> {{GStringTemplateEngine}} supports option 
> {{groovy.GStringTemplateEngine.reuseClassLoader}} to reuse 
> {{{}GroovyClassLoader{}}}, we can do the same thing for 
> {{{}StreamingTemplateEngine{}}}, e.g. 
> {{groovy.StreamingTemplateEngine.reuseClassLoader}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to