Hi, I've been trying to figure out if there is a common pattern in how implementations and bindings could be interpretting and applying policies so that we could include this in the SPI. But haven't been successful with this. Maybe with getting policies to work with a few implementation types will give a better idea.
So, to start with I have extended the java implementaion type a bit to support policies. I have picked on the 'Logging' intent for now and have implemented a rudimentary logging mechanism that simply uses System.out.println. I am going to soon replace this with a formal Logging system. I've been looking a SLF4J so that we could facilitate switching of various logging implementations thro policy specifications. But seems like there is no programmatic way of binding the logging options (such as log4j or JDK Logging) into SLF4J. The logging implementation jar in the classpath is the one that would get picked up it seems. So for now I plan to go on with using the JDK Logger and having policies to specify the logging levels, logging handlers and so on. While I am working on completing this, I'd like to explore another implementation type for including policy support for a QoS - maybe transactions. I'd appreciate a lot if people could give me some feedback on the approach I have taken for the java implementation type and also suggestions on a implementation type that we could pickup for supporting transactions. Thanks. - Venkat
