commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 35529] - [configuration] FileChangedReloadingStrategy javadoc misleading
Date Mon, 22 Aug 2005 15:30:29 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35529>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35529





------- Additional Comments From jordanh@zootweb.com  2005-08-22 17:30 -------
Spawning a thread would probably violate the j2ee spec and cause huge problems
for people who use containers like JBoss.  Having a true monitoring solution
would be really nice though. 

What does the 5000 ms rate actually do if not monitor the file every 5 seconds?
 I to found the javadoc incredibly confusing.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message