You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Wang Zhi <wz...@gmail.com> on 2005/11/11 09:31:01 UTC
portlet decorator deploy
i update a portlet decorator(css and .vm file) and deploy to
jetspeed-2-m4, but it not go into effect until i restart tomcat. how
to let it go into effect immediately like jetspeed-2-m3?
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: portlet decorator deploy
Posted by Wang Zhi <wz...@gmail.com>.
it go into effect immediately now,
Thanks much!
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: portlet decorator deploy
Posted by Ate Douma <at...@douma.nu>.
This is because of WEB-INF/velocity.properties:
webapp.resource.loader.cache = true
which is done for performance improvements.
Wang Zhi said:
> i update a portlet decorator(css and .vm file) and deploy to
> jetspeed-2-m4, but it not go into effect until i restart tomcat. how
> to let it go into effect immediately like jetspeed-2-m3?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org