In New Features Part 1, I mentioned that one of the biggest impediments to a release was the urge to implement that one last killer feature. Well I’m weak – I caved, I did another feature.
JMX With Oddjob
The new feature is the ability to get and set attributes and invoke operations of remote MBeans from within Oddjob.
Properties in Oddjob
Two cool things have happened to properties in Oddjob 1.2. First is that nested property expansion is now supported. This allows us to resolve expressions like
One new features in Oddjob 1.2, took me ages – and it’s just two little buttons!
Here they are:
All they do is move a row up or down. Here we need to move our row up, so that
favourite.fruit is defined before it is needed to define
It’s coming to that time again. That time where I draw a line in the README file and call it a release. Being the only developer on a project that doesn’t have a large user base, a release is really just a state of mind. Like the flying ants that decide on mass to pour forth from their nests without the aid of any social media – it becomes time for a release.
Here’s my previous password passed to Spring example run from Oddjob:
Run as a GUI, Oddjob provides a simple form for entering properties including a password prompt.
I previously presented a
CustomPropertyConfgurer that allows properties outside of Spring to be accessed from within Spring. The article was syndicated by DZone where a reader noted that in fact the Spring class
PropertySourcesPlaceholderConfigurer has a
setProperties method, and so for my particular example, the
CustomPropertyConfigurer was redundant.
Running SQL install scripts can be tedious. They get so far, and then fail. Finding out where they failed isn’t always easy and when the problem is fixed, there is a choice – drop the schema and re-run, or comment out what has been applied already, and re-run. I once spent an entire morning in this fix/re-run cycle for a particularly large and badly maintained script. It was very ungratifying work. What I need, I thought, are some friendly green ticks, some positive visual feedback to aid job satisfaction.
(Please note there as a postscript to this post: A Simpler Custom Property in Spring)
<context:property-placeholder> is a really easy way to provide property replacements in Spring configurations with values from a standard Java Properties file. But what if you don’t want a property hard coded into a file – a clear text password for instance? Spring provides all the bits and pieces to write your own property replacement. Let me introduce my
I’ve been progressing quite nicely along my Road to Maven, that was until today when I tried to take a detour.
While many are looking forward to the holidays, those that must support batch based applications may not be so enthusiastic as they anticipate the numerous support calls for jobs that failed because they shouldn’t have run or for jobs that should have run but didn’t. It was after one such lost long weekend a decade ago that I decided to have a go at writing my own scheduling system.