[ 
http://issues.apache.org/jira/browse/JS2-190?page=comments#action_12413055 ] 

Ate Douma commented on JS2-190:
-------------------------------

I've written a implementation for this using a background monitor thread, which 
will check web.xml, portlet.xml and (if available) jetspeed-portlet.xml for 
changes.
If changes are found, the portlet application will be unregistered and 
subsequently re-registered.
Furthermore, if the portlet application cannot be loaded because of errors in 
the xml definitions, the monitor thread will keep on checking for changes.
Thus, when the errors are corrected, the portlet application will automatically 
be registered (again).

The implementation is contained within the PortletApplicationManager which now 
has a new property, descriptorChangeMonitorInterval, through which you can
configure the interval (in seconds) for the monitor to check for changes. The 
default interval is 10 seconds, but you can disable the monitor all together by
specifying a value <= 0.

As the PortletApplicationManager needs to startup the monitor *after* it is 
created, it now requires the init-method "start" (as well as the destroy-method 
"stop") to be defined in the deployment.xml assembly configuration.
Warning: This is a new *requirement*. Failing to do so will prevent portlet 
applications being registered !!!

The updated deployment.xml contains a commented out example of setting this new 
descriptorChangeMonitorInterval property, but as already said: by default it is 
set to 10 seconds so the monitor is now also active by default. 

> Changing the portlet.xml in a deployed portlet/webapp does not change 
> Jetspeed.
> -------------------------------------------------------------------------------
>
>          Key: JS2-190
>          URL: http://issues.apache.org/jira/browse/JS2-190
>      Project: Jetspeed 2
>         Type: Improvement

>   Components: Deployment
>     Versions: 2.0-dev/cvs, 2.0-M1, 2.0-M2
>     Reporter: Scott T Weaver
>     Assignee: Ate Douma
>      Fix For: 2.0-FINAL

>
> Changing the portlet.xml in a deployed portlet/webapp does not change 
> Jetspeed.  We need a way for jetspeed to redploy/register id the portlet.xml 
> changes.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to