You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by rabelenda <ra...@gmail.com> on 2009/01/02 20:13:39 UTC
SERVICE_ONJECT_SUPPLIER not specified
Hi, I have developed a webService using axis2 and spring. When I request de
wsdl file of the webservice I get the right wsdl file, but when I want to
use a defined operation of the webservice (using a java client or a browser)
I get the following exception:
[CODE]org.apache.axis2.AxisFault: The SERVICE_OBJECT_SUPPLIER parameter is
not specified.
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:512)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:370)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:228)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at springma.webservice.MyWSStub.myOp(MyWSStub.java:1077)
at springma.test.webservice.MyWSTests.main(MyWSTests.java:24)
[/CODE]
In the client the line pointed contains the call to the operation, and in
the stub is [CODE]_operationClient.execute(true);[/CODE]
Anybody knows what it could be? Thanks in advance.
--
View this message in context: http://www.nabble.com/SERVICE_ONJECT_SUPPLIER-not-specified-tp21255767p21255767.html
Sent from the Axis - User mailing list archive at Nabble.com.
Re: Unsubscribe
Posted by Andreas Veithen <an...@gmail.com>.
You need to send a mail to axis-user-unsubscribe@ws.apache.org.
On Sun, Jan 4, 2009 at 05:33, Harikrishna Imadabattina
<ha...@techendeavour.com> wrote:
> HI I want to unsubscribe from this group. Please let me know the way
>
>
>
> Thanks
>
> Harikrishna
>
>
>
> ________________________________
>
> From: Amila Suriarachchi [mailto:amilasuriarachchi@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 <ro...@gmail.com>
> wrote:
>
> On Fri, Jan 2, 2009 at 5:26 PM, rabelenda <ra...@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/
Unsubscribe
Posted by Harikrishna Imadabattina <ha...@techendeavour.com>.
HI I want to unsubscribe from this group. Please let me know the way
Thanks
Harikrishna
_____
From: Amila Suriarachchi [mailto:amilasuriarachchi@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 <ro...@gmail.com>
wrote:
On Fri, Jan 2, 2009 at 5:26 PM, rabelenda <ra...@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/
Re: SERVICE_ONJECT_SUPPLIER not specified
Posted by rabelenda <ra...@gmail.com>.
Amila Suriarachchi wrote:
>
> 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
> <ro...@gmail.com>wrote:
>
>> On Fri, Jan 2, 2009 at 5:26 PM, rabelenda <ra...@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
>>
>
> I have tested changing serviceObjetSupplier with ServiceObjectSupplier in
> the services.xml file and I get a different error message. When I start
> tomcat I get "[INFO] org.apache.axis2.deployment.DeploymentException: The
> following error occu
> rred during schema generation: null" but nothing else information about
> this error. In services.xml I have tu put serviceObjetSupplier or
> ServiceObjectSupplier? how can I manage to get more verbose from the
> output of tomcat (I have put all logging properties to FINE)?
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
>
--
View this message in context: http://www.nabble.com/SERVICE_ONJECT_SUPPLIER-not-specified-tp21255767p21290205.html
Sent from the Axis - User mailing list archive at Nabble.com.
Re: SERVICE_ONJECT_SUPPLIER not specified
Posted by Amila Suriarachchi <am...@gmail.com>.
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 <ro...@gmail.com>wrote:
> On Fri, Jan 2, 2009 at 5:26 PM, rabelenda <ra...@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/
RE: SERVICE_ONJECT_SUPPLIER not specified
Posted by Martin Gainty <mg...@hotmail.com>.
spring\src\META-INF\services.xml:
<service name="SpringService">
<parameter name="ServiceObjectSupplier" >org.apache.axis2.extensions.spring.receivers.SpringAppContextAwareObjectSupplier</parameter>
Bon Chance,
Martin
______________________________________________
Note de déni et de confidentialité
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.
> To: java-user@axis.apache.org
> From: sravanpalakala@gmail.com
> Subject: Re: SERVICE_ONJECT_SUPPLIER not specified
> Date: Fri, 25 Mar 2011 10:52:53 +0000
>
> rabelenda <rabelenda <at> gmail.com> writes:
>
> >
> >
> > Ready, I didn't kow that that was an expected behaivour. Now I run the client
> > and all works, thanks to all. Solution: change serviceObjectSupplier to
> > ServiceObjectSupplier. The null message was beacause I had forgotten that I
> > had deleted the service folder in the webapplication . Thanks to all .
>
>
> can u please explain me how u solved this error
> >
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
Re: SERVICE_ONJECT_SUPPLIER not specified
Posted by sravan kumar palakala <sr...@gmail.com>.
rabelenda <rabelenda <at> gmail.com> writes:
>
>
> Ready, I didn't kow that that was an expected behaivour. Now I run the client
> and all works, thanks to all. Solution: change serviceObjectSupplier to
> ServiceObjectSupplier. The null message was beacause I had forgotten that I
> had deleted the service folder in the webapplication . Thanks to all .
can u please explain me how u solved this error
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
Re: SERVICE_ONJECT_SUPPLIER not specified
Posted by rabelenda <ra...@gmail.com>.
Ready, I didn't kow that that was an expected behaivour. Now I run the client
and all works, thanks to all. Solution: change serviceObjectSupplier to
ServiceObjectSupplier. The null message was beacause I had forgotten that I
had deleted the service folder in the webapplication :-). Thanks to all ;-).
--
View this message in context: http://www.nabble.com/SERVICE_ONJECT_SUPPLIER-not-specified-tp21255767p21296527.html
Sent from the Axis - User mailing list archive at Nabble.com.
Re: SERVICE_ONJECT_SUPPLIER not specified
Posted by robert lazarski <ro...@gmail.com>.
On Mon, Jan 5, 2009 at 11:43 AM, rabelenda <ra...@gmail.com> wrote:
> 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 ?
>
> --
Please post the entire stacktrace. You probably have some other errors
that are closer to the problem. You need to enable either
commons-logging or log4j in your war file. For example. you should
have a log4j.properties in WEB-INF/classes . The axis2 distro has an
example.
HTH,
Robert
Re: SERVICE_ONJECT_SUPPLIER not specified
Posted by rabelenda <ra...@gmail.com>.
iksrazal wrote:
>
> On Fri, Jan 2, 2009 at 5:26 PM, rabelenda <ra...@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
>
>
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.
Re: SERVICE_ONJECT_SUPPLIER not specified
Posted by robert lazarski <ro...@gmail.com>.
On Fri, Jan 2, 2009 at 5:26 PM, rabelenda <ra...@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
Re: SERVICE_ONJECT_SUPPLIER not specified
Posted by rabelenda <ra...@gmail.com>.
iksrazal wrote:
>
> On Fri, Jan 2, 2009 at 4:13 PM, rabelenda <ra...@gmail.com> wrote:
>>
>> Hi, I have developed a webService using axis2 and spring. When I request
>> de
>> wsdl file of the webservice I get the right wsdl file, but when I want to
>> use a defined operation of the webservice (using a java client or a
>> browser)
>> I get the following exception:
>>
>> [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
> :
>
> Parameter implInfoParam =
> service.getParameter(Constants.SERVICE_CLASS);
> if (implInfoParam != null) {
> final Class implClass = Loader.loadClass(
> classLoader,
> ((String) implInfoParam.getValue()).trim());
> return
> org.apache.axis2.java.security.AccessController.doPrivileged(
> new PrivilegedExceptionAction() {
> public Object run() throws
> InstantiationException, IllegalAccessException {
> return implClass.newInstance();
> }
> }
> );
> } else {
> throw new AxisFault(
> Messages.getMessage("paramIsNotSpecified",
> "SERVICE_OBJECT_SUPPLIER"));
> }
>
> HTH,
> Robert
>
>
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 :-).
--
View this message in context: http://www.nabble.com/SERVICE_ONJECT_SUPPLIER-not-specified-tp21255767p21257431.html
Sent from the Axis - User mailing list archive at Nabble.com.
Re: SERVICE_ONJECT_SUPPLIER not specified
Posted by robert lazarski <ro...@gmail.com>.
On Fri, Jan 2, 2009 at 4:13 PM, rabelenda <ra...@gmail.com> wrote:
>
> Hi, I have developed a webService using axis2 and spring. When I request de
> wsdl file of the webservice I get the right wsdl file, but when I want to
> use a defined operation of the webservice (using a java client or a browser)
> I get the following exception:
>
> [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
:
Parameter implInfoParam =
service.getParameter(Constants.SERVICE_CLASS);
if (implInfoParam != null) {
final Class implClass = Loader.loadClass(
classLoader,
((String) implInfoParam.getValue()).trim());
return
org.apache.axis2.java.security.AccessController.doPrivileged(
new PrivilegedExceptionAction() {
public Object run() throws
InstantiationException, IllegalAccessException {
return implClass.newInstance();
}
}
);
} else {
throw new AxisFault(
Messages.getMessage("paramIsNotSpecified",
"SERVICE_OBJECT_SUPPLIER"));
}
HTH,
Robert