You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "bluejoe (JIRA)" <de...@velocity.apache.org> on 2008/08/29 11:40:44 UTC

[jira] Created: (VELTOOLS-106) question on VelocityView

question on VelocityView
------------------------

                 Key: VELTOOLS-106
                 URL: https://issues.apache.org/jira/browse/VELTOOLS-106
             Project: Velocity Tools
          Issue Type: Wish
          Components: VelocityView
    Affects Versions: 2.0
         Environment: resin3.0 jdk1.5
            Reporter: bluejoe


Dear developers,

Sorry to bother you!

I am a user of VelocityTools from China, and I want to rewrite some JSP pages in Velocity template language. I have no idea whether to use VelocityViewServlet or VelocityViewTag, then I choosed VelocityViewTag, considering some JSP features, such as taglib or fragment, may be used.

I use resin as J2EE container, when I use VelocityViewTag in the page, I found the page displayed so slowly in web browser. Maybe the compilation of Velocity template requires much time, I think. So,  can you give me some advice on how to improve the speed? 

Thank you very much and expect your early reply! 

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


[jira] Resolved: (VELTOOLS-106) VelocityViewTag needs caching using the not yet released StringResourceLoader

Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
     [ https://issues.apache.org/jira/browse/VELTOOLS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nathan Bubna resolved VELTOOLS-106.
-----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.x)
                   2.0

So, i realized today that we could provide some simple, default setting caching for VelocityViewTag bodyContent, because the default static repo settings for StringResourceLoader are essentially the same on the surface in both Engine 1.5 and Engine 1.6.

So, yeah, as of revision 709355, the VelocityViewTag now caches tag bodies by default, rather than re-parsing them for every render.

I have no idea why it didn't occur to me to do this before.  I was probably just imagining the impossibility of supporting all the possibilities of 1.6's  StringResourceLoader while only requiring 1.5 for Tools 2.0.  Sorry 'bout that.

> VelocityViewTag needs caching using the not yet released StringResourceLoader
> -----------------------------------------------------------------------------
>
>                 Key: VELTOOLS-106
>                 URL: https://issues.apache.org/jira/browse/VELTOOLS-106
>             Project: Velocity Tools
>          Issue Type: Wish
>          Components: VelocityView
>    Affects Versions: 2.0
>         Environment: resin3.0 jdk1.5
>            Reporter: bluejoe
>             Fix For: 2.0
>
>
> Dear developers,
> Sorry to bother you!
> I am a user of VelocityTools from China, and I want to rewrite some JSP pages in Velocity template language. I have no idea whether to use VelocityViewServlet or VelocityViewTag, then I choosed VelocityViewTag, considering some JSP features, such as taglib or fragment, may be used.
> I use resin as J2EE container, when I use VelocityViewTag in the page, I found the page displayed so slowly in web browser. Maybe the compilation of Velocity template requires much time, I think. So,  can you give me some advice on how to improve the speed? 
> Thank you very much and expect your early reply! 

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


[jira] Commented: (VELTOOLS-106) question on VelocityView

