ok, I don't understand your example "update a field", I can't imagine the
scenario... Do you mean my .JSP need to learn this Jahia event? for my part
I think my .JSP only need to access the content model. The eventlistner.jsp
seems to be a controller, for Jahia application, not for me...

Why this file is a .JSP because there is it's all the most JAVA code, why
not a servlet?

Into the Jahia Template Developer Guide, the chapter 20 "Event Listeners" is
empty, do you have a small informal documentation on this? What I need is
to get a good understanding to interaction between .JSP templates and Jahia
Application.

Philippe Vollenweider wrote:

> Hello,
> 

> The template.xml file is used to describe all templates included into a
> jar file and the embedded jar which could include java classes or the
> resources bundles. This embedded jar is deployed into
> WEB-INF/classes/jahiatemplates This file is read each time you wand to
> deploy a template set.
> 
> The evenlistner.jsp is used to listen any jahia event, like
> addContainerEngineAfterInit, addContainerEngineBeforeSave,
> afterServicesLoad, beforeContainerActivation, beforeFieldActivation,
> beforeServicesLoad, containerAdded, containerDeleted,
> containerListPropertiesSet, containerUpdated, fieldAdded, fieldDeleted,
> fieldUpdated, pageAdded, pageLoaded, pagePropertiesSet, rightsSet,
> userLoggedIn, userLoggedOut.
> So you can get any of these events and do what you want (for example
> update a field, etc.)
> 
> Philippe
> 
> At 10.11.2004 11:42, you wrote:
>>Hi,
>>
>>I was studing corporate portal templates and I saw two files which are
>>not like the others.
>>
>>eventlistner.jsp and templates.xml
>>
>>What is the goal of this files. It seems to me eventlistner is a controler
>>(into MVC paradigm), and what is templates.xml for web.xml ?
>>
>>Thanks.
> 
> -------=[ pvollenweider at jahia dot com ]=---------
> Jahia : A collaborative source CMS and Portal Server
> www.jahia.org Community and product web site
> www.jahia.com Commercial services company


Reply via email to