Skip to main content

[jsr352-public] job properties resolution order and self reference

  • From: Cheng Fang < >
  • To:
  • Subject: [jsr352-public] job properties resolution order and self reference
  • Date: Tue, 26 Mar 2013 22:57:53 -0400

In the following xml, there is job-level property foo (resolved), and also a batchlet-level property foo, declared to be #{jobProperties['foo']}. Which target should this reference resolve to?

<job>
    <properties>
        <property name="foo" value="foo"/>
    </properties>
    <step>
        <batchlet>
            <properties>
                <property name="foo" value="#{jobProperties['foo']}"/>
            </properties>

Since the resolution process starts from the innermost containment, and inside batchlet, foo is already declared (though not resolved), I tend to think it should resolve to itself, hence yield null. I feel this is more natural. I noticed some TCK tests use this reference structure and expect it resolved to the job-level one. What do you think?

Thanks,
Cheng


[jsr352-public] job properties resolution order and self reference

Cheng Fang 03/27/2013

[jsr352-public] Re: job properties resolution order and self reference

Kaushik Mukherjee 03/27/2013

[jsr352-public] Re: job properties resolution order and self reference

Christopher Vignola 03/27/2013

[jsr352-public] Re: job properties resolution order and self reference

Kaushik Mukherjee 03/27/2013

[jsr352-public] Re: Re: job properties resolution order and self reference

Christopher Vignola 03/28/2013
 
 
Close
loading
Please Confirm
Close