jPOS Spaces have proven to be very useful for us and I believe that they could be useful for others too, but adding a full jPOS dependency may prevent its use by other projects, so I did some minor surgery in order to remove a few dependencies and I’ve created a minimalist version of it here.
If you think I’m doing this just to test the new exciting Google Code hosting you are wrong, but I have to admit that it was the trigger… I couldn’t resist to give it a shot 🙂
A note to jPOS users: You don’t need miniSpace, you have it inside jPOS. I believe that we can benefit from external feedback from people using miniSpace – we will port improvements made in miniSpace-land back to jPOS-land as we see fit.
We recently went live on yet another instance of a jPOS based application called OLS.Switch, and after several months working with the OLS team we reached over 1000 iterations.
At the same time, we see a lot of people in our mailing lists, new to jPOS, sometimes new to payment systems, and still facing a deadline in say … one week (two weeks for the pragmatists).
I consider myself an average programmer, but I’ve been exposed to payment systems for over 15 years, and I wrote jPOS from scratch, and the OLS team has tremendous experience in this area, and we still need to work month after month, iteration after iteration in order to get ready to go live.
Am I missing something? Is this just because I don’t use an IDE? Hmm… I doubt it.
Andy (OLS’ CTO) put it in a very nice way in his blog.