Re: Problem with invoking a https based service
Hi Divakar, I could not find why it didn't work for you, according to the logs. If you can build Axis2/C from source, you can test if the SSL transport (i.e., without any SOAP stuff) is working using the test/core/transport/http/test_http_transport.c test case. Regards, Dumindu. divakar wrote: Hi All, I am facing some problems with invoking a https based .Net webservice using the axis2c client. It is giving the error Error code: 82 :: Input stream is NULL in msg_ctx in the client log file. I am attaching the axis2.xml, client log file sample program for your reference. Please check the same and let me know, if i am making any mistakes in my client program. Thanks Regards, Murali Krishna K - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | http://wso2.com | Oxygenating the Web Service Platform signature.asc Description: OpenPGP digital signature
Re: Problem with invoking a https based service
Manjula Peiris wrote: Hi Divakar, You have not set the ca-cert in the axis2.xml. You need to set the following parameter in the axis2.xml. parameter name=SERVER_CERT/path/to/ca/certificate/parameter This is not necessary as the SERVER_CERT has been set in the client code. -Dumindu. signature.asc Description: OpenPGP digital signature
Re: Axis2/C - USERNAME and PASSWORD
I tried to run echo.c using the Axis2C 1.1 release, but I'm not seeing the basic http authorization in the http headers. I'm expecting to see something like Authorization: Basic YJKLa35. I'm using tcp monitor to check the outgoing message (shown below). Is there something else I have to do to get this to work? This is my command: C:\axis2c-src-1.1.0\build\deploy\bin\samplesecho.exe -auth user pass This is the outgoing message: POST /axis2/services/echo HTTP/1.1 User-Agent: Axis2/C Content-Length: 512 Content-Type: application/soap+xml;charset=UTF-8 Host: localhost:9090 soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header xmlns:wsa=http://www.w3.org/2005/08/addressing; wsa:Tohttp://localhost:9091/axis2/services/echo/wsa:To wsa:Actionhttp://ws.apache.org/axis2/c/samples/echoString/wsa:Action wsa:MessageID4ecf636a-5637-4be9-afe4-80e80f0e3117/wsa:MessageID /soapenv:Header soapenv:Body ns1:echoString xmlns:ns1=http://ws.apache.org/axis2/services/echo; textHello World!/text /ns1:echoString /soapenv:Body/soapenv:Envelope Thanks, Mike Michael J Molé Software Engineer IBM Software Group - Rational (781)676-2710 Dumindu Pallewela [EMAIL PROTECTED] 08/13/2007 07:38 AM Please respond to Apache AXIS C User List axis-c-user@ws.apache.org To Apache AXIS C User List axis-c-user@ws.apache.org cc Michael Mole/Lexington/[EMAIL PROTECTED] Subject Re: Axis2/C - USERNAME and PASSWORD Michael Mole wrote: I'm looking for more information about AXIS2_USER_NAME and AXIS2_PASSWORD in axis2_const.h. What are they used for, and how are they used? I'm still trying to solve my issue of using Basic http Authentication with my web services, and these look like they may be the key. Any help is greatly appreciated. We have added HTTP basic authentication support for axis2/c client. All you have to do is to set the two properties HTTP_AUTH_USERNAME and HTTP_AUTH_PASSWD in your client code. Please refer to echo.c [1] for a sample of its usage. I propose that we remove the AXIS2_USER_NAME and AXIS2_PASSWORD declarations as they are not being used. HTTP authentication related declarations can be found in axis2_http_transport.h. Regards, Dumindu. [1] http://svn.apache.org/viewvc/webservices/axis2/trunk/c/samples/client/echo/echo.c?view=markup - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
axis2_stub_create_with_endpoint_ref_and_client_home always returns NULL
hi folks, I am new to axis2/c, I try to get the following simple c
client to work, but for some reason
axis2_stub_create_with_endpoint_ref_and_client_home always returns
NULL. The env and endpoint_ref I pass to the function both seem to be
valid. Any idea what the problem might be?
thanks!
axis2_stub_t *stub = NULL;
axis2_endpoint_ref_t *endpoint_ref = NULL;
const axutil_env_t *env = NULL;
const axis2_char_t *endpoint_uri = NULL;
const axis2_char_t *client_home = NULL;
AXIS2_FUNC_PARAM_CHECK ( client_home, env, NULL)
address = http://localhost:8080/test/services/test;;
client_home = AXIS2_GETENV(AXIS2C_HOME);
if (!client_home || !strcmp (client_home, ))
client_home = ./;
env = axutil_env_create_all(test_client.log, AXIS2_LOG_LEVEL_TRACE);
if (NULL == endpoint_uri)
{
endpoint_uri =
axis2_stub_ReportGenerate_get_endpoint_uri_from_wsdl( env );
}
endpoint_ref = axis2_endpoint_ref_create(env, endpoint_uri);
stub = axis2_stub_create_with_endpoint_ref_and_client_home (
env, endpoint_ref, client_home );//stub is null
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2/C - USERNAME and PASSWORD
Hi Mole, Currently the auth header is sent only if the server requests for it. So if your server sends a WWW-Authenticate: header when authentication failed at the first request, Axis2 will send another with the required header. However, I think we should have allowed the user to send the auth header without waiting for a failed response in the first place, because it is only an additional overhead, if the user already *knows* that the server requires basic auth, Somehow we missed it from 1.1 release :( Regards, Dumindu. Michael Mole wrote: I tried to run echo.c using the Axis2C 1.1 release, but I'm not seeing the basic http authorization in the http headers. I'm expecting to see something like Authorization: Basic YJKLa35. I'm using tcp monitor to check the outgoing message (shown below). Is there something else I have to do to get this to work? *This is my command:* C:\axis2c-src-1.1.0\build\deploy\bin\samplesecho.exe -auth user pass *This is the outgoing message:* POST /axis2/services/echo HTTP/1.1 User-Agent: Axis2/C Content-Length: 512 Content-Type: application/soap+xml;charset=UTF-8 Host: localhost:9090 soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header xmlns:wsa=http://www.w3.org/2005/08/addressing; wsa:Tohttp://localhost:9091/axis2/services/echo/wsa:To wsa:Actionhttp://ws.apache.org/axis2/c/samples/echoString/wsa:Action wsa:MessageID4ecf636a-5637-4be9-afe4-80e80f0e3117/wsa:MessageID /soapenv:Header soapenv:Body ns1:echoString xmlns:ns1=http://ws.apache.org/axis2/services/echo; textHello World!/text /ns1:echoString /soapenv:Body/soapenv:Envelope Thanks, Mike Michael J Molé Software Engineer IBM Software Group - Rational (781)676-2710 *Dumindu Pallewela [EMAIL PROTECTED]* 08/13/2007 07:38 AM Please respond to Apache AXIS C User List axis-c-user@ws.apache.org To Apache AXIS C User List axis-c-user@ws.apache.org cc Michael Mole/Lexington/[EMAIL PROTECTED] Subject Re: Axis2/C - USERNAME and PASSWORD Michael Mole wrote: I'm looking for more information about AXIS2_USER_NAME and AXIS2_PASSWORD in axis2_const.h. What are they used for, and how are they used? I'm still trying to solve my issue of using Basic http Authentication with my web services, and these look like they may be the key. Any help is greatly appreciated. We have added HTTP basic authentication support for axis2/c client. All you have to do is to set the two properties HTTP_AUTH_USERNAME and HTTP_AUTH_PASSWD in your client code. Please refer to echo.c [1] for a sample of its usage. I propose that we remove the AXIS2_USER_NAME and AXIS2_PASSWORD declarations as they are not being used. HTTP authentication related declarations can be found in axis2_http_transport.h. Regards, Dumindu. [1] http://svn.apache.org/viewvc/webservices/axis2/trunk/c/samples/client/echo/echo.c?view=markup - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | http://wso2.com | Oxygenating the Web Service Platform signature.asc Description: OpenPGP digital signature
Re: Differences in SOAP request packets between wsdl2c and wsdl2java -built clients
HI Royston, If the wsdl is changed to element name=getVersion complexType sequence /sequence /complexType /element WSDL2C is generating code that interop with WSDL2Java generated code. (They send the same SOAP) And the code generation with your wsdl is a bug in the WSDL2C templates. Hopefully it will be fixed soon. Thanks Dimuthu On 10/2/07, Royston Day [EMAIL PROTECTED] wrote: Hi all From the same WSDL file, I am seeing a difference in SOAP request packets between c- and java- clients, for Web Service operations which take no request parameters. Furthermore, the SOAP packet generated from the c code does not work, as its soapenv:Body element is empty, as follows... c-code generated request SOAP packet: soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ soapenv:Header/soapenv:Body//soapenv:Envelope java-code generated request SOAP packet: ?xml version='1.0' encoding='UTF-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ soapenv:Bodyns1:getVersion xmlns:ns1= http://localhost/axis/FabricManager; / /soapenv:Body/soapenv:Envelope For operations which take no request parameters, I am defining the type as a named element which contains an empty complexType element. For the SOAP examples above, this looks like: element name=getVersion complexType/ /element I would have thought that clients (c- or java-) generated from the same WSDL file should generate identical SOAP request packets. Is there a (different) way to define a request with no parameters in the wsdl file from which the c-code generation tool (wsdl2c) creates a client which produces the correct SOAP packet? Thanks in advance, Royston - - - Royston Day, Software Engineer MPC Data Limited e-mail: [EMAIL PROTECTED] web: www.mpc-data.co.uk tel: +44 (0) 1225 710600 fax: +44 (0) 1225 710601 ddi: +44 (0) 1225 710634 MPC Data Limited is a company registered in England and Wales with company number 05507446 Registered Address: County Gate, County Way, Trowbridge, Wiltshire, BA14 7FJ VAT no: 850625238 The information in this email and in the attached documents is confidential and may be legally privileged. Any unauthorized review, copying, disclosure or distribution is prohibited and may be unlawful. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. When addressed to our clients any opinions or advice contained in this email is subject to the terms and conditions expressed in the governing contract. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
