[#BATCH-119] ExitStatus can't be used in JMX (or other remote interfaces).

Spring Batch

ExitStatus can't be used in JMX (or other remote interfaces).

Created: 29/Aug/07 03:08 AM Updated: 07/Aug/08 10:06 AM

Component/s:

Infrastructure

Affects Version/s:

1.0-m2

Fix Version/s:

1.0-m3

Security Level:

Public (Public Issues)

Time Tracking:

Not Specified

Description

« Hide

ExitStatus is not Serializable, so it can't be used in JMX (or other remote interfaces). The TaskExecutorLauncher in the samples shows this quite quickly (launch with -Dcom.sun.management.jmxremote and look in the jconsole).

All

Comments

Work Log

Change History

FishEye

Builds

Sort Order:

[ Permlink | « Hide ]

Dave Syer added a comment - 29/Aug/07 03:59 AM

Made ExitStatus Serializable, which is OK up to a point, but still not great for jconsole demos - the class needs to be loadable by the client. Next stage will be to add JMX data type (e.g. CompositeDataSupport) to output from remote MBean, e.g. with AOP.

[ Permlink | « Hide ]

Dave Syer added a comment - 29/Aug/07 08:22 AM

Added TypeConverterMethodInterceptor and configuration example in adhocLoopJob.xml. Converts ExitStatus to String by calling toString() - pretty basic but could be extended by adding a TypeConverter instance.

[ Permlink | « Hide ]

Dave Syer added a comment - 07/Aug/08 10:06 AM

Assume closed as resolved and released