On Mon, Jun 15, 2009 at 10:23 AM, Ramkumar R<[email protected]> wrote: > Hi All, > > Tuscany currently provides a value add on top of the implementation.spring > specification by providing support for SCA annotations. > > Looks like, it would take a while for the specification to approve on > support for SCA annotations. In the mean while > there have been some requirement from the users to provide a switch on/off > feature for supporting SCA annotations in > implementation.spring module. > > (TUSCANY-3096) - Switch off SCA Annotation support for Implementation.Spring > > I believe, defining an implementation policy for this feature will help to > deal with the switch on/off feature. > > Any comments/suggestions? Please. >
We may not need something as complicated as a policy for this as policy would give more flexibility than is really needed. IIUC this is just a global switch to disable the existing support for the entire runtime. You'd think ideally there would be something like a tuscany.properties files for defining those types of things, but we don't have anything like that in 1.x. How about adding a utility extension point with a config interface to the spring extension and have it look up that extension point and if its not null get the config property values from that. The default behaviour if no extension impl is defined would be to do what the code does today, and if Tuscany embeders want to override that then they include their own extension point impl. We could add something for the spring versions supported to the config interface as well so as to avoid that hard coded check thats used today. ...ant
