Currently the HeuristicPojoProcessor is used to Heuristically evaluates an un-annotated Java implementation type to determine services, references, and properties according to the algorithm described in the SCA Java Client and Implementation Model Specification.
Today, the HeuristicPojoProcessor is also basically used to introspect Spring Bean Class to determine services, references and properties as all the Spring Beans are Java Classes anyways. Spring Framework allows references and properties to be set as private Fields (with a public/protected setter & getter methods), whereas SCA only allows references and properties to be set as public OR protected Fields (in case of unannotated). So I have now created a SpringBeanPojoProcessor which can return the references and properties even if they are declared as private Fields (with a with a public/protected setter & getter methods). What is bothering me is that, SpringBeanPojoProcessor is now a duplicate of HeuristicPojoProcessor except for a few lines of code added to instrospect private Fields to determine references and properties. Like to take some suggestions here, if it would be good idea to allow HeuristicPojoProcessor to instrospect private Fields based on user inputs? -- Thanks & Regards, Ramkumar Ramalingam
