bike part reward : setting bean ID property automatically

Rod Widdowson rdw at steadingsoftware.com
Wed Feb 12 05:35:03 EST 2014


> Rod and I were talking earlier, and he noted the issue with using that
> approach while using the custom schemas. I suggested he look into whether
> we can configure the default-init/destroy on the builders somehow, but
> that does seem like a problem.

This is the rub.  If we can find a way in the parsers to simulate
"default-init" and "destroy" then not only should we do that, we must do
that.  We want all our code to be the same and I agree (I was wrong)
peppering our classes with random interfaces is a sucky thing to do if there
is a better solution.

If we cannot to the default-init thing (and that seems unlikely), I have no
problems with deriving all classes liable to be summoned by a customer
schema parser from an abstract class in spring-extensions which does all the
spring specific stuff, then we at least keep that Spring stuff out of the
mainline.  

I'll add, to my chagrin, that my head is so full of custom schema parsing
right now that when I made that statement about initializing bean and its
friends that I had complete neglected that we use normal spring beans and
had totally forgotten about default-init.

Finding how to do default-init with custom schemas is on my list.  I'm
running short of interrupt stack so I have put in IDP-370 (by way of a
DPC/FORK if you want to extend the analogy which you don't).

/Rod



More information about the dev mailing list