Re: [Vote 2] [Axis2] Vote for Apache Axis2/C 1.0.0 Release
Tested both linux/win32 sources for SSL client. It works fine. +1 for the release. Thanks, Dumindu. Samisa Abeysinghe wrote: Hi Devs, After fixing the issues found with the initial release artifacts, I have re-packaged and uploaded the Apache Axis2/C 1.0.0 release artifacts at http://people.apache.org/~samisa/release/1.0.0/final/ The key used to sign the release artifacts can be found at http://www.apache.org/dist/ws/axis2/c/KEYS Please test, review and vote on these latest release artifacts for Apache Axis2/C 1.0.0 release. I have tested and reviewed them and here is my vote: +1 Thanks, Samisa... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote 2] [Axis2] Vote for Apache Axis2/C 1.0.0 Release
Samisa Abeysinghe wrote: >Please test, review and vote on these latest release artifacts for > Apache Axis2/C 1.0.0 release. Compiles, tests, and installs like a charm -- thank you! I've run axis2_http_server and pinged the sample clients off it. I also quickly tried mod_axis2 with httpd 2.2.3 and the samples worked there too. So, +1 from me, and thanks again, Chris. -- GPG Key ID: 366A375B GPG Key Fingerprint: 485E 5041 17E1 E2BB C263 E4DE C8E3 FA36 366A 375B - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
empty Values in Soap document produces an error
Hi ,
I have a problem with my webservice. He receive an Soap Document, with
the following structure You find it at the end of the Mail(for example).
If AXIS reads the password of the Auth object, occurs an error and the
Auth object won't prepared. The problem is that the text_value is emty
and AXIS don't understand this. I have change my Source Code of the
axiom_element_get_text Method to: if(om_element->text_value == NULL )
om_element->text_value = ""; It works, but i don't know have it effect
of the rest of AXIS2C. Can someone check it this okay. If yes, can it
included in the source code of AXIS2? The same problem is by
axutil_array_list_size. My example is after the SOAP Document.
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing";
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wsse
curity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-
open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
urn:uuid:7b21bdf8-6f69-44a1-b44c-cde2d1ffa8ff
http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anony
mous
http://localhost:9090/axis2/services/ttwebservicesaxis
2007-05-03T08:40:48Z
2007-05-03T08:45:48Z
bill
AXIS2_EXTERN int AXIS2_CALL
axutil_array_list_size(struct axutil_array_list *array_list,
const axutil_env_t *env)
{
AXIS2_ENV_CHECK(env, AXIS2_FAILURE);
if(array_list == NULL)
return 0;
return array_list->size;
}
Regards Lars
Re: [Vote 2] [Axis2] Vote for Apache Axis2/C 1.0.0 Release
Tested and reviewed on Linux. Here is my +1. Thanks ~sanjaya Samisa Abeysinghe wrote: Hi Devs, After fixing the issues found with the initial release artifacts, I have re-packaged and uploaded the Apache Axis2/C 1.0.0 release artifacts at http://people.apache.org/~samisa/release/1.0.0/final/ The key used to sign the release artifacts can be found at http://www.apache.org/dist/ws/axis2/c/KEYS Please test, review and vote on these latest release artifacts for Apache Axis2/C 1.0.0 release. I have tested and reviewed them and here is my vote: +1 Thanks, Samisa... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (AXIS2C-510) Integrate security policy with rampart
[ https://issues.apache.org/jira/browse/AXIS2C-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Malinda Kaushalye Kapuruge closed AXIS2C-510. - > Integrate security policy with rampart > -- > > Key: AXIS2C-510 > URL: https://issues.apache.org/jira/browse/AXIS2C-510 > Project: Axis2-C > Issue Type: New Feature > Components: rampart >Affects Versions: 1.0.0 > Environment: Any >Reporter: Malinda Kaushalye Kapuruge > Assigned To: Malinda Kaushalye Kapuruge > Fix For: 1.0.0 > > > Rampart should support security policy. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2C-510) Integrate security policy with rampart
[ https://issues.apache.org/jira/browse/AXIS2C-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Malinda Kaushalye Kapuruge reassigned AXIS2C-510: - Assignee: Malinda Kaushalye Kapuruge > Integrate security policy with rampart > -- > > Key: AXIS2C-510 > URL: https://issues.apache.org/jira/browse/AXIS2C-510 > Project: Axis2-C > Issue Type: New Feature > Components: rampart >Affects Versions: 1.0.0 > Environment: Any >Reporter: Malinda Kaushalye Kapuruge > Assigned To: Malinda Kaushalye Kapuruge > Fix For: 1.0.0 > > > Rampart should support security policy. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote 2] [Axis2] Vote for Apache Axis2/C 1.0.0 Release
tested and reviewed on windows. Works fine. Here's my +1 regards, Dushshantha On 5/3/07, Dinesh Premalal <[EMAIL PROTECTED]> wrote: +1 thanks, Dinesh -- Dinesh Premalal [EMAIL PROTECTED] WSO2, Inc.; http://www.wso2.com/ GPG Key ID : A255955C GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2C-599) compile errors
[ https://issues.apache.org/jira/browse/AXIS2C-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-599. -- Resolution: Fixed Assignee: Samisa Abeysinghe Removed duplication > compile errors > -- > > Key: AXIS2C-599 > URL: https://issues.apache.org/jira/browse/AXIS2C-599 > Project: Axis2-C > Issue Type: Bug > Environment: Microsoft Visual Studio 7.1 on Windows XP >Reporter: Jim S > Assigned To: Samisa Abeysinghe > > I am getting compile errors attempting to compile the source code from Final > version 1.0.0 > If I comment out the second occurrence of this variable the source > compilation works properly > This is because the same variable is being defined more than once.in > axutil_error.h > Line 561: > const axis2_char_t* axutil_error_messages[AXIS2_ERROR_LAST + 1]; > Line 579 >const axis2_char_t* axutil_error_messages[AXIS2_ERROR_LAST + 1]; > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote 2] [Axis2] Vote for Apache Axis2/C 1.0.0 Release
+1 thanks, Dinesh -- Dinesh Premalal [EMAIL PROTECTED] WSO2, Inc.; http://www.wso2.com/ GPG Key ID : A255955C GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2C-515) the sample dynamic_client segfault on Linux: double free or corruption
[ https://issues.apache.org/jira/browse/AXIS2C-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-515. -- Resolution: Won't Fix Dynamic client has been removed form 1.0.0 > the sample dynamic_client segfault on Linux: double free or corruption > -- > > Key: AXIS2C-515 > URL: https://issues.apache.org/jira/browse/AXIS2C-515 > Project: Axis2-C > Issue Type: Bug > Components: xml/om > Environment: Linux >Reporter: Dushshantha Chandradasa > > The sample dynamic_client segfaults with the message: > *** glibc detected *** ./dynamic_client: double free or corruption (!prev): > 0x0065ed50 *** > === Backtrace: = > /lib64/libc.so.6[0x2b7c278a837e] > /lib64/libc.so.6(__libc_free+0x6c)[0x2b7c278a999c] > /usr/lib64/libxml2.so.2(xmlBufferFree+0x2e)[0x2b7c272dcfae] > /root/axis2Test/c/deploy/lib/libaxis2_parser.so.0(axis2_libxml2_writer_wrapper_free+0x30)[0x2b7c26d339d0] > /root/axis2Test/c/deploy/lib/libaxis2_axiom.so.0(axiom_output_free+0x88)[0x2b7c26c185d8] > ./dynamic_client[0x401293] > /lib64/libc.so.6(__libc_start_main+0xf4)[0x2b7c2785a154] > ... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2C-224) Calculator server sample need to be changed
[ https://issues.apache.org/jira/browse/AXIS2C-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-224. -- Resolution: Won't Fix Dynamic client has been dropped form 1.0.0 > Calculator server sample need to be changed > --- > > Key: AXIS2C-224 > URL: https://issues.apache.org/jira/browse/AXIS2C-224 > Project: Axis2-C > Issue Type: Improvement > Components: samples >Affects Versions: Current (Nightly) >Reporter: Damitha Kumarage > > Calculator server sample need to be changed so that it serves both wsdl1 and > wsdl2 > dynamic client requests done by dynamic client sample -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2C-581) Issues in the "Apache Axis2/C User's Guide - Writing Web Services Skeleton Using Code Generator and Writing Web Service Clients Using Axis2's Primary APIs"
[
https://issues.apache.org/jira/browse/AXIS2C-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-581.
--
Resolution: Fixed
User guide has been dropped and content moved to Axis2/C manual. These issues
has been fixed in the manual
> Issues in the "Apache Axis2/C User's Guide - Writing Web Services Skeleton
> Using Code Generator and Writing Web Service Clients Using Axis2's Primary
> APIs"
> ---
>
> Key: AXIS2C-581
> URL: https://issues.apache.org/jira/browse/AXIS2C-581
> Project: Axis2-C
> Issue Type: Bug
> Components: documentation
> Environment: Windows XP
>Reporter: Evanthika Amarasiri
>Priority: Minor
>
> 1. In "The WSDL interoptestdoclitparameters.wsdl can be found in
> /test/resources directory." shouldn't be
> ?
> All the instances which says should be replaced by
>
> 2. There are some variables in the User guide given in capitals but in the
> samples they are given in simples. These needs to be changed.
> Under the heading "echo_blocking Client"
> a) AXIS2_OPTIONS_SET_TO
> b) AXIS2_SVC_CLIENT_SET_OPTIONS
> c) AXIS2_SVC_CLIENT_SEND_RECEIVE
> Under the heading "echo_non_blocking Client"
> a) AXIS2_SVC_CLIENT_SEND_RECEIVE_NON_BLOCKING
> b) AXIS2_CALLBACK_SET_ON_COMPLETE
> Under the heading "echo_non_blocking_dual Client"
> a) AXIS2_SVC_CLIENT_ENGAGE_MODULE
> b) AXIS2_MODULE_ADDRESSING - Not used anywhere in the code
> c) AXIS2_OPTIONS_SET_USE_SEPERATE_LISTENER
> 3. The following code segments are different to what is given in the samples.
> Generally all the code segments given in the user guide should be replaced
> with the latest code
> **
> Sample
> ==
> if (!client_home || !strcmp (client_home, ""))
> client_home = "../..";
> Guide
>
> if (!client_home)
>client_home = "../../deploy";
> ***
> Sample
> =
> AXIS2_LOG_ERROR(env->log, AXIS2_LOG_SI, "Stub invoke FAILED: Error
> code:"
> " %d :: %s", env->error->error_number,
> AXIS2_ERROR_GET_MESSAGE(env->error));
> return -1;
> }
> Guide
>
>AXIS2_LOG_ERROR(env->log, AXIS2_LOG_SI, "Stub invoke FAILED:Error
> code:
> % d :: %s", env->error->error_number,
> AXIS2_ERROR_GET_MESSAGE(env->error));
> ***
> Sample
> =
> if(ret_node)
> {
>axis2_char_t *om_str = NULL;
>om_str = AXIOM_NODE_TO_STRING(ret_node, env);
>if (om_str)
> {
>printf("\nReceived OM : %s\n", om_str);
> AXIS2_FREE(env->allocator, om_str);
> }
> printf("\necho client invoke SUCCESSFUL!\n");
> }
> Guide
>
> if(ret_node)
> {
>axis2_char_t *om_str = NULL;
>om_str = AXIOM_NODE_TO_STRING(ret_node, env);
>if (om_str)
>printf("\nReceived OM : %s\n", om_str);
>
>
> printf("\necho client invoke SUCCESSFUL!\n");
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (AXIS2C-535) Axis2/C adds rampart handlers when they are not engaged.
[ https://issues.apache.org/jira/browse/AXIS2C-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Malinda Kaushalye Kapuruge closed AXIS2C-535. - > Axis2/C adds rampart handlers when they are not engaged. > > > Key: AXIS2C-535 > URL: https://issues.apache.org/jira/browse/AXIS2C-535 > Project: Axis2-C > Issue Type: Bug >Affects Versions: Current (Nightly) >Reporter: Manjula Peiris > Assigned To: Malinda Kaushalye Kapuruge >Priority: Critical > Attachments: patch.txt > > > If we run normal Axis2/C samples after building rampart they fail. This is > because Axis2/C engine adds rampart handlers to its phases even the module > is not engaged in the axis2.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2C-535) Axis2/C adds rampart handlers when they are not engaged.
[ https://issues.apache.org/jira/browse/AXIS2C-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Malinda Kaushalye Kapuruge reassigned AXIS2C-535: - Assignee: Malinda Kaushalye Kapuruge > Axis2/C adds rampart handlers when they are not engaged. > > > Key: AXIS2C-535 > URL: https://issues.apache.org/jira/browse/AXIS2C-535 > Project: Axis2-C > Issue Type: Bug >Affects Versions: Current (Nightly) >Reporter: Manjula Peiris > Assigned To: Malinda Kaushalye Kapuruge >Priority: Critical > Attachments: patch.txt > > > If we run normal Axis2/C samples after building rampart they fail. This is > because Axis2/C engine adds rampart handlers to its phases even the module > is not engaged in the axis2.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2C-582) Building axis2c fails when OpenSSL is installed into a directory with spaces (on Windows)
[ https://issues.apache.org/jira/browse/AXIS2C-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-582. -- Resolution: Fixed use double quotes in the given install path - that fixes the problem > Building axis2c fails when OpenSSL is installed into a directory with spaces > (on Windows) > - > > Key: AXIS2C-582 > URL: https://issues.apache.org/jira/browse/AXIS2C-582 > Project: Axis2-C > Issue Type: Bug > Components: build system (Windows) > Environment: Windows XP >Reporter: Evanthika Amarasiri > > Below are the steps to reproduce the issue > 1. Installed OpenSSL in to the directory "C:\Program Files\OpenSSL" > 2. Enabled SSL in the "configure.in" file > 3. Executed the command "nmake all" > 4. Got the following issue while building > > Generating Code... > LINK : fatal error LNK1181: cannot open input file 'Files\OpenSSL\lib\VC.obj' > NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio > 8\VC\BIN\link.exe"' : return code '0x49d' > Stop. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2C-562) make of axis2c-src-0.96 fails because of undeclared variable XML_PARSE_RECOVER in libxml2_reader_wrapper.c
[
https://issues.apache.org/jira/browse/AXIS2C-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-562.
--
Resolution: Fixed
XML_PARSE_RECOVER is a constant defined in libxml2. Hence, this issue is
basiclly to do with not using the correct libxml version or not having the
correct paths set for libxml2. This is not a problem in Axis2/C source
> make of axis2c-src-0.96 fails because of undeclared variable
> XML_PARSE_RECOVER in libxml2_reader_wrapper.c
> --
>
> Key: AXIS2C-562
> URL: https://issues.apache.org/jira/browse/AXIS2C-562
> Project: Axis2-C
> Issue Type: Bug
> Components: build system (Unix/Linux)
>Affects Versions: 0.96
> Environment: Operating system: GNU/Linux, Hardware-platform: i386,
> libxml2 version 2.5.10-7, libxml2-devel version 2.5.10-7, gcc version 2.96
>Reporter: gayatri subramanian
>
> I followed the instructions for installing Axis2/C on Linux using the source
> release.
> 1) axis2c-src-0.96.tar.gz is unzipped to /home/gaysubra/axis-c/axis2c
> 2) setenv AXIS2C_HOME /home/gaysubra/axis-c/axis2c
> 3) cd /home/gaysubra/axis-c/axis2c
> 4) ./configure --prefix=${AXIS2C_HOME}
> 5) make
> And make gives an error because of undeclared variable XML_PARSE_RECOVER in
> libxml2_reader_wrapper.c; the configure script ran without giving any error.
> Here is the output from make:
> (gaysubra) axis2c- make
> make all-recursive
> make[1]: Entering directory `/home/gaysubra/axis-c/axis2c'
> Making all in util
> make[2]: Entering directory `/home/gaysubra/axis-c/axis2c/util'
> make all-recursive
> make[3]: Entering directory `/home/gaysubra/axis-c/axis2c/util'
> Making all in src
> make[4]: Entering directory `/home/gaysubra/axis-c/axis2c/util/src'
> Making all in platforms/unix
> make[5]: Entering directory
> `/home/gaysubra/axis-c/axis2c/util/src/platforms/unix'
> make[5]: Nothing to be done for `all'.
> make[5]: Leaving directory
> `/home/gaysubra/axis-c/axis2c/util/src/platforms/unix'
> Making all in minizip
> make[5]: Entering directory `/home/gaysubra/axis-c/axis2c/util/src/minizip'
> make[5]: Nothing to be done for `all'.
> make[5]: Leaving directory `/home/gaysubra/axis-c/axis2c/util/src/minizip'
> make[5]: Entering directory `/home/gaysubra/axis-c/axis2c/util/src'
> make[5]: Nothing to be done for `all-am'.
> make[5]: Leaving directory `/home/gaysubra/axis-c/axis2c/util/src'
> make[4]: Leaving directory `/home/gaysubra/axis-c/axis2c/util/src'
> Making all in include
> make[4]: Entering directory `/home/gaysubra/axis-c/axis2c/util/include'
> make[4]: Nothing to be done for `all'.
> make[4]: Leaving directory `/home/gaysubra/axis-c/axis2c/util/include'
> make[4]: Entering directory `/home/gaysubra/axis-c/axis2c/util'
> make[4]: Leaving directory `/home/gaysubra/axis-c/axis2c/util'
> make[3]: Leaving directory `/home/gaysubra/axis-c/axis2c/util'
> make[2]: Leaving directory `/home/gaysubra/axis-c/axis2c/util'
> Making all in axiom
> make[2]: Entering directory `/home/gaysubra/axis-c/axis2c/axiom'
> make all-recursive
> make[3]: Entering directory `/home/gaysubra/axis-c/axis2c/axiom'
> Making all in src
> make[4]: Entering directory `/home/gaysubra/axis-c/axis2c/axiom/src'
> Making all in parser
> make[5]: Entering directory `/home/gaysubra/axis-c/axis2c/axiom/src/parser'
> Making all in libxml2
> make[6]: Entering directory
> `/home/gaysubra/axis-c/axis2c/axiom/src/parser/libxm
> l2'
> if /bin/sh ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I. -I../../.. -I../../../include -I../../../src/parser -I
> ../../../../util/include -g -O2 -D_LARGEFILE64_SOURCE -ansi -Wall
> -Wno-implicit-function-declaration -I/usr/include/libxml2-MT
> libxml2_reader_wrapper.lo -MD -MP -MF ".deps/libxml2_reader_wrapper.Tpo" -c
> -o libxml2_reader_wrapper.lo libxml2_reader_wrapper.c; \
> then mv -f ".deps/libxml2_reader_wrapper.Tpo"
> ".deps/libxml2_reader_wrapper.Plo"; else rm -f
> ".deps/libxml2_reader_wrapper.Tpo"; exit 1; fi
> gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../include
> -I../../../src/parser -I ../../../../util/include -g -O2
> -D_LARGEFILE64_SOURCE -ansi -Wall -Wno-implicit-function-declaration
> -I/usr/include/libxml2 -MT libxml2_reader_wrapper.lo -MD -MP -MF
> .deps/libxml2_reader_wrapper.Tpo -c libxml2_reader_wrapper.c -fPIC -DPIC -o
> .libs/libxml2_reader_wrapper.o
> libxml2_reader_wrapper.c: In function `axiom_xml_reader_create_for_file':
> libxml2_reader_wrapper.c:309: `XML_PARSE_RECOVER' undeclared (first use in
> this function)
> libxml2_reader_wrapper.c:309: (Each undeclared identifier is reported only
> once
> libxml2_reader_wrapper.c:309: for each function it appears in.)
> libxml2_reader_wrapper.c:309: warning: assignment makes pointer fr
[jira] Assigned: (AXIS2C-534) Rampart client segfaults in the presense of wrong clientrepo path
[ https://issues.apache.org/jira/browse/AXIS2C-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Malinda Kaushalye Kapuruge reassigned AXIS2C-534: - Assignee: Malinda Kaushalye Kapuruge > Rampart client segfaults in the presense of wrong clientrepo path > -- > > Key: AXIS2C-534 > URL: https://issues.apache.org/jira/browse/AXIS2C-534 > Project: Axis2-C > Issue Type: Bug > Components: rampart >Affects Versions: Current (Nightly) > Environment: All >Reporter: Dushshantha Chandradasa > Assigned To: Malinda Kaushalye Kapuruge > > Given a wrong client repo path as an argument, Rampart sample client sec_echo > segfaults. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDL2C
Hi Jim, Please try this nightly build http://people.apache.org/dist/axis2/nightly/axis2-SNAPSHOT.zip. Thanks Milinda On 5/3/07, Milinda Pathirage <[EMAIL PROTECTED]> wrote: Hi Jim, Can you please tell me which version of Axis2/Java is used for code generation. It is better if you can get a checkout from Axis2/Java svn trunk and build. I updated all the changes in current trunk of Axis2/Java before the Axis2/c 1.0.0 release. Thanks Milinda On 5/2/07, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote: > > Jim Seipp wrote: > > >Hi Samisa, > > > >I am using "Apache Axis2 1.2-SNAPSHOT build (May 1 2007)" > > > >It appears that it is compiling WSDL2C.java to use the header file > >'axis2_log_default.h" > > > >In the Axis2C release folder util/include I see the file > >"axutil_log_default.h" > > > >It appears that the WSDL2C.java program is compiling to use an obsolete > >header name? > > > > > Opps, that is a bug :( > > Is it possible for you to create a Jira issue and attach the WSDL file > tat you are using to that Jira? > > Samisa... > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- [EMAIL PROTECTED] WSO2, Inc: http://www.wso2.com "Oxygenating the Web Service Platform" http://www.milindalakmal.wordpress.com -- [EMAIL PROTECTED] WSO2, Inc: http://www.wso2.com "Oxygenating the Web Service Platform" http://www.milindalakmal.wordpress.com
Re: [VOTE]Rampart/C 0.90 release
Thanks... My mistake :) There are few other issues too. I will call a new vote for Rampart/C. -Kaushalye Samisa Abeysinghe wrote: Source has been posted only in tar format. For the benefit of Windows users, we should also post source in zip format as well. Samisa... Kaushalye Kapuruge wrote: Hi List, It's time to release Apache Rampart/C 0.90. This will be released in parallel to the release of Apache Axis2/C 1.0. I've packed and uploaded the bin and src distributions here[1]. The key used to sign can be found here[2]. Apache Rampart/C 0.90 feature list includes... 1. Ability to send Username Tokens with plain text passwords or password digests. 2. Timestamp token support 3. SOAP message encryption 4. SOAP message signature 5. WS-Security Policy based configurations. Please test, review and vote. Here is my +1. Cheers, Kaushalye [1] http://people.apache.org/~kaushalye/release/rampart-c/0.90/ [2] http://people.apache.org/~kaushalye/release/KEYS - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Vote 2] [Axis2] Vote for Apache Axis2/C 1.0.0 Release
Hi Devs, After fixing the issues found with the initial release artifacts, I have re-packaged and uploaded the Apache Axis2/C 1.0.0 release artifacts at http://people.apache.org/~samisa/release/1.0.0/final/ The key used to sign the release artifacts can be found at http://www.apache.org/dist/ws/axis2/c/KEYS Please test, review and vote on these latest release artifacts for Apache Axis2/C 1.0.0 release. I have tested and reviewed them and here is my vote: +1 Thanks, Samisa... -- Samisa Abeysinghe : http://www.bloglines.com/blog/samisa - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote] [Axis2] Vote for Apache Axis2/C 1.0.0 Release
Given that we fixed several issues and re-packaged the artifacts several time, we should call the fresh vote on the release artifacts. So I would start a new vote as soon as the new artifacts are ready. Thanks, Samisa... Samisa Abeysinghe wrote: Fixed both the issues. Thanks, Samisa... Chris Darroch wrote: Samisa: The latest, and final, artifacts are uploaded here: http://people.apache.org/~samisa/release/1.0.0/final/ Please test. I plan to send the release note in about 12 hours form now. I have tested all the sources and binaries successfully. Thanks for all the quick fixes! The configure --help notes and the INSTALL files are much clearer. I successfully built and installed and tested with --enable-tests, and with the samples directory. Two things, one small, one maybe not: The small thing is that is seems like the test/core/clientapi/test_clientapi program fails (with a message now, thank you!) unless AXIS2C_HOME points to the installed location. (I'm guessing it's looking for axis2.xml.) This means you really should run "make && make install", then set AXIS2C_HOME=/path/to/install, and then "make check". That's a little different than the usual "make && make check && make install" process. We should perhaps make that clean in the main INSTALL file, or else alter test_clientapi.c somehow so that it will work if you set AXIS2C_HOME=/path/to/source or something. Then the more typical "check then install" process would function, so long as you had AXIS2C_HOME set to the location of the Axis2/C sources. The maybe not-so-small thing is that for me, at least, on an older RedHat Linux box, util/test/util/test_thread fails sometimes and not other times. That feels like a race condition problem to me. (This is regardless of what AXIS2C_HOME is set to, or even if it's unset; that was a red herring in my previous email.) Here's the output from an unsuccessful run: success - thread_init - axutil_thread_once_init success - thread_init - axutil_thread_mutex_create success - test_axutil_thread_create - axutil_thread_create success - test_axutil_thread_create - axutil_thread_create thread data = 5 x = 1 thread data = 25 x = 2 success - test_axutil_thread_create - axutil_thread_join Segmentation fault Here's another, different one: success - thread_init - axutil_thread_once_init success - thread_init - axutil_thread_mutex_create thread data = 5 x = 1 success - test_axutil_thread_create - axutil_thread_create success - test_axutil_thread_create - axutil_thread_create Segmentation fault Here's a backtrace from a failure like the first one above: (gdb) bt #0 0x003854bd in axutil_thread_join (thd=0x80552b0) at thread_unix.c:158 #1 0x08048d27 in test_axutil_thread_detach (env=0x80551e0) at test_thread.c:132 #2 0x08048fdb in create_env_with_error_log () at test_thread.c:260 #3 0x0804915d in __libc_csu_fini () from /tmp/chrisd_build/axis2c-src-1.0.0/util/test/util/.libs/test_thread #4 0x00125e23 in __libc_start_main () from /lib/tls/libc.so.6 #5 0x080489e1 in __do_global_dtors_aux () from /tmp/chrisd_build/axis2c-src-1.0.0/util/test/util/.libs/test_thread (gdb) frame #0 0x003854bd in axutil_thread_join (thd=0x80552b0) at thread_unix.c:158 158 if (0 == pthread_join(*(thd->td), (void *)(&thread_stat))) (gdb) print *(thd->td) Cannot access memory at address 0x62696c2f I'm not sure if that helps, but it looks to me like something must be getting deallocated at the wrong time here. Chris. -- Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web Services Developers' Portal) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
