[
https://issues.jboss.org/browse/WFLY-3724?page=com.atlassian.jira.plugin....
]
Ari Silvan reopened WFLY-3724:
------------------------------
My example is based on the Phonebilling example application on the Java EE 7 tutorial, but
is simplified as much as possible. Why the exactly same code is behaving differently on
GlassFish and Wildfly?
On GlassFish:
TestReader class: code line System.out.println("Partition params is not null.");
is called and batch is started as two partitions. Partition params are available.
On WildFly:
TestReader class: code line System.out.println("Partition params is null, should not
be."); is called and batch work cannot be started because partition params are not
available.
Can you please examine the issue a little bit more. I don't think that Java EE 7
tutorial gives an example that is against the specification.
Batch jobs don't receive partition-specific parameters
------------------------------------------------------
Key: WFLY-3724
URL:
https://issues.jboss.org/browse/WFLY-3724
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Batch
Affects Versions: 8.1.0.Final
Environment: Windows 7 Home Premium Service Pack 1 64-bit + JDK8u11 + WildFly
8.1.0 Final
Reporter: Ari Silvan
Assignee: Enrique González Martínez
When defining a batch job chunk step to run as partitions, ItemReader doesn't receive
the partition-specific parameters specified by an implementation of the PartitionPlan
interface. Parameters are null. See steps to reproduce for further details.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)