http://cse-mjmcl.cse.bris.ac.uk/blog/2007/06/20/1182370280435.htm
The Spring Framework integrates with the Quartz scheduler in a way that makes Quartz much easier to use. Although in order to use Spring beans with your Quartz jobs you have to deviate slightly from the usual Spring "dependency injection" way of doing things. According to the Spring API this is necessary because Quartz itself is responsible for the lifecycle of its Jobs.
I was recently refactoring my use of Quartz and Spring in my feed aggregator web application. Rather than explain the internal workings of my application at this time, I will explain some features I discovered with reference to James Goodwill's recent simple example of using Quartz and Spring together. James shows how a "cron style" job can easily be created by configuring Quartz Job, trigger, SchedulerFactoryBean and loading up the application context.
Source : http://cse-mjmcl.cse.bris.ac.uk/blog/2007/06/20/1182370280435.html
shared items
Tuesday, April 27, 2010
Monday, March 29, 2010
VM setting in Eclipse
http://wiki.eclipse.org/Eclipse.iniSpecifying the JVM
One of the most recommended options to use is to specify a specific JVM for Eclipse to run on. Doing this ensures that you are absolutely certain which JVM Eclipse will run in and insulates you from system changes that can alter the "default" JVM for your system. Many a user has been tripped up because they thought they knew what JVM would be used by default, but they thought wrong. eclipse.ini lets you be CERTAIN.
The following examples of eclipse.ini demonstrate correct usage of the -vm option.
Note the format of the -vm option - it is important to be exact:
The -vm option and its value (the path) must be on separate lines.
The value must be the full absolute path to the Java executable, not just to the Java home directory.
The -vm option must occur before the -vmargs option, since everything after -vmargs is passed directly to the JVM.
Windows Example
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-vm
C:\Java\JDK\1.5\bin\javaw.exe
-vmargs
-Xms40m
-Xmx512m
Source : http://wiki.eclipse.org/Eclipse.ini
One of the most recommended options to use is to specify a specific JVM for Eclipse to run on. Doing this ensures that you are absolutely certain which JVM Eclipse will run in and insulates you from system changes that can alter the "default" JVM for your system. Many a user has been tripped up because they thought they knew what JVM would be used by default, but they thought wrong. eclipse.ini lets you be CERTAIN.
The following examples of eclipse.ini demonstrate correct usage of the -vm option.
Note the format of the -vm option - it is important to be exact:
The -vm option and its value (the path) must be on separate lines.
The value must be the full absolute path to the Java executable, not just to the Java home directory.
The -vm option must occur before the -vmargs option, since everything after -vmargs is passed directly to the JVM.
Windows Example
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-vm
C:\Java\JDK\1.5\bin\javaw.exe
-vmargs
-Xms40m
-Xmx512m
Source : http://wiki.eclipse.org/Eclipse.ini
Sunday, January 17, 2010
javascript : Select all checkbox
function checkall()
{
var len =document.getElementsByName('asid');
if(len.length != null)
{
for (var i = 0; i < len.length ; i++) {
len[i].checked = true;
}
}
else
{
len.checked = true;
}
}
function clearall()
{var len =document.getElementsByName('asid');
if(len.length != null)
{
for (var i = 0; i < len.length ; i++) {
len[i].checked = false;
}
}
}
Monday, December 28, 2009
Thursday, November 12, 2009
Removing Stale Rails Sessions
Source : http://www.realityforge.org/articles/2006/03/01/removing-stale-rails-sessions
Subscribe to:
Posts (Atom)