[ https://issues.apache.org/jira/browse/AXIS2C-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar updated AXIS2C-1418:
-------------------------------------
Component/s: REST
> HTTP_METHOD DELETE and REST does not work (server returns error 500)
> --------------------------------------------------------------------
>
> Key: AXIS2C-1418
> URL: https://issues.apache.org/jira/browse/AXIS2C-1418
> Project: Axis2-C
> Issue Type: Bug
> Components: REST
> Affects Versions: 1.6.0
> Environment: CentOS 5.1 64 bit
> Reporter: Ilia Gilderman
>
> When http_method set to DELETE and REST is used request fails with error 500 returned
from server.
> The error happens either on echo_rest sample or simple curl request.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar updated AXIS2C-1414:
-------------------------------------
Component/s: util
> Error in length computing in util/url.c
> ---------------------------------------
>
> Key: AXIS2C-1414
> URL: https://issues.apache.org/jira/browse/AXIS2C-1414
> Project: Axis2-C
> Issue Type: Bug
> Components: util
> Reporter: Francois Mireaux
>
> A C string ends with 0 so length computing are erroneous in util/url.c for functions
axutil_url_set_host and axutil_url_get_server : we need to allocate 1 more byte.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar resolved AXIS2C-1409.
--------------------------------------
Resolution: Duplicate
Same issue as AXIS2C-1402
> The AXIS2_PARAM_CHECK macro reset the env status when the param is OK
> ---------------------------------------------------------------------
>
> Key: AXIS2C-1409
> URL: https://issues.apache.org/jira/browse/AXIS2C-1409
> Project: Axis2-C
> Issue Type: Bug
> Components: core/engine
> Reporter: Francois Mireaux
> Assignee: S.Uthaiyashankar
>
> In AXIS2_PARAM_CHECK macro, reseting the env status to OK when the tested parameter is
OK seems not a good thing. Some days ago, the macro was modified to not reset the env status
which leads me to track down some errors (see JIRA AXIS2C-1407 and AXIS2C-1408).
> This day (10/21/2009) the macro resets again the env status but this could conceal real
errors.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar reassigned AXIS2C-1409:
----------------------------------------
Assignee: S.Uthaiyashankar
> The AXIS2_PARAM_CHECK macro reset the env status when the param is OK
> ---------------------------------------------------------------------
>
> Key: AXIS2C-1409
> URL: https://issues.apache.org/jira/browse/AXIS2C-1409
> Project: Axis2-C
> Issue Type: Bug
> Components: core/engine
> Reporter: Francois Mireaux
> Assignee: S.Uthaiyashankar
>
> In AXIS2_PARAM_CHECK macro, reseting the env status to OK when the tested parameter is
OK seems not a good thing. Some days ago, the macro was modified to not reset the env status
which leads me to track down some errors (see JIRA AXIS2C-1407 and AXIS2C-1408).
> This day (10/21/2009) the macro resets again the env status but this could conceal real
errors.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar updated AXIS2C-1412:
-------------------------------------
Component/s: tests
> Very simple unit test framework and tests corrections
> -----------------------------------------------------
>
> Key: AXIS2C-1412
> URL: https://issues.apache.org/jira/browse/AXIS2C-1412
> Project: Axis2-C
> Issue Type: Test
> Components: tests
> Reporter: Francois Mireaux
> Attachments: tests.patch, tests.patch
>
>
> Here is a proposition for a very simple unit test framework, used for rewrite some of
tests (numerous errors found).
> Tests are also modified to be used under Windows (tested with the C compiler of Visual
Studio 2008 Express Edition) with the help of a JScript program which computes a Makefile
extension for tests (file makeTests) analysing files Makefile.am. After executing buid\win32\build.bat,
one can use build\win32\buildtests.bat to build and execute all defined tests. An optionnal
parameter ciould be used to build and execute one specific test defined by test_<nn>
(see makeTests file).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar updated AXIS2C-1409:
-------------------------------------
Component/s: core/engine
> The AXIS2_PARAM_CHECK macro reset the env status when the param is OK
> ---------------------------------------------------------------------
>
> Key: AXIS2C-1409
> URL: https://issues.apache.org/jira/browse/AXIS2C-1409
> Project: Axis2-C
> Issue Type: Bug
> Components: core/engine
> Reporter: Francois Mireaux
>
> In AXIS2_PARAM_CHECK macro, reseting the env status to OK when the tested parameter is
OK seems not a good thing. Some days ago, the macro was modified to not reset the env status
which leads me to track down some errors (see JIRA AXIS2C-1407 and AXIS2C-1408).
> This day (10/21/2009) the macro resets again the env status but this could conceal real
errors.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar updated AXIS2C-1404:
-------------------------------------
Component/s: mtom
> MTOM does not work with CGI installation of Axis
> ------------------------------------------------
>
> Key: AXIS2C-1404
> URL: https://issues.apache.org/jira/browse/AXIS2C-1404
> Project: Axis2-C
> Issue Type: Bug
> Components: mtom
> Environment: $ uname -a
> Linux <hostname> 2.6.18-8.el5 #1 SMP Thu Mar 15 19:46:53 EDT 2007 x86_64 x86_64
x86_64 GNU/Linux
> $ gcc --version
> gcc (GCC) 4.2.2
> Copyright (C) 2007 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> $ ld --version
> GNU ld version 2.17.50.0.6-2.el5 20061020
> Copyright 2005 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms of
> the GNU General Public License. This program has absolutely no warranty.
> Reporter: Russell Tempero
> Attachments: axis2_cgi_main.c.diff
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> When using the the CGI version of Axis, a web service is able to neither receive requests
with MTOM attachments nor send responses with said attachments. The process crashes in either
case.
> I have attached a fix that allows messages with MTOM attachments to be both sent and
received from an Axis2 CGI process. Note that the attached fix works for our current setup
and may not take other configurations into account. It is recommended that further investigation
be made to ensure that the fix works for all cases.
> The first part of the attached patch allows for the receipt of chunked transfer-encoding
HTTP messages. This is not a necessity for MTOM, but is very helpful. The rest of the patch
allows MTOM messages to be sent back out.
> Let me know if there are any questions or concerns or I if I can further assist in any
way.
> Thanks,
> Russell
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar updated AXIS2C-1398:
-------------------------------------
Component/s: core/clientapi
Issue Type: New Feature (was: Bug)
> Add a method to the axis2_options to set mustunderstand attribute to WS-Addressing
> ----------------------------------------------------------------------------------
>
> Key: AXIS2C-1398
> URL: https://issues.apache.org/jira/browse/AXIS2C-1398
> Project: Axis2-C
> Issue Type: New Feature
> Components: core/clientapi
> Environment: Any
> Reporter: Nandika Jayawardana
>
> Currently there isnt a convenient way to set mustunderstand attribute for WS-Addressing
headers from the client api
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar updated AXIS2C-1397:
-------------------------------------
Component/s: transport/http
> HTTPS through proxy does not work for WS client
> -----------------------------------------------
>
> Key: AXIS2C-1397
> URL: https://issues.apache.org/jira/browse/AXIS2C-1397
> Project: Axis2-C
> Issue Type: Bug
> Components: transport/http
> Affects Versions: 1.6.0
> Environment: I have WS client in windows XP machine
> Reporter: Frank Zhou
>
> I have a web service client using axis2/c installed in a windows XP machine. The client
machine is behind a proxy server. The web service provides services that requires use HTTPS/SSL.
> I have set the proxy host and port properly in the configuration file axis2.xml, and
in my case no proxy authentication is needed. The HTTPS/SSL setting is also configured in
axis2.xml. My web service client is still unable to establish connection with the web server.
> I tested that HTTPS/SSL without proxy server is working fine, I also tested that HTTP
(NOT HTTPS) works with proxy server settings.
> Not sure if this is related to the issue JIRA-1312.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar updated AXIS2C-1396:
-------------------------------------
Component/s: xml/om
Affects Version/s: 1.6.0
Issue Type: Improvement (was: Bug)
> When outputting faults, sometimes, it is necessary to namespace qualify text values.
Currently this is not suported in Axis2/C
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2C-1396
> URL: https://issues.apache.org/jira/browse/AXIS2C-1396
> Project: Axis2-C
> Issue Type: Improvement
> Components: xml/om
> Affects Versions: 1.6.0
> Environment: Any
> Reporter: Nandika Jayawardana
>
> When handling Soap faults, it is necessary to qualify the text data with a namespace
prefix.
> Eg.
> <env:Code>
> <env:Value>env:Sender</env:Value>
> <env:Subcode>
> <env:Value>m:MessageTimeout</env:Value>
> </env:Subcode>
> </env:Code>
> For this, it is necessary to have a method to axiom_text_t to set the namespce and that
correct namespace prefix must be appended to the text value serialized
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar updated AXIS2C-1402:
-------------------------------------
Component/s: core/engine
> AXIS2_PARAM_CHECK overwrite previously set error status
> -------------------------------------------------------
>
> Key: AXIS2C-1402
> URL: https://issues.apache.org/jira/browse/AXIS2C-1402
> Project: Axis2-C
> Issue Type: Bug
> Components: core/engine
> Affects Versions: 1.6.0
> Reporter: S.Uthaiyashankar
> Assignee: S.Uthaiyashankar
> Fix For: Next Version
>
> Attachments: axis2_param_check.patch
>
>
> When checking AXIS2_PARAM_CHECK, if it is success, it overwrites STATUS_CODE by setting
AXIS2_ERROR_SET_STATUS_CODE(error, AXIS2_SUCCESS);
> check the macro definition:
> #define AXIS2_PARAM_CHECK(error, object, error_return) \
> if (!object) \
> { \
> AXIS2_ERROR_SET_ERROR_NUMBER(error, AXIS2_ERROR_INVALID_NULL_PARAM); \
> AXIS2_ERROR_SET_STATUS_CODE(error, AXIS2_FAILURE); \
> return error_return; \
> } \
> else \
> { \
> AXIS2_ERROR_SET_STATUS_CODE(error, AXIS2_SUCCESS); \
> }
> Ideally, if PARAM_CHECK is success, it should not touch error status code.
> This macro is a problem when sending soap faults from generated code. To send faults
from generated code, we have to set the error status inside service logic and it will be checked
by the engine to create soap fault. However, after setting error status, there are several
generated codes doing AXIS2_PARAM_CHECK and hence overwriting the status code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar updated AXIS2C-1400:
-------------------------------------
Component/s: transport/http
Fix Version/s: Next Version
> crash with arbitrary rest post data
> -----------------------------------
>
> Key: AXIS2C-1400
> URL: https://issues.apache.org/jira/browse/AXIS2C-1400
> Project: Axis2-C
> Issue Type: Bug
> Components: transport/http
> Affects Versions: 1.6.0
> Environment: Windows XP, Fedora release 11 (Leonidas)
> Reporter: Tamas Martinec
> Priority: Critical
> Fix For: Next Version
>
>
> The echo sample crashes if the post data is empty, or content is not according to the
> text=sometext
> pattern.
> Here are the messages:
> SENDING DATA..
> /* sending time = 23:57:14*/
> /* message uuid = eb01af8d-4d6b-45a3-8bbf-2f80f43acbd2*/
> ---------------------
> POST /axis2/services/echo/echoString HTTP/1.0
> Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel,
application/msword, application/vnd.ms-powerpoint, */*
> Accept-Language: en-us
> Accept-Encoding: gzip, deflate
> User-Agent: Mozilla/4.0
> Content-Length: 6
> Host: LOCALHOST
> Content-Type: application/x-www-form-urlencoded
> text
> RETRIEVING DATA..
> /* retrieving time = 23:57:14*/
> /* time throughput = 0 sec(s)*/
> ---------------------
> HTTP/1.0 500 Internal Server Error
> Date: Thu Sep 24 23:57:14 2009 GMT
> Server: Axis2C/1.6.0 (Simple Axis2 HTTP Server)
> Content-Type: text/html
> Content-Length: 210
> <html><head><title>500 Internal Server Error</title></head><body><h2>Internal
Server Error</h2><p>The server encountered an unexpected condition which prevented
it from fulfilling the request.</p></body></html>
> And the call stack for the crash:
> axis2_engine.dll!axis2_http_status_line_free(axis2_http_status_line * status_line=0xdddddddd,
const axutil_env * env=0x006dd498) Line 143 + 0x3 bytes C
> axis2_engine.dll!axis2_http_simple_response_free(axis2_http_simple_response * simple_response=0x006df500,
const axutil_env * env=0x006dd498) Line 117 C
> axis2_engine.dll!axis2_http_out_transport_info_impl_free(axis2_http_out_transport_info
* http_out_transport_info=0x006de700, const axutil_env * env=0x006dd498) Line 158 C
> axis2_engine.dll!axis2_http_out_transport_info_free(axis2_http_out_transport_info
* http_out_transport_info=0x006de700, const axutil_env * env=0x006dd498) Line 206 + 0x12
bytes C
> axis2_engine.dll!axis2_out_transport_info_impl_free(axis2_out_transport_info * out_transport_info=0x006de700,
const axutil_env * env=0x006dd498) Line 61 C
> axis2_engine.dll!axis2_msg_ctx_free(axis2_msg_ctx * msg_ctx=0x006dfa38, const axutil_env
* env=0x006dd498) Line 444 + 0x20 bytes C
> axis2_engine.dll!axis2_http_worker_process_request(axis2_http_worker * http_worker=0x006dc350,
const axutil_env * env=0x006dd498, axis2_simple_http_svr_conn * svr_conn=0x006dd4e0, axis2_http_simple_request
* simple_request=0x006e0b18) Line 2009 C
> axis2_http_receiver.dll!axis2_svr_thread_worker_func(axutil_thread_t * thd=0x006df870,
void * data=0x006dc608) Line 260 + 0x18 bytes C
> axutil.dll!dummy_worker(void * opaque=0x006df870) Line 88 + 0x15 bytes C
> kernel32.dll!7c80b729()
> [Frames below may be incorrect and/or missing, no symbols loaded for kernel32.dll]
> Seems like axis2_http_status_line_free wants to free something already freed..
> And this is the end of the log:
> [Thu Sep 24 23:57:14 2009] [debug] c:\axis2c-repo\src\core\transport\http\common\http_worker.c(200)
Client HTTP version HTTP/1.0
> [Thu Sep 24 23:57:14 2009] [debug] c:\axis2c-repo\src\core\engine\rest_disp.c(114) Checking
for service using target endpoint address : http://127.0.0.1:9090/axis2/services/echo/echoString
> [Thu Sep 24 23:57:14 2009] [debug] c:\axis2c-repo\src\core\engine\rest_disp.c(135) Service
found using target endpoint address
> [Thu Sep 24 23:57:14 2009] [debug] c:\axis2c-repo\src\core\util\core_utils.c(772) Checking
for operation using REST HTTP Location fragment : /echoString
> [Thu Sep 24 23:57:14 2009] [debug] c:\axis2c-repo\src\core\util\core_utils.c(834) Operation
found using target endpoint uri fragment
> [Thu Sep 24 23:57:14 2009] [debug] c:\axis2c-repo\src\core\engine\phase.c(210) Invoke
the handler request_uri_based_dispatcher within the phase Transport
> [Thu Sep 24 23:57:14 2009] [debug] c:\axis2c-repo\src\core\engine\phase.c(210) Invoke
the handler AddressingInHandler within the phase Transport
> [Thu Sep 24 23:57:14 2009] [info] Starting addressing in handler
> [Thu Sep 24 23:57:14 2009] [info] c:\axis2c-repo\src\modules\mod_addr\addr_in_handler.c
> [Thu Sep 24 23:57:14 2009] [debug] c:\axis2c-repo\src\core\engine\phase.c(210) Invoke
the handler addressing_based_dispatcher within the phase Transport
> [Thu Sep 24 23:57:14 2009] [debug] c:\axis2c-repo\src\core\engine\phase.c(210) Invoke
the handler rest_dispatcher within the phase Dispatch
> [Thu Sep 24 23:57:14 2009] [debug] c:\axis2c-repo\src\core\engine\phase.c(210) Invoke
the handler soap_message_body_based_dispatcher within the phase Dispatch
> [Thu Sep 24 23:57:14 2009] [debug] c:\axis2c-repo\src\core\engine\phase.c(210) Invoke
the handler soap_action_based_dispatcher within the phase Dispatch
> [Thu Sep 24 23:57:14 2009] [debug] c:\axis2c-repo\src\core\engine\phase.c(210) Invoke
the handler dispatch_post_conditions_evaluator within the phase PostDispatch
> [Thu Sep 24 23:57:14 2009] [debug] c:\axis2c-repo\src\core\engine\phase.c(210) Invoke
the handler context_handler within the phase PostDispatch
> [Thu Sep 24 23:57:14 2009] [debug] c:\axis2c-repo\src\core\receivers\raw_xml_in_out_msg_recv.c(382)
fault_detail:<Detail></Detail>
> This post describes the same issue under linux:
> http://www.mail-archive.com/axis-c-dev@ws.apache.org/msg16788.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar updated AXIS2C-1371:
-------------------------------------
Fix Version/s: Next Version
Assignee: S.Uthaiyashankar
> Axis should log libcurl debug information
> -----------------------------------------
>
> Key: AXIS2C-1371
> URL: https://issues.apache.org/jira/browse/AXIS2C-1371
> Project: Axis2-C
> Issue Type: Improvement
> Components: transport/http
> Affects Versions: 1.6.0
> Reporter: Incarnadine
> Assignee: S.Uthaiyashankar
> Priority: Minor
> Fix For: Next Version
>
> Attachments: EnableLibcurlLogging.diff
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> It is difficult to debug the libcurl transport today because Axis2/C doesn't enable libcurl
debug logging. I'll attach a patch which does this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar updated AXIS2C-1372:
-------------------------------------
Fix Version/s: Next Version
Assignee: S.Uthaiyashankar
> Setting the content-length header for libcurl causes auth to fail
> -----------------------------------------------------------------
>
> Key: AXIS2C-1372
> URL: https://issues.apache.org/jira/browse/AXIS2C-1372
> Project: Axis2-C
> Issue Type: Bug
> Components: transport/http
> Affects Versions: 1.6.0
> Reporter: Incarnadine
> Assignee: S.Uthaiyashankar
> Priority: Blocker
> Fix For: Next Version
>
> Attachments: RemoveContentLengthHeader.diff
>
> Original Estimate: 0.08h
> Remaining Estimate: 0.08h
>
> Certain auth schemes, like NTLM, may result in an empty request (no body, content-length:0)
being sent to the server first to trigger a 401 auth challenge so as not to waste bandwidth
by posting the real message body twice when it knows the first request will result in an auth
challenge.
> Libcurl currently has a bug where it will use the specified content-length on this first
request instead of sending 0, which will cause subsequent requests to fail because the message
body was never sent.
> Since libcurl automatically calculates the content-length based on the POST size, it's
not necessary to specify it from Axis2/C. Removing this header allows libcurl to calculate
the length and send the correct values during both requests.
> I recommend the content-length setting code be removed because:
> 1. It doesn't appear to be needed
> 2. Curl docs do not recommend specifying a content-length header
> 3. It's currently the only way to get NTLM authentication working (see AXIS2C-1370)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar updated AXIS2C-1370:
-------------------------------------
Fix Version/s: Next Version
Assignee: S.Uthaiyashankar
> Axis should support libcurl's other auth types (not just basic)
> ---------------------------------------------------------------
>
> Key: AXIS2C-1370
> URL: https://issues.apache.org/jira/browse/AXIS2C-1370
> Project: Axis2-C
> Issue Type: Improvement
> Components: transport/http
> Affects Versions: 1.6.0
> Reporter: Incarnadine
> Assignee: S.Uthaiyashankar
> Fix For: Next Version
>
> Attachments: axis2_libcurl.c.diff, axis2c-1370.diff, options.c.diff
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Looking over axis2_libcurl_set_auth_options() I see it only allows basic auth.
> if (auth_type &&
> 0 == axutil_strcmp(auth_type, AXIS2_HTTP_AUTH_TYPE_BASIC))
> {
> curl_easy_setopt(handler, CURLOPT_HTTPAUTH, CURLAUTH_BASIC);
> }
> else
> {
> /* Uses anonymous connection.*/
> }
> If new schemes can be enabled as easily as mapping Axis options to Libcurl, this would
appear to be an easy fix. Other supported values to be mapped include:
> CURLAUTH_BASIC
> HTTP Basic authentication. This is the default choice, and the only method that is in
wide-spread use and supported virtually everywhere. This is sending the user name and password
over the network in plain text, easily captured by others.
> CURLAUTH_DIGEST
> HTTP Digest authentication. Digest authentication is defined in RFC2617 and is a more
secure way to do authentication over public networks than the regular old-fashioned Basic
method.
> CURLAUTH_GSSNEGOTIATE
> HTTP GSS-Negotiate authentication. The GSS-Negotiate (also known as plain "Negotiate")
method was designed by Microsoft and is used in their web applications. It is primarily meant
as a support for Kerberos5 authentication but may be also used along with another authentication
methods. For more information see IETF draft draft-brezak-spnego-http-04.txt.
> You need to build libcurl with a suitable GSS-API library for this to work.
> CURLAUTH_NTLM
> HTTP NTLM authentication. A proprietary protocol invented and used by Microsoft. It uses
a challenge-response and hash concept similar to Digest, to prevent the password from being
eavesdropped.
> You need to build libcurl with OpenSSL support for this option to work, or build libcurl
on Windows.
> CURLAUTH_ANY
> This is a convenience macro that sets all bits and thus makes libcurl pick any it finds
suitable. libcurl will automatically select the one it finds most secure.
> CURLAUTH_ANYSAFE
> This is a convenience macro that sets all bits except Basic and thus makes libcurl pick
any it finds suitable. libcurl will automatically select the one it finds most secure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar resolved AXIS2C-1235.
--------------------------------------
Resolution: Fixed
Fixed in revision 888696.
Thank you very much for the patch
> Need a way to specify libcurl options
> -------------------------------------
>
> Key: AXIS2C-1235
> URL: https://issues.apache.org/jira/browse/AXIS2C-1235
> Project: Axis2-C
> Issue Type: New Feature
> Components: transport/http
> Affects Versions: Current (Nightly)
> Reporter: ttg
> Assignee: S.Uthaiyashankar
> Fix For: Next Version
>
> Attachments: axis2c-1235.txt
>
>
> I need some way to specify additional options for libcurl, but at the moment there is
no way to access the CURL* handler.
> For example I want the client to connect via SOCKS5 proxy with authorization, increase
connection timeouts and make it not complain about self-signed SSL certificates. Here is the
list of libcurl options I would use:
> curl_easy_setopt(handler, CURLOPT_PROXY, proxy);
> curl_easy_setopt(handler, CURLOPT_PROXYPORT, port);
> curl_easy_setopt(handler, CURLOPT_PROXYTYPE, type);
> curl_easy_setopt(handler, CURLOPT_PROXYAUTH, CURLAUTH_ANY);
> curl_easy_setopt(handler, CURLOPT_PROXYUSERPWD, userpwd);
> curl_easy_setopt(handler, CURLOPT_TIMEOUT, timeout);
> curl_easy_setopt(handler, CURLOPT_CONNECTTIMEOUT, 10);
> curl_easy_setopt(handler, CURLOPT_SSL_VERIFYHOST, 0);
> curl_easy_setopt(handler, CURLOPT_SSL_VERIFYPEER, 0);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar resolved AXIS2C-1416.
--------------------------------------
Resolution: Fixed
Fixed in revision 888691.
Thank you Russell Tempero for the patch.
> type in svc_builder.c
> ---------------------
>
> Key: AXIS2C-1416
> URL: https://issues.apache.org/jira/browse/AXIS2C-1416
> Project: Axis2-C
> Issue Type: Bug
> Components: core/deployment
> Affects Versions: 1.6.0
> Environment: $ gcc --version
> gcc (GCC) 4.2.2
> Copyright (C) 2007 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> $ ld --version
> GNU ld version 2.17.50.0.6-2.el5 20061020
> Copyright 2005 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms of
> the GNU General Public License. This program has absolutely no warranty.
> $ uname -a
> Linux <hostname> 2.6.18-8.el5 #1 SMP Thu Mar 15 19:46:53 EDT 2007 x86_64 x86_64
x86_64 GNU/Linux
> Reporter: Russell Tempero
> Assignee: S.Uthaiyashankar
> Priority: Minor
> Fix For: Next Version
>
> Attachments: svc_builder.c.diff
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> While tromping around the Axis code tree I noticed a typo for which I have attached a
patch. I never actually noticed any problems associated with this typo, but I figured it might
be good to fix it anyway.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar reassigned AXIS2C-1416:
----------------------------------------
Assignee: S.Uthaiyashankar
> type in svc_builder.c
> ---------------------
>
> Key: AXIS2C-1416
> URL: https://issues.apache.org/jira/browse/AXIS2C-1416
> Project: Axis2-C
> Issue Type: Bug
> Components: core/deployment
> Affects Versions: 1.6.0
> Environment: $ gcc --version
> gcc (GCC) 4.2.2
> Copyright (C) 2007 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> $ ld --version
> GNU ld version 2.17.50.0.6-2.el5 20061020
> Copyright 2005 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms of
> the GNU General Public License. This program has absolutely no warranty.
> $ uname -a
> Linux <hostname> 2.6.18-8.el5 #1 SMP Thu Mar 15 19:46:53 EDT 2007 x86_64 x86_64
x86_64 GNU/Linux
> Reporter: Russell Tempero
> Assignee: S.Uthaiyashankar
> Priority: Minor
> Fix For: Next Version
>
> Attachments: svc_builder.c.diff
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> While tromping around the Axis code tree I noticed a typo for which I have attached a
patch. I never actually noticed any problems associated with this typo, but I figured it might
be good to fix it anyway.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar updated AXIS2C-1416:
-------------------------------------
Component/s: core/deployment
Fix Version/s: Next Version
> type in svc_builder.c
> ---------------------
>
> Key: AXIS2C-1416
> URL: https://issues.apache.org/jira/browse/AXIS2C-1416
> Project: Axis2-C
> Issue Type: Bug
> Components: core/deployment
> Affects Versions: 1.6.0
> Environment: $ gcc --version
> gcc (GCC) 4.2.2
> Copyright (C) 2007 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> $ ld --version
> GNU ld version 2.17.50.0.6-2.el5 20061020
> Copyright 2005 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms of
> the GNU General Public License. This program has absolutely no warranty.
> $ uname -a
> Linux <hostname> 2.6.18-8.el5 #1 SMP Thu Mar 15 19:46:53 EDT 2007 x86_64 x86_64
x86_64 GNU/Linux
> Reporter: Russell Tempero
> Assignee: S.Uthaiyashankar
> Priority: Minor
> Fix For: Next Version
>
> Attachments: svc_builder.c.diff
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> While tromping around the Axis code tree I noticed a typo for which I have attached a
patch. I never actually noticed any problems associated with this typo, but I figured it might
be good to fix it anyway.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
On Fri, Dec 4, 2009 at 11:13 PM, Samisa Abeysinghe <samisa@wso2.com> wrote: > I meant to say, Axis2! > Samisa... > > On Fri, Dec 4, 2009 at 11:08 PM, Samisa Abeysinghe <samisa@wso2.com> wrote: >> >> Folks, >> I looked at the Jiras after a loooong time and seems that there are >> quite a number of them as well as few ones with patches from users. >> May be it is a good time to fire up a new release. Thoughts are >> welcome. +1. I'll go through the Jira and fix them. What will be the version number? 1.7.0? Regards, Shankar >> Thanks, >> Samisa... >> -- >> Samisa Abeysinghe >> Director, Engineering - WSO2 Inc. >> >> http://www.wso2.com/ - "The Open Source SOA Company" > > > > -- > Samisa Abeysinghe > Director, Engineering - WSO2 Inc. > > http://www.wso2.com/ - "The Open Source SOA Company" > -- S.Uthaiyashankar Software Architect WSO2 Inc. http://wso2.com/ - "The Open Source SOA Company"
HTTP_METHOD DELETE and REST does not work (server returns error 500)
--------------------------------------------------------------------
Key: AXIS2C-1418
URL: https://issues.apache.org/jira/browse/AXIS2C-1418
Project: Axis2-C
Issue Type: Bug
Affects Versions: 1.6.0
Environment: CentOS 5.1 64 bit
Reporter: Ilia Gilderman
When http_method set to DELETE and REST is used request fails with error 500 returned from
server.
The error happens either on echo_rest sample or simple curl request.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
I meant to say, Axis2! Samisa... On Fri, Dec 4, 2009 at 11:08 PM, Samisa Abeysinghe <samisa@wso2.com> wrote: > Folks, > I looked at the Jiras after a loooong time and seems that there are > quite a number of them as well as few ones with patches from users. > > May be it is a good time to fire up a new release. Thoughts are > welcome. > > Thanks, > Samisa... > > -- > Samisa Abeysinghe > Director, Engineering - WSO2 Inc. > > http://www.wso2.com/ - "The Open Source SOA Company" > -- Samisa Abeysinghe Director, Engineering - WSO2 Inc. http://www.wso2.com/ - "The Open Source SOA Company"
Folks,
I looked at the Jiras after a loooong time and seems that there are
quite a number of them as well as few ones with patches from users.
May be it is a good time to fire up a new release. Thoughts are welcome.
Thanks,
Samisa...
--
Samisa Abeysinghe
Director, Engineering - WSO2 Inc.
http://www.wso2.com/ - "The Open Source SOA Company"
This is not a problem, in Axis2/C, I guess. Samisa... On Thu, Oct 29, 2009 at 7:12 PM, Nair, Anushree <anushree.nair@hp.com>wrote: > Hello, > > > > When SOAPAction is not set, SOAP1.1 requests are assumed to be REST > invocations by Axis2/C. > > This problem has been reported earlier in JIRA WSFPHP-42( > http://www.wso2.org/jira/browse/WSFPHP-42?page=all) which is resolved. > > Can anyone tell me which version onwards is the fix for this problem > available? > > > > Regards, > > Anushree >
Thanks, Dinesh. After poking around a bit, I think it is under branches: http://svn.apache.org/viewvc/webservices/axis2/branches/c/1.6.x/1.6.0/c/ Revision: r765550 Thanks, -Dave. On Mon, Nov 30, 2009 at 5:00 PM, Dinesh Premalal <xydinesh@gmail.com> wrote: > Hi, Dave, > > It should be here [1] however I can not find a tag for Axis2/C > 1.6.0 . Release manager might have changed the location. > > Dinesh. > > 1. http://svn.apache.org/viewvc/webservices/axis2/tags/c/ > > Dave Meier <dmeier@serena.com> writes: > > > Hi, > > > > I've used axis2/c in the past but not released anything with it. I now > plan to > > use the last stable release (1.6). I would like to know the SVN version > number > > that corresponds to version 1.6. Can you tell me what it is? I think I > used > > to browse the web interface for SVN and look in tags, but I don't see > tags > > anymore. Are releases labeled (tagged)? I want to work with the 1.6 > version, > > but be able to quickly diff any changes I make against 1.6 source files > by > > using svn diff at the root directory of the source. > > > > Thanks, > > > > -Dave. >
Hi, Dave,
It should be here [1] however I can not find a tag for Axis2/C
1.6.0 . Release manager might have changed the location.
Dinesh.
1. http://svn.apache.org/viewvc/webservices/axis2/tags/c/
Dave Meier <dmeier@serena.com> writes:
> Hi,
>
> I've used axis2/c in the past but not released anything with it. I now plan to
> use the last stable release (1.6). I would like to know the SVN version number
> that corresponds to version 1.6. Can you tell me what it is? I think I used
> to browse the web interface for SVN and look in tags, but I don't see tags
> anymore. Are releases labeled (tagged)? I want to work with the 1.6 version,
> but be able to quickly diff any changes I make against 1.6 source files by
> using svn diff at the root directory of the source.
>
> Thanks,
>
> -Dave.
Hi, I've used axis2/c in the past but not released anything with it. I now plan to use the last stable release (1.6). I would like to know the SVN version number that corresponds to version 1.6. Can you tell me what it is? I think I used to browse the web interface for SVN and look in tags, but I don't see tags anymore. Are releases labeled (tagged)? I want to work with the 1.6 version, but be able to quickly diff any changes I make against 1.6 source files by using svn diff at the root directory of the source. Thanks, -Dave.
[ https://issues.apache.org/jira/browse/AXIS2C-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Russell Tempero updated AXIS2C-1417:
------------------------------------
Attachment: axis_changes.diff
Here are the changes that we made to support our desired functionality.
> ability to add an MTOM sending callback without requiring a module
> ------------------------------------------------------------------
>
> Key: AXIS2C-1417
> URL: https://issues.apache.org/jira/browse/AXIS2C-1417
> Project: Axis2-C
> Issue Type: New Feature
> Components: mtom
> Affects Versions: 1.6.0
> Environment: $ gcc --version
> gcc (GCC) 4.2.2
> Copyright (C) 2007 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> $ ld --version
> GNU ld version 2.17.50.0.6-2.el5 20061020
> Copyright 2005 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms of
> the GNU General Public License. This program has absolutely no warranty.
> $ uname -a
> Linux <hostname> 2.6.18-8.el5 #1 SMP Thu Mar 15 19:46:53 EDT 2007 x86_64 x86_64
x86_64 GNU/Linux
> Reporter: Russell Tempero
> Attachments: axis_changes.diff
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> We wanted to be able to specify our own set of functions for reading file data which
is currently supported in Axis2 via sending callback modules. However, we did not want the
inefficiency associated with loading another dynamic library. Our solution was to alter the
Axis code to allow us to achieve the same functionality by only passing a few function pointers.
> Note that we also added support for using the callback handlers to send file attachments
as non-MTOM (base-64 encoded) data. See changes to data_handler.c.
> Some suggested further changes:
> - add a case to axiom_data_handler_read_from() for AXIOM_DATA_HANDLER_TYPE_CALLBACK that
works similarly to my addition for AXIOM_DATA_HANDLER_TYPE_HANDLER. This will allow traditional
call back handlers (those loaded via a module) can be used to send non-MTOM data.
> - alter axiom_data_handler_read_from() to work even if the "data_size" function is not
specified. My idea was to check if this function is not specified or if it returns some special
value (i.e. a negative number). If so, a much less efficient, brute-force method could be
employed to determine the size of the data. One way would be to iterate once through the data,
only counting the size and throwing away the actual data. Then create a buffer of the proper
size and iterate a second time through the data while filling the buffer.
> Hopefully this patch is useful.
> Thanks,
> Russell
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
ability to add an MTOM sending callback without requiring a module
------------------------------------------------------------------
Key: AXIS2C-1417
URL: https://issues.apache.org/jira/browse/AXIS2C-1417
Project: Axis2-C
Issue Type: New Feature
Components: mtom
Affects Versions: 1.6.0
Environment: $ gcc --version
gcc (GCC) 4.2.2
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ ld --version
GNU ld version 2.17.50.0.6-2.el5 20061020
Copyright 2005 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License. This program has absolutely no warranty.
$ uname -a
Linux <hostname> 2.6.18-8.el5 #1 SMP Thu Mar 15 19:46:53 EDT 2007 x86_64 x86_64 x86_64
GNU/Linux
Reporter: Russell Tempero
Attachments: axis_changes.diff
We wanted to be able to specify our own set of functions for reading file data which is currently
supported in Axis2 via sending callback modules. However, we did not want the inefficiency
associated with loading another dynamic library. Our solution was to alter the Axis code to
allow us to achieve the same functionality by only passing a few function pointers.
Note that we also added support for using the callback handlers to send file attachments as
non-MTOM (base-64 encoded) data. See changes to data_handler.c.
Some suggested further changes:
- add a case to axiom_data_handler_read_from() for AXIOM_DATA_HANDLER_TYPE_CALLBACK that works
similarly to my addition for AXIOM_DATA_HANDLER_TYPE_HANDLER. This will allow traditional
call back handlers (those loaded via a module) can be used to send non-MTOM data.
- alter axiom_data_handler_read_from() to work even if the "data_size" function is not specified.
My idea was to check if this function is not specified or if it returns some special value
(i.e. a negative number). If so, a much less efficient, brute-force method could be employed
to determine the size of the data. One way would be to iterate once through the data, only
counting the size and throwing away the actual data. Then create a buffer of the proper size
and iterate a second time through the data while filling the buffer.
Hopefully this patch is useful.
Thanks,
Russell
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
type in svc_builder.c
---------------------
Key: AXIS2C-1416
URL: https://issues.apache.org/jira/browse/AXIS2C-1416
Project: Axis2-C
Issue Type: Bug
Affects Versions: 1.6.0
Environment: $ gcc --version
gcc (GCC) 4.2.2
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ ld --version
GNU ld version 2.17.50.0.6-2.el5 20061020
Copyright 2005 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License. This program has absolutely no warranty.
$ uname -a
Linux <hostname> 2.6.18-8.el5 #1 SMP Thu Mar 15 19:46:53 EDT 2007 x86_64 x86_64 x86_64
GNU/Linux
Reporter: Russell Tempero
Priority: Minor
Attachments: svc_builder.c.diff
While tromping around the Axis code tree I noticed a typo for which I have attached a patch.
I never actually noticed any problems associated with this typo, but I figured it might be
good to fix it anyway.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Russell Tempero updated AXIS2C-1416:
------------------------------------
Attachment: svc_builder.c.diff
Attaching patch for typo in svc_builder.c
> type in svc_builder.c
> ---------------------
>
> Key: AXIS2C-1416
> URL: https://issues.apache.org/jira/browse/AXIS2C-1416
> Project: Axis2-C
> Issue Type: Bug
> Affects Versions: 1.6.0
> Environment: $ gcc --version
> gcc (GCC) 4.2.2
> Copyright (C) 2007 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> $ ld --version
> GNU ld version 2.17.50.0.6-2.el5 20061020
> Copyright 2005 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms of
> the GNU General Public License. This program has absolutely no warranty.
> $ uname -a
> Linux <hostname> 2.6.18-8.el5 #1 SMP Thu Mar 15 19:46:53 EDT 2007 x86_64 x86_64
x86_64 GNU/Linux
> Reporter: Russell Tempero
> Priority: Minor
> Attachments: svc_builder.c.diff
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> While tromping around the Axis code tree I noticed a typo for which I have attached a
patch. I never actually noticed any problems associated with this typo, but I figured it might
be good to fix it anyway.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Buffer overrun in axis2_http_client_recieve_header when receiving a HTTP header field larger
than 512 bytes in length.
----------------------------------------------------------------------------------------------------------------------
Key: AXIS2C-1415
URL: https://issues.apache.org/jira/browse/AXIS2C-1415
Project: Axis2-C
Issue Type: Bug
Components: transport/http
Affects Versions: 1.6.0
Environment: Windows XP SP2, Axis2/C compiled with Visual Studio 2008 SP1
Reporter: Nigel Meachen
A buffer overrun occurs in axis2_http_client_recieve_header when a HTTP header field larger
than 512 bytes is received resulting in stack corruption and in my case causes the client
to loop forever.
In my scenario I was using the Axis2/C 1.6 client to invoke a RESTful service using Basic
Authentication running on a Websphere 7 environment. Upon successful authentication the response
HTTP header contains a Set-Cookie field totaling 760 bytes.
I was able to work around this issue by doubling the size of the str_header field and modifying
the memset reference to use sizeof avoiding the need to modify thm in the future if the size
changes again. The module at the least should keep track of the accumulated header field size
to avoid overruns in the future but ideally should dynamically allocate memory to cope with
any size header field.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Error in length computing in util/url.c
---------------------------------------
Key: AXIS2C-1414
URL: https://issues.apache.org/jira/browse/AXIS2C-1414
Project: Axis2-C
Issue Type: Bug
Reporter: Francois Mireaux
A C string ends with 0 so length computing are erroneous in util/url.c for functions axutil_url_set_host
and axutil_url_get_server : we need to allocate 1 more byte.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francois Mireaux updated AXIS2C-1412:
-------------------------------------
Attachment: tests.patch
Improvement of test mini-framework & usage in tests.
Please, comment !
> Very simple unit test framework and tests corrections
> -----------------------------------------------------
>
> Key: AXIS2C-1412
> URL: https://issues.apache.org/jira/browse/AXIS2C-1412
> Project: Axis2-C
> Issue Type: Test
> Reporter: Francois Mireaux
> Attachments: tests.patch, tests.patch
>
>
> Here is a proposition for a very simple unit test framework, used for rewrite some of
tests (numerous errors found).
> Tests are also modified to be used under Windows (tested with the C compiler of Visual
Studio 2008 Express Edition) with the help of a JScript program which computes a Makefile
extension for tests (file makeTests) analysing files Makefile.am. After executing buid\win32\build.bat,
one can use build\win32\buildtests.bat to build and execute all defined tests. An optionnal
parameter ciould be used to build and execute one specific test defined by test_<nn>
(see makeTests file).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779429#action_12779429
]
Francois Mireaux commented on AXIS2C-1413:
------------------------------------------
Those functions are only used in tests so correction isn't so critical !
> Windows version axutil_thread_once_init don't initialize control struct
> -----------------------------------------------------------------------
>
> Key: AXIS2C-1413
> URL: https://issues.apache.org/jira/browse/AXIS2C-1413
> Project: Axis2-C
> Issue Type: Bug
> Components: platforms/windows
> Environment: Windows
> Reporter: Francois Mireaux
> Priority: Critical
>
> On Windows 'axutil_thread_once_init' don't initialize control struct so value may have
random value and 'axutil_thread_once' never calls parameter function.
> We must add :
> if (control)
> {
> control->value = 0;
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779396#action_12779396
]
Francois Mireaux commented on AXIS2C-1413:
------------------------------------------
Sorry, I forget to say that error was dtected on Windows Vista with Visual Studio 2008 Express
Edition C compiler.
> Windows version axutil_thread_once_init don't initialize control struct
> -----------------------------------------------------------------------
>
> Key: AXIS2C-1413
> URL: https://issues.apache.org/jira/browse/AXIS2C-1413
> Project: Axis2-C
> Issue Type: Bug
> Components: platforms/windows
> Environment: Windows
> Reporter: Francois Mireaux
> Priority: Critical
>
> On Windows 'axutil_thread_once_init' don't initialize control struct so value may have
random value and 'axutil_thread_once' never calls parameter function.
> We must add :
> if (control)
> {
> control->value = 0;
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Windows version axutil_thread_once_init don't initialize control struct
-----------------------------------------------------------------------
Key: AXIS2C-1413
URL: https://issues.apache.org/jira/browse/AXIS2C-1413
Project: Axis2-C
Issue Type: Bug
Components: platforms/windows
Environment: Windows
Reporter: Francois Mireaux
Priority: Critical
On Windows 'axutil_thread_once_init' don't initialize control struct so value may have random
value and 'axutil_thread_once' never calls parameter function.
We must add :
if (control)
{
control->value = 0;
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/AXIS2C-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francois Mireaux updated AXIS2C-1412:
-------------------------------------
Attachment: tests.patch
Caution, patch also contains a bug correction in util\url.c.
Two include files are defined in cutest\include to write tests :
tunit.h : simple macros and functions
ut_http_server.h : help function to start and stop a thread executing HTTP server (on
Unix needs the patch proposed in JIRA-1411)
Windows JScript program (genmktests.js) is a bit of mish-mash but seems to be the only solution
as libraries structure and names are not the same on Unix and Windows.
The first test failure aborts test processing which is arguable but permits a simple error
detection without reading log files.
I could go on working on rewrite and extend tests : some failures don't stop tests, some tests
don't really check that all is right... But I need to know if general principles are OK.
> Very simple unit test framework and tests corrections
> -----------------------------------------------------
>
> Key: AXIS2C-1412
> URL: https://issues.apache.org/jira/browse/AXIS2C-1412
> Project: Axis2-C
> Issue Type: Test
> Reporter: Francois Mireaux
> Attachments: tests.patch
>
>
> Here is a proposition for a very simple unit test framework, used for rewrite some of
tests (numerous errors found).
> Tests are also modified to be used under Windows (tested with the C compiler of Visual
Studio 2008 Express Edition) with the help of a JScript program which computes a Makefile
extension for tests (file makeTests) analysing files Makefile.am. After executing buid\win32\build.bat,
one can use build\win32\buildtests.bat to build and execute all defined tests. An optionnal
parameter ciould be used to build and execute one specific test defined by test_<nn>
(see makeTests file).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Very simple unit test framework and tests corrections
-----------------------------------------------------
Key: AXIS2C-1412
URL: https://issues.apache.org/jira/browse/AXIS2C-1412
Project: Axis2-C
Issue Type: Test
Reporter: Francois Mireaux
Here is a proposition for a very simple unit test framework, used for rewrite some of tests
(numerous errors found).
Tests are also modified to be used under Windows (tested with the C compiler of Visual Studio
2008 Express Edition) with the help of a JScript program which computes a Makefile extension
for tests (file makeTests) analysing files Makefile.am. After executing buid\win32\build.bat,
one can use build\win32\buildtests.bat to build and execute all defined tests. An optionnal
parameter ciould be used to build and execute one specific test defined by test_<nn>
(see makeTests file).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Hi, I try to get the target endpoint address in a services in Axis2c, I put the following code
in the invoke function in the skeleton library:
axis2_endpoint_ref_t *endpoint_ref = NULL;
const axis2_char_t *address = NULL;
.
.
.
endpoint_ref = axis2_msg_ctx_get_to(msg_ctx, env);
if(endpoint_ref)
{
AXIS2_LOG_DEBUG(env->log, AXIS2_LOG_SI, "%s%s if(endpoint_ref)",pdesWebServ->nombre_web,nombreFuncion);
address = axis2_endpoint_ref_get_address(endpoint_ref, env);
if (address)
{
AXIS2_LOG_DEBUG(env->log, AXIS2_LOG_SI, "%s%s if (address)",pdesWebServ->nombre_web,nombreFuncion);
}
}
When I run this, I got NULL in endpoint_ref variable, so I don’t know it was something wrong
with this code.
It is the correct way to get the endpoint address or exists another way to get that info.
Thank in advance.
------------------------------------------------------------
José M. Medina V.
Wesam Consulting
jose_medina@wesamconsulting.com
Mobile: +58(416)613-3302 +58(414)019-0580
Ofc: +58(212)959-4155 Ext. 204
BB pin: 31E562BF
Caracas - Venezuela