RE: Unable to hit AXIS2 service

2008-01-11 Thread Kandalam, Anjana
Thank you very much for your responses.

Anjana Kandalam
Private Client Group - AIG
Work: 908-679-2608
Cell: 908-596-0424
-Original Message-
From: Deepal jayasinghe [mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 10, 2008 9:51 AM
To: axis-user@ws.apache.org
Subject: Re: Unable to hit AXIS2 service


 Kevin, Thanks for your response. My client is Axis 1.4. When I try to
 hit the Axis2 service, I get the following exception

  

 The endpoint reference (EPR) for the Operation not found is
 http://localhost:9082/axis2/services/AcordWinsRateService and the WSA
 Action =

  

 Where my EPR is http://localhost:9082/axis2/services/AcordWinsRateService.

 When I use the Axis2.0 client and hit the 2.0 service I am able to hit
 it and get the response. Why is this?

Hmm , as I can see the issue is you are not sending the soap action ,
please look at the wsdl (as Keith suggested) if the wsdl has a soap
action then you need to send that in the request,

-Deepal


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Unable to hit AXIS2 service

2008-01-10 Thread Deepal jayasinghe

 Kevin, Thanks for your response. My client is Axis 1.4. When I try to
 hit the Axis2 service, I get the following exception

  

 The endpoint reference (EPR) for the Operation not found is
 http://localhost:9082/axis2/services/AcordWinsRateService and the WSA
 Action =

  

 Where my EPR is http://localhost:9082/axis2/services/AcordWinsRateService.

 When I use the Axis2.0 client and hit the 2.0 service I am able to hit
 it and get the response. Why is this?

Hmm , as I can see the issue is you are not sending the soap action ,
please look at the wsdl (as Keith suggested) if the wsdl has a soap
action then you need to send that in the request,

-Deepal


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Unable to hit AXIS2 service

2008-01-09 Thread Kandalam, Anjana
Hi,

 

I have implemented my service in Axis 2.0 soap 1.2 . I am unable to hit this
service from any SOAP 1.1 client. How do I service in order to make it
available to any client??

 

Anjana Kandalam 
Private Client Group - AIG 
Work: 908-679-2608 
Cell: 908-596-0424 

 



Re: Unable to hit AXIS2 service

2008-01-09 Thread keith chapman
Hi Anjana,

The statement  have implemented my service in Axis 2.0 soap 1.2 sounds
weird. Axis2 exposes any web service over SOAP 1.1, SOAP 1.2 and REST. Just
implementing the service would do this for you. So any web services client
(Let it be over SOAP 1.1 or SOAP 1.2 ) should be able access your service.

Thanks,
Keith.

On Jan 9, 2008 8:08 PM, Kandalam, Anjana [EMAIL PROTECTED] wrote:

  Hi,



 I have implemented my service in Axis 2.0 soap 1.2 . I am unable to hit
 this service from any SOAP 1.1 client. How do I service in order to make
 it available to any client??



 Anjana Kandalam
 Private Client Group - AIG
 Work: 908-679-2608
 Cell: 908-596-0424






-- 
Keith Chapman
Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org


RE: Unable to hit AXIS2 service

2008-01-09 Thread Kandalam, Anjana
Kevin, Thanks for your response. My client is Axis 1.4. When I try to hit
the Axis2 service, I get the following exception

 

The endpoint reference (EPR) for the Operation not found is
http://localhost:9082/axis2/services/AcordWinsRateService and the WSA Action
=

 

Where my EPR is http://localhost:9082/axis2/services/AcordWinsRateService
http://localhost:9082/axis2/services/AcordWinsRateService .

When I use the Axis2.0 client and hit the 2.0 service I am able to hit it
and get the response. Why is this?

 

 

Anjana Kandalam 
Private Client Group - AIG 
Work: 908-679-2608 
Cell: 908-596-0424 

  _  

From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, January 09, 2008 10:01 AM
To: axis-user@ws.apache.org
Subject: Re: Unable to hit AXIS2 service

 

Hi Anjana,

The statement  have implemented my service in Axis 2.0 soap 1.2 sounds
weird. Axis2 exposes any web service over SOAP 1.1, SOAP 1.2 and REST. Just
implementing the service would do this for you. So any web services client
(Let it be over SOAP 1.1 or SOAP 1.2 ) should be able access your service.

Thanks,
Keith.

On Jan 9, 2008 8:08 PM, Kandalam, Anjana [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]  wrote:

Hi,

 

I have implemented my service in Axis 2.0 soap 1.2 . I am unable to hit this
service from any SOAP 1.1 client. How do I service in order to make it
available to any client??

 

Anjana Kandalam 
Private Client Group - AIG 
Work: 908-679-2608 
Cell: 908-596-0424 

 




-- 
Keith Chapman
Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/ http://wso2.org/ 

blog: http://www.keith-chapman.org http://www.keith-chapman.org  



Re: Unable to hit AXIS2 service

2008-01-09 Thread keith chapman
The reason is that the server does not have enough information to dispatch
the request to the correct operation. Please check the WSDL for the service.
The WSDL would state the default soap action it is looking for. If your
client is using SOAP 1.1 (in SOAP 1.1 the soapAction is mandatory) it can
set the legitimate soap action for that service to enable the server to
dispatch it to the correct operation. the default dispatching works as
follows, The service is dispatched using the request URI.

1. Try to dispatch to the operation using the request URI (possible if the
uri is serviceName/operationName)
2. Use Addressing details
3. Dispatch using soapaction
4. Dispatch using the soap body

So you need to provide at least one of the following for the request to get
dispatched to the operation.

Thanks,
Keith.

On Jan 9, 2008 9:49 PM, Kandalam, Anjana [EMAIL PROTECTED] wrote:

  Kevin,



 I am not using WS-addressing in my services.xml,  ( is there is no
 actionMapping element) still the error message says WSA action =  When I
 changed my client to add the operation name then it worksDo you know
 why?



 Thanks a lot.



 Anjana Kandalam
 Private Client Group - AIG
 Work: 908-679-2608
 Cell: 908-596-0424
   --

 *From:* keith chapman [mailto:[EMAIL PROTECTED]
 *Sent:* Wednesday, January 09, 2008 10:01 AM
 *To:* axis-user@ws.apache.org
 *Subject:* Re: Unable to hit AXIS2 service



 Hi Anjana,

 The statement  have implemented my service in Axis 2.0 soap 1.2 sounds
 weird. Axis2 exposes any web service over SOAP 1.1, SOAP 1.2 and REST.
 Just implementing the service would do this for you. So any web services
 client (Let it be over SOAP 1.1 or SOAP 1.2 ) should be able access your
 service.

 Thanks,
 Keith.

 On Jan 9, 2008 8:08 PM, Kandalam, Anjana [EMAIL PROTECTED] wrote:

 Hi,



 I have implemented my service in Axis 2.0 soap 1.2 . I am unable to hit
 this service from any SOAP 1.1 client. How do I service in order to make
 it available to any client??



 Anjana Kandalam
 Private Client Group - AIG
 Work: 908-679-2608
 Cell: 908-596-0424






 --
 Keith Chapman
 Software Engineer
 WSO2 Inc.
 Oxygenating the Web Service Platform.
 http://wso2.org/

 blog: http://www.keith-chapman.org




-- 
Keith Chapman
Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org