View • Attachments (0) • Info
Create class WorkflowXmlIngestionStep in org.kuali.kfs.sys.batch. ProcurementCardLoadStep can be used as an example. According to Batch 3
documentation, add an execute method to the step.
package org.kuali.kfs.sys.batch; ... import edu.iu.uis.eden.batch.CompositeXmlDocCollection; import edu.iu.uis.eden.batch.FileXmlDocCollection; import edu.iu.uis.eden.batch.XmlDoc; import edu.iu.uis.eden.batch.XmlDocCollection; import edu.iu.uis.eden.util.Utilities; import edu.iu.uis.eden.web.UserLoginFilter; import org.kuali.kfs.sys.batch.AbstractStep; import org.apache.log4j.Logger; ... public class WorkflowXmlIngestionStep extends AbstractStep { public boolean execute(String jobName) throws InterruptedException { ... } }
| The return value of the execute() method does not determine whether the Step succeeded or failed. Rather, whether the additional steps should be run or not. Any step failure is described through an InterruptedException |
This is where a majority of the functionality will go.
${staging.directory}/ingester should be read.
${staging.directory}
kualiConfigurationService.getPropertyString(KFSConstants.STAGING_DIRECTORY_KEY)
After files are read from
This happens automatically through the framework. There is no need to worry about the log.
private static final Logger LOG = Logger.getLogger(WorkflowXmlIngestionStep.class);
Create an entry in Spring for the step. Inject the KualiConfigurationService and XmlIngesterService into the Step.
<bean id="workflowXmlIngestionStep" class="org.kuali.kfs.sys.batch.WorkflowXmlIngestionStep" parent="step"> <property name="xmlIngesterService" ref="xmlIngesterService" /> <property name="kualiConfigurationService" ref="kualiConfigurationService" /> </bean>
|
Browse Space |
Explore Confluence |
Your Account |
Add Content |