Bug 4705 - TCK ContextGetIdTests issues
TCK ContextGetIdTests issues
Status: RESOLVED WONTFIX
Product: jbatch
Classification: Unclassified
Component: source
1
All All
: P5 normal
: ---
Assigned To: ScottKurz
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-02-23 02:33 UTC by mminella
Modified: 2013-03-18 06:17 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mminella 2013-02-23 02:33:18 UTC
1.  testJobContextGetId - How is the job1 set on the JobContext?  Why do we believe that it should be job1?
2.  testStepContextGetId - Same question only at the step level.
Comment 1 ScottKurz 2013-03-08 04:37:53 UTC
Michael,

The naming has been changed with the description spelled out even more in PFD 1.5.

We'll now have:

public interface JobContext <T> {
	/**
	 * Get job name
	 * @return value of 'id' attribute from <job>
	 */
	public String getJobName();


public interface StepContext <T,P extends Serializable> {	
	/**
	 * Get step name
	 * @return value of 'id' attribute from <step>
	 * 
	 */	
	public String getStepName();

-------

Previously each of these two methods had been named simply getId().


In both cases though, they map simply to the @id attribute on <job>, and <step> respectively.

This is where the 'job1' and 'step1' values come from (in the corresponding JSL), uncreative as they may be.