Thank you Ramkumar. I hope I understood the solution suggested by you. My SCA component implementation is a Spring context. It has multiple beans, and Spring dependency injections. I'm using <sca:service> to expose one bean as the service. Since I'm not using SDO, and my service bean is getting a DAO injected the spring way, I had to use some interceptors there. That is why I changed the tuscany code to make it work.
Regards, Rupesh From: Ramkumar R <[email protected]> To: [email protected] Date: 10/23/2009 03:17 PM Subject: Re: tuscany + spring + ProxyFactoryBean Hi Rupesh, You are right, I agree with you. This issue is addressed in 2.x code base as complying with OASIS 1.1 specification. There are lot other scenarios, that are considered in 2.x apart from the one you have pointed out. I believe we don;t have any plans to do changes in 1.x as we consider them as a functionality for 2.x. If you are interested in getting around this issue in 1.x, then I would suggest you to explicitly define the <sca:services> offered by the application context, rather than relying on the implicit services. On Fri, Oct 23, 2009 at 9:57 AM, Rupesh M G <[email protected]> wrote: Hello, Anybody tried using spring ProxyFactoryBean inside the application context working as SCA implementation? In my application, I was getting NullPointerException when I tried to use ProxyFactoryBean to follow the program-to-interfaces approach. My requirement was to use some Spring-Interceptors for the spring beans. I traced the tuscany code raising this exception, and the code for loading beans from the application context. If the bean is of type ProxyFactoryBean, Spring returns null...and tuscany code fails. I had to put an extra null check at 2 places to make my code working. Don't know if it is the right thing to do. Please have a look. The files I edited are attached. In both the files, I have put a comment starting with "rupesh inserted the below block" Regards, Rupesh DISCLAIMER: "The information in this e-mail and any attachment is intended only for the person to whom it is addressed and may contain confidential and/or privileged material. If you have received this e-mail in error, kindly contact the sender and destroy all copies of the original communication. IBS makes no warranty, express or implied, nor guarantees the accuracy, adequacy or completeness of the information contained in this email or any attachment and is not liable for any errors, defects, omissions, viruses or for resultant loss or damage, if any, direct or indirect." -- Thanks & Regards, Ramkumar Ramalingam DISCLAIMER: "The information in this e-mail and any attachment is intended only for the person to whom it is addressed and may contain confidential and/or privileged material. If you have received this e-mail in error, kindly contact the sender and destroy all copies of the original communication. IBS makes no warranty, express or implied, nor guarantees the accuracy, adequacy or completeness of the information contained in this email or any attachment and is not liable for any errors, defects, omissions, viruses or for resultant loss or damage, if any, direct or indirect."