Posted by "Claude Brisson (JIRA)" <de...@velocity.apache.org>.
    [ https://issues.apache.org/jira/browse/VELTOOLS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626933#action_12626933 ] 

Claude Brisson commented on VELTOOLS-106:
-----------------------------------------

Hi bulejoe,

Nathan did already answer your question on the user mailing list, didn't you see it?

I paste again his answer:

> yes, the VelocityViewTag does not currently do any caching of the
> template/tag body, so it must be reparsed for each render.   Once
> Velocity Engine 1.6 is released, we will be able to properly use the
> new StringResourceLoader to easily provide that caching.  until that
> time, VelocityViewTag will only perform well when it loads templates
> via a template="foo.vm" attribute, rather than having the template as
> its body.

Maybe it wasn't clear enough for you, then you should continue on the user mailing list,
this place is not meant to discuss user issues.

Still, we can maybe leave this ticket open to remember to implement this caching once
the v1.6 of the engine is out...


  Claude


> question on VelocityView
> ------------------------
>
>                 Key: VELTOOLS-106
>                 URL: https://issues.apache.org/jira/browse/VELTOOLS-106
>             Project: Velocity Tools
>          Issue Type: Wish
>          Components: VelocityView
>    Affects Versions: 2.x
>         Environment: resin3.0 jdk1.5
>            Reporter: bluejoe
>
> Dear developers,
> Sorry to bother you!
> I am a user of VelocityTools from China, and I want to rewrite some JSP pages in Velocity template language. I have no idea whether to use VelocityViewServlet or VelocityViewTag, then I choosed VelocityViewTag, considering some JSP features, such as taglib or fragment, may be used.
> I use resin as J2EE container, when I use VelocityViewTag in the page, I found the page displayed so slowly in web browser. Maybe the compilation of Velocity template requires much time, I think. So,  can you give me some advice on how to improve the speed? 
> Thank you very much and expect your early reply! 

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


[jira] Updated: (VELTOOLS-106) VelocityViewTag needs caching using the not yet released StringResourceLoader

Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
     [ https://issues.apache.org/jira/browse/VELTOOLS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nathan Bubna updated VELTOOLS-106:
----------------------------------

        Fix Version/s: 2.x
    Affects Version/s:     (was: 2.x)
                       2.0

> VelocityViewTag needs caching using the not yet released StringResourceLoader
> -----------------------------------------------------------------------------
>
>                 Key: VELTOOLS-106
>                 URL: https://issues.apache.org/jira/browse/VELTOOLS-106
>             Project: Velocity Tools
>          Issue Type: Wish
>          Components: VelocityView
>    Affects Versions: 2.0
>         Environment: resin3.0 jdk1.5
>            Reporter: bluejoe
>             Fix For: 2.x
>
>
> Dear developers,
> Sorry to bother you!
> I am a user of VelocityTools from China, and I want to rewrite some JSP pages in Velocity template language. I have no idea whether to use VelocityViewServlet or VelocityViewTag, then I choosed VelocityViewTag, considering some JSP features, such as taglib or fragment, may be used.
> I use resin as J2EE container, when I use VelocityViewTag in the page, I found the page displayed so slowly in web browser. Maybe the compilation of Velocity template requires much time, I think. So,  can you give me some advice on how to improve the speed? 
> Thank you very much and expect your early reply! 

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org


[jira] Updated: (VELTOOLS-106) VelocityViewTag needs caching using the not yet released StringResourceLoader

Posted by "Claude Brisson (JIRA)" <de...@velocity.apache.org>.
     [ https://issues.apache.org/jira/browse/VELTOOLS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claude Brisson updated VELTOOLS-106:
------------------------------------

    Affects Version/s:     (was: 2.0)
                       2.x
              Summary: VelocityViewTag needs caching using the not yet released StringResourceLoader  (was: question on VelocityView)

> VelocityViewTag needs caching using the not yet released StringResourceLoader
> -----------------------------------------------------------------------------
>
>                 Key: VELTOOLS-106
>                 URL: https://issues.apache.org/jira/browse/VELTOOLS-106
>             Project: Velocity Tools
>          Issue Type: Wish
>          Components: VelocityView
>    Affects Versions: 2.x
>         Environment: resin3.0 jdk1.5
>            Reporter: bluejoe
>
> Dear developers,
> Sorry to bother you!
> I am a user of VelocityTools from China, and I want to rewrite some JSP pages in Velocity template language. I have no idea whether to use VelocityViewServlet or VelocityViewTag, then I choosed VelocityViewTag, considering some JSP features, such as taglib or fragment, may be used.
> I use resin as J2EE container, when I use VelocityViewTag in the page, I found the page displayed so slowly in web browser. Maybe the compilation of Velocity template requires much time, I think. So,  can you give me some advice on how to improve the speed? 
> Thank you very much and expect your early reply! 

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org