> Especially if you also want to explicitly tell iBATIS how to handle > transactions, it's a good idea to create a class that implements both > Interceptor and ConfigurableComponent: the latter to initialize, and the > former to handle the transactions.
I agree. But if you need interceptor functionality, your problem is solved: you put the initializing code in ConfigurableComponent's init method and implement your interceptor, all in one class. In fact, theoretically, you *could* implement an interceptor that does nothing and implements ConfigurableComponent so that your initializing code will be executed by Stripes. But surely we don't want to encourage such a practice. Thus the suggestion of a simple initializing interface that extends ConfigurableComponent and is autodiscovered by Stripes, for the purpose of having a place to put initializing code. Cheers, Freddy ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
