iksrazal wrote: > > On Fri, Jan 2, 2009 at 5:26 PM, rabelenda <[email protected]> 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 > >
I have changed serviceObjectSupplier with ServiceObjectSupplier in the services.xml file and I get a different error. When loading tomcat I get [INFO] org.apache.axis2.deployment.DeploymentException: The following error occu > rred during schema generation: null. I have tested setting all logging > properties of tomcat to ALL and I don't get any more explanation, any > ideas? In the services.xml file, I must put serviceObjectSupplier or > ServiceObjectSupplier ? -- View this message in context: http://www.nabble.com/SERVICE_ONJECT_SUPPLIER-not-specified-tp21255767p21292204.html Sent from the Axis - User mailing list archive at Nabble.com.
