HI I want to unsubscribe from this group. Please let me know the way
Thanks Harikrishna _____ From: Amila Suriarachchi [mailto:amilasuriarach...@gmail.com] Sent: Sunday, January 04, 2009 7:56 AM To: axis-user@ws.apache.org Subject: Re: SERVICE_ONJECT_SUPPLIER not specified have a look at here[1]. you need to specify a object supplier at the services.xml thanks, Amila. [1] http://ws.apache.org/axis2/1_4_1/spring.html On Sat, Jan 3, 2009 at 2:11 AM, robert lazarski <robertlazar...@gmail.com> wrote: On Fri, Jan 2, 2009 at 5:26 PM, rabelenda <rabele...@gmail.com> wrote: >>> [CODE]org.apache.axis2.AxisFault: The SERVICE_OBJECT_SUPPLIER parameter >>> is >>> not specified. >> >> You most likely have a bean name / service class mismatch. I'd look >> for typos. Here's the problem code from >> modules/kernel/src/org/apache/axis2/receivers/AbstractMessageReceiver.java > > I have search for any mistake and I didn't find anything. I tested chenging > the SpringBeanName parameter in the services.xml file to an invalid one and > the application gives me the same error. But if a put it in the correct way, > it still gives me the error. I think that the problem isn't a mapping > between bean and service because if a put an invalid class name on the bean > the server (tomcat) gives me an error when deploying saying that the class > doesn't exists. I don't kow if is this what you were thinking that could be > wrong, thanks for the fast reply :-). > Perhaps its actually not finding the ServiceObjectSupplier . Make sure the name is correct there. Put axis2 / spring in debug and make sure that spring is loading correctly. You'll see warnings in the logs if axis2 can't find a bean name, ie, spring isn't getting loaded, before the exception. HTH, Robert -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/
