The XCRI-CAP project has given us the perfect reason to implement some of the new features of Java EE 6. Glassfish application server 3 is one of the first fully compliant Java EE 6 application servers. I’d like to mention some of the features I’ve made use of.<\/p>\n
The first is the new scheduling feature found in EJB. The XCRI-CAP file is generated every night by populating a separate DB schema that maps to the XCRI-CAP XSD. Once the schema has been populated, the system regenerates the XCRI-CAP file that is used for the feed. In the past we would have had to use a CRON job to be able to set off the process but EJB 3.1 allows the use of the Schedule annotation. The schedule annotation will turn any EJB method into a timed process in a declarative way, using the\u00a0 schedule annotation. Here is the method we use to set off the nightly process:<\/p>\n
This process runs every night at 2am. More information on scheduling in Java EE 6 can be found here:<\/p>\n
\n\/**
\n* Timed process to update schema and re-populate the XCRI-CAP file
\n*\/
\n@Override
\n@Schedule(second = \"0\", minute = \"0\", hour = \"2\", persistent = false)
\npublic void populateSchema() {
\nString academicYear = getAcademicYear();
\nList progs = loadProgProposals(academicYear);
\npopulateSchema(\"MAIN\", progs, true, false);
\n}
\n<\/code><\/p>\n