[jira] Commented: (AXIS2C-528) problem with the build on AIX
[ https://issues.apache.org/jira/browse/AXIS2C-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643634#action_12643634 ] Dinesh Premalal commented on AXIS2C-528: suggested fix http://mail-archives.apache.org/mod_mbox/ws-axis-c-dev/200810.mbox/[EMAIL PROTECTED] > problem with the build on AIX > - > > Key: AXIS2C-528 > URL: https://issues.apache.org/jira/browse/AXIS2C-528 > Project: Axis2-C > Issue Type: Bug > Components: build system (Unix/Linux) > Environment: AIX 5.3 > gcc -v > Using built-in specs. > Target: powerpc-ibm-aix5.3.0.0 > Configured with: ../gcc-4.1.1/configure --prefix=/usr/local/4.1.1 > --enable-languages=c,c++,objc > Thread model: aix > gcc version 4.1.1 >Reporter: Vladimir Penev >Assignee: Sanjaya Ratnaweera > > I have tried to build version 0.96 of AXIS2C on our development mashine: > AIX 5.3 > gcc -v > Using built-in specs. > Target: powerpc-ibm-aix5.3.0.0 > Configured with: ../gcc-4.1.1/configure --prefix=/usr/local/4.1.1 > --enable-languages=c,c++,objc > Thread model: aix > gcc version 4.1.1 > The configure has ok, but after make command I received: > gmake all-recursive > gmake[1]: Entering directory `/axis2c-src-0.96' > Making all in util > gmake[2]: Entering directory `/axis2c-src-0.96/util' > gmake all-recursive > gmake[3]: Entering directory `/axis2c-src-0.96/util' > Making all in src > gmake[4]: Entering directory `/axis2c-src-0.96/util/src' > Making all in platforms/unix > gmake[5]: Entering directory `/axis2c-src-0.96/util/src/platforms/unix' > if /bin/sh ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I. -I../../.. -I../../../include -I../../../include/platforms > -I../../../include/platforms/unix-g -O2 -D_LARGEFILE64_SOURCE -ansi -Wall > -Wno-implicit-function-declaration -MT uuid_gen_unix.lo -MD -MP -MF > ".deps/uuid_gen_unix.Tpo" -c -o uuid_gen_unix.lo uuid_gen_unix.c; \ > then mv -f ".deps/uuid_gen_unix.Tpo" ".deps/uuid_gen_unix.Plo"; else > rm -f ".deps/uuid_gen_unix.Tpo"; exit 1; fi > mkdir .libs > gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../include > -I../../../include/platforms -I../../../include/platforms/unix -g -O2 > -D_LARGEFILE64_SOURCE -ansi -Wall -Wno-implicit-function-declaration -MT > uuid_gen_unix.lo -MD -MP -MF .deps/uuid_gen_unix.Tpo -c uuid_gen_unix.c > -DPIC -o .libs/uuid_gen_unix.o > uuid_gen_unix.c:24:26: error: sys/sockio.h: No such file or directory > In file included from uuid_gen_unix.c:26: > /usr/include/net/if_arp.h:68: error: expected specifier-qualifier-list before > 'u_short' > /usr/include/net/if_arp.h:99: error: expected specifier-qualifier-list before > 'u_short' > /usr/include/net/if_arp.h:103: error: expected specifier-qualifier-list > before 'u_short' > /usr/include/net/if_arp.h:107: error: expected specifier-qualifier-list > before 'u_short' > /usr/include/net/if_arp.h:153: error: expected specifier-qualifier-list > before 'u_char' > /usr/include/net/if_arp.h:170: error: field 'at_iaddr' has incomplete type > /usr/include/net/if_arp.h:171: error: expected specifier-qualifier-list > before 'u_char' > /usr/include/net/if_arp.h:204: error: field 'arp_pa' has incomplete type > /usr/include/net/if_arp.h:205: error: field 'arp_ha' has incomplete type > /usr/include/net/if_arp.h:207: error: expected specifier-qualifier-list > before 'u_short' > /usr/include/net/if_arp.h:227: error: field 'ac_if' has incomplete type > /usr/include/net/if_arp.h:228: error: expected specifier-qualifier-list > before 'u_char' > /usr/include/net/if_arp.h:324: error: expected specifier-qualifier-list > before 'u_char' > In file included from uuid_gen_unix.c:32: > /usr/include/net/if_dl.h:87: error: expected specifier-qualifier-list before > 'u_char' > In file included from uuid_gen_unix.c:47: > ../../../include/platforms/unix/axis2_uuid_gen_unix.h:56: error: field > 'time_last' has incomplete type > In file included from > ../../../include/platforms/axis2_platform_auto_sense.h:50, > from uuid_gen_unix.c:48: > ../../../include/platforms/unix/axis2_unix.h:117:20: error: getopt.h: No such > file or directory > In file included from ../../../include/platforms/unix/axis2_unix.h:131, > from > ../../../include/platforms/axis2_platform_auto_sense.h:50, > from uuid_gen_unix.c:48: > /usr/local/include/zlib.h:1183: error: expected '=', ',', ';', 'asm' or > '__attribute__' before 'gzseek' > /usr/local/include/zlib.h:1208: error: expected '=', ',', ';', 'asm' or > '__attribute__' before 'gztell' > /usr/local/include/zlib.h:1276: error: expected declaration specifiers or > '...' before 'off_t' > /usr/local/include/zlib.h:1301: error: expected declaration specifiers or > '...' before 'off_t' > In file included from /usr/include/sched.h:51, >
[jira] Commented: (AXIS2C-528) problem with the build on AIX
[ https://issues.apache.org/jira/browse/AXIS2C-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643629#action_12643629 ] Dinesh Premalal commented on AXIS2C-528: An user has suggest a fix for this http://mail-archives.apache.org/mod_mbox/ws-axis-c-dev/200810.mbox/browser > problem with the build on AIX > - > > Key: AXIS2C-528 > URL: https://issues.apache.org/jira/browse/AXIS2C-528 > Project: Axis2-C > Issue Type: Bug > Components: build system (Unix/Linux) > Environment: AIX 5.3 > gcc -v > Using built-in specs. > Target: powerpc-ibm-aix5.3.0.0 > Configured with: ../gcc-4.1.1/configure --prefix=/usr/local/4.1.1 > --enable-languages=c,c++,objc > Thread model: aix > gcc version 4.1.1 >Reporter: Vladimir Penev >Assignee: Sanjaya Ratnaweera > > I have tried to build version 0.96 of AXIS2C on our development mashine: > AIX 5.3 > gcc -v > Using built-in specs. > Target: powerpc-ibm-aix5.3.0.0 > Configured with: ../gcc-4.1.1/configure --prefix=/usr/local/4.1.1 > --enable-languages=c,c++,objc > Thread model: aix > gcc version 4.1.1 > The configure has ok, but after make command I received: > gmake all-recursive > gmake[1]: Entering directory `/axis2c-src-0.96' > Making all in util > gmake[2]: Entering directory `/axis2c-src-0.96/util' > gmake all-recursive > gmake[3]: Entering directory `/axis2c-src-0.96/util' > Making all in src > gmake[4]: Entering directory `/axis2c-src-0.96/util/src' > Making all in platforms/unix > gmake[5]: Entering directory `/axis2c-src-0.96/util/src/platforms/unix' > if /bin/sh ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I. -I../../.. -I../../../include -I../../../include/platforms > -I../../../include/platforms/unix-g -O2 -D_LARGEFILE64_SOURCE -ansi -Wall > -Wno-implicit-function-declaration -MT uuid_gen_unix.lo -MD -MP -MF > ".deps/uuid_gen_unix.Tpo" -c -o uuid_gen_unix.lo uuid_gen_unix.c; \ > then mv -f ".deps/uuid_gen_unix.Tpo" ".deps/uuid_gen_unix.Plo"; else > rm -f ".deps/uuid_gen_unix.Tpo"; exit 1; fi > mkdir .libs > gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../include > -I../../../include/platforms -I../../../include/platforms/unix -g -O2 > -D_LARGEFILE64_SOURCE -ansi -Wall -Wno-implicit-function-declaration -MT > uuid_gen_unix.lo -MD -MP -MF .deps/uuid_gen_unix.Tpo -c uuid_gen_unix.c > -DPIC -o .libs/uuid_gen_unix.o > uuid_gen_unix.c:24:26: error: sys/sockio.h: No such file or directory > In file included from uuid_gen_unix.c:26: > /usr/include/net/if_arp.h:68: error: expected specifier-qualifier-list before > 'u_short' > /usr/include/net/if_arp.h:99: error: expected specifier-qualifier-list before > 'u_short' > /usr/include/net/if_arp.h:103: error: expected specifier-qualifier-list > before 'u_short' > /usr/include/net/if_arp.h:107: error: expected specifier-qualifier-list > before 'u_short' > /usr/include/net/if_arp.h:153: error: expected specifier-qualifier-list > before 'u_char' > /usr/include/net/if_arp.h:170: error: field 'at_iaddr' has incomplete type > /usr/include/net/if_arp.h:171: error: expected specifier-qualifier-list > before 'u_char' > /usr/include/net/if_arp.h:204: error: field 'arp_pa' has incomplete type > /usr/include/net/if_arp.h:205: error: field 'arp_ha' has incomplete type > /usr/include/net/if_arp.h:207: error: expected specifier-qualifier-list > before 'u_short' > /usr/include/net/if_arp.h:227: error: field 'ac_if' has incomplete type > /usr/include/net/if_arp.h:228: error: expected specifier-qualifier-list > before 'u_char' > /usr/include/net/if_arp.h:324: error: expected specifier-qualifier-list > before 'u_char' > In file included from uuid_gen_unix.c:32: > /usr/include/net/if_dl.h:87: error: expected specifier-qualifier-list before > 'u_char' > In file included from uuid_gen_unix.c:47: > ../../../include/platforms/unix/axis2_uuid_gen_unix.h:56: error: field > 'time_last' has incomplete type > In file included from > ../../../include/platforms/axis2_platform_auto_sense.h:50, > from uuid_gen_unix.c:48: > ../../../include/platforms/unix/axis2_unix.h:117:20: error: getopt.h: No such > file or directory > In file included from ../../../include/platforms/unix/axis2_unix.h:131, > from > ../../../include/platforms/axis2_platform_auto_sense.h:50, > from uuid_gen_unix.c:48: > /usr/local/include/zlib.h:1183: error: expected '=', ',', ';', 'asm' or > '__attribute__' before 'gzseek' > /usr/local/include/zlib.h:1208: error: expected '=', ',', ';', 'asm' or > '__attribute__' before 'gztell' > /usr/local/include/zlib.h:1276: error: expected declaration specifiers or > '...' before 'off_t' > /usr/local/include/zlib.h:1301: error: expected declaration specifiers or > '...' before 'off_t' > In file included from /usr/include/sched.
[jira] Commented: (AXIS2C-1143) Implement CGI deployment support for Axis2/C
[ https://issues.apache.org/jira/browse/AXIS2C-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602291#action_12602291 ] Dinesh Premalal commented on AXIS2C-1143: - What is going on regarding this project ? Could we see any progress reports etc ? > Implement CGI deployment support for Axis2/C > -- > > Key: AXIS2C-1143 > URL: https://issues.apache.org/jira/browse/AXIS2C-1143 > Project: Axis2-C > Issue Type: New Feature > Environment: Linux\Windows >Reporter: Nandika Jayawardana > > This would require implementing an executable that will enable deploying > Axis2/C on Web Servers that Support CGI. -- 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] Commented: (AXIS2C-1179) Axis2-C Unicode Support
[ https://issues.apache.org/jira/browse/AXIS2C-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602288#action_12602288 ] Dinesh Premalal commented on AXIS2C-1179: - Mail archives 1.http://marc.info/?l=axis-c-dev&w=2&r=1&s=axis2%2Fc+unicode&q=b 2.http://marc.info/?l=axis-c-user&w=2&r=1&s=axis2%2Fc+unicode&q=b > Axis2-C Unicode Support > --- > > Key: AXIS2C-1179 > URL: https://issues.apache.org/jira/browse/AXIS2C-1179 > Project: Axis2-C > Issue Type: Bug > Components: platforms >Affects Versions: 1.2.0 > Environment: Windows XP SP2 >Reporter: Dayakar Reddy >Priority: Critical > Fix For: 1.2.0 > > Original Estimate: 168h > Remaining Estimate: 168h > > Hi, > I would like know, whether Axis2\C 1.2.0 supports UNICODE ? > I am using Axis2\C for just accessing the Web Services from the server. i.e I > am creating Axis2\C client. > If there is no UNICODE support, then is there any way to make unicode > complant Axis2\C client ? > Thanks. > Dayakar -- 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] Commented: (AXIS2C-1179) Axis2-C Unicode Support
[ https://issues.apache.org/jira/browse/AXIS2C-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602287#action_12602287 ] Dinesh Premalal commented on AXIS2C-1179: - AFAIK, there is no UNICODE support Axis2/C. Please read the mail archives for more details. > Axis2-C Unicode Support > --- > > Key: AXIS2C-1179 > URL: https://issues.apache.org/jira/browse/AXIS2C-1179 > Project: Axis2-C > Issue Type: Bug > Components: platforms >Affects Versions: 1.2.0 > Environment: Windows XP SP2 >Reporter: Dayakar Reddy >Priority: Critical > Fix For: 1.2.0 > > Original Estimate: 168h > Remaining Estimate: 168h > > Hi, > I would like know, whether Axis2\C 1.2.0 supports UNICODE ? > I am using Axis2\C for just accessing the Web Services from the server. i.e I > am creating Axis2\C client. > If there is no UNICODE support, then is there any way to make unicode > complant Axis2\C client ? > Thanks. > Dayakar -- 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] Updated: (AXIS2C-1166) axis2_http_server remote crash
[ https://issues.apache.org/jira/browse/AXIS2C-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal updated AXIS2C-1166: Priority: Major (was: Blocker) > axis2_http_server remote crash > --- > > Key: AXIS2C-1166 > URL: https://issues.apache.org/jira/browse/AXIS2C-1166 > Project: Axis2-C > Issue Type: Bug > Components: transport/http >Affects Versions: 1.4.0 > Environment: linux fc6 >Reporter: Frederic Heem > Attachments: echoString.txt > > > Please run netcat as follows: > nc 127.0.0.1 9090 < echoString.txt > This leads to a segmentation fault: > ==17690== Thread 3: > ==17690== Invalid read of size 4 > ==17690==at 0x400F14A: axis2_http_header_create_by_str (http_header.c:64) > ==17690==by 0x4012C2B: axis2_simple_http_svr_conn_read_request > (simple_http_svr_conn.c:264) > ==17690==by 0x316B496B: ??? > ==17690== Address 0x4371796c is not stack'd, malloc'd or (recently) free'd > ==17690== > ==17690== Process terminating with default action of signal 11 (SIGSEGV) > ==17690== Access not within mapped region at address 0x4371796C > ==17690==at 0x400F14A: axis2_http_header_create_by_str (http_header.c:64) > ==17690==by 0x4012C2B: axis2_simple_http_svr_conn_read_request > (simple_http_svr_conn.c:264) > ==17690==by 0x316B496B: ??? > ==17690== > ==17690== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 65 from 1) > ==17690== malloc/free: in use at exit: 470,266 bytes in 10,435 blocks. > ==17690== malloc/free: 17,660 allocs, 7,225 frees, 1,202,705 bytes allocated. > ==17690== For counts of detected errors, rerun with: -v > ==17690== searching for pointers to 10,435 not-freed blocks. > ==17690== checked 21,606,456 bytes. > ==17690== > ==17690== LEAK SUMMARY: > ==17690==definitely lost: 1,222 bytes in 45 blocks. > ==17690== possibly lost: 272 bytes in 2 blocks. > ==17690==still reachable: 468,772 bytes in 10,388 blocks. > ==17690== suppressed: 0 bytes in 0 blocks. > ==17690== Rerun with --leak-check=full to see details of leaked memory. > Killed -- 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] Updated: (AXIS2C-1135) MacOS version doesn't compile. Patch provided
[
https://issues.apache.org/jira/browse/AXIS2C-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Premalal updated AXIS2C-1135:
Priority: Major (was: Blocker)
> MacOS version doesn't compile. Patch provided
> -
>
> Key: AXIS2C-1135
> URL: https://issues.apache.org/jira/browse/AXIS2C-1135
> Project: Axis2-C
> Issue Type: Bug
> Components: build system (Unix/Linux)
>Affects Versions: 1.4.0
> Environment: MacOS 10.5.2
>Reporter: Mikolaj Kaluszynski
>Assignee: Sanjaya Ratnaweera
>
> Complie error:
> dir_handler.c: In function
> 'axutil_dir_handler_list_services_or_modules_in_dir':
> dir_handler.c:72: warning: passing argument 3 of 'scandir' from incompatible
> pointer type
> Patch:
> --- util/src/dir_handler.c.bak2008-05-13 14:57:10.0 +0200
> +++ util/src/dir_handler.c2008-05-13 14:58:42.0 +0200
> @@ -34,14 +34,15 @@
> #ifdef IS_MACOSX
> int dir_select(
> struct dirent *entry);
> +int file_select(
> +struct dirent *entry);
> #else
> int dir_select(
> const struct dirent *entry);
> +int file_select(
> +const struct dirent *entry);
> #endif
>
> -int
> -file_select(
> -const struct dirent *entry);
>
> /**
> * List the dll files in the given service or module folder path
> @@ -320,9 +321,15 @@
> return file_list;
> }
>
> +#ifdef IS_MACOSX
> +int
> +file_select(
> +struct dirent *entry)
> +#else
> int
> file_select(
> const struct dirent *entry)
> +#endif
> {
> /** FIXME:
>* This block of code has been sitting here doing nothing.
--
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] Updated: (AXIS2C-1171) axis2_http_server remote crash, invalid read in axutil_stream_peek_socket
[ https://issues.apache.org/jira/browse/AXIS2C-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal updated AXIS2C-1171: Priority: Major (was: Blocker) > axis2_http_server remote crash, invalid read in axutil_stream_peek_socket > - > > Key: AXIS2C-1171 > URL: https://issues.apache.org/jira/browse/AXIS2C-1171 > Project: Axis2-C > Issue Type: Bug > Components: transport/http >Affects Versions: 1.4.0 > Environment: linux fc6 >Reporter: Frederic Heem > Attachments: echoStringAxutil_stream_peek_socket.txt > > > The following netcat command makes axis2_http_server crash > nc 127.0.0.1 9090 < echoStringAxutil_stream_peek_socket.txt > Here the valgrind output: > ==32180== Thread 3: > ==32180== Invalid read of size 4 > ==32180==at 0x404CB40: axutil_stream_peek_socket (stream.c:650) > ==32180==by 0x4012A0D: axis2_simple_http_svr_conn_read_request > (simple_http_svr_conn.c:164) > ==32180==by 0x7A5A5336: ??? > ==32180== Address 0x53794645 is not stack'd, malloc'd or (recently) free'd > ==32180== > ==32180== Process terminating with default action of signal 11 (SIGSEGV) > ==32180== Access not within mapped region at address 0x53794645 > ==32180==at 0x404CB40: axutil_stream_peek_socket (stream.c:650) > ==32180==by 0x4012A0D: axis2_simple_http_svr_conn_read_request > (simple_http_svr_conn.c:164) > ==32180==by 0x7A5A5336: ??? > ==32180== > ==32180== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 65 from 1) > ==32180== malloc/free: in use at exit: 467,710 bytes in 10,401 blocks. > ==32180== malloc/free: 17,610 allocs, 7,209 frees, 1,197,675 bytes allocated. > ==32180== For counts of detected errors, rerun with: -v > ==32180== searching for pointers to 10,401 not-freed blocks. > ==32180== checked 21,596,240 bytes. > ==32180== > ==32180== LEAK SUMMARY: > ==32180==definitely lost: 1,222 bytes in 45 blocks. > ==32180== possibly lost: 272 bytes in 2 blocks. > ==32180==still reachable: 466,216 bytes in 10,354 blocks. > ==32180== suppressed: 0 bytes in 0 blocks. > ==32180== Rerun with --leak-check=full to see details of leaked memory. > Killed -- 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] Updated: (AXIS2C-1169) axis2_http_server denial of service
[ https://issues.apache.org/jira/browse/AXIS2C-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal updated AXIS2C-1169: Priority: Major (was: Blocker) This is not a blocker for Axis2/C therefore I'm downgrading priority > axis2_http_server denial of service > --- > > Key: AXIS2C-1169 > URL: https://issues.apache.org/jira/browse/AXIS2C-1169 > Project: Axis2-C > Issue Type: Bug >Affects Versions: 1.4.0 > Environment: linux fc6 >Reporter: Frederic Heem > Attachments: echoString.txt > > > Use the following netcat command to trigger a 100% CPU for axis2_http_server: > nc 127.0.0.1 9090 < echoString.txt -- 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] Commented: (AXIS2C-1169) axis2_http_server denial of service
[ https://issues.apache.org/jira/browse/AXIS2C-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601440#action_12601440 ] Dinesh Premalal commented on AXIS2C-1169: - Frederic, AFAIK axis2_http_server is a server that we (Axis2/C developers) use for testing purposes. That is not intended to use in production environment. I think that is why no body really look into this DOS issue before. I would suggest you to go with mod_axis2 (Apache2) if you are planning to use Axis2/C in a production environment. > axis2_http_server denial of service > --- > > Key: AXIS2C-1169 > URL: https://issues.apache.org/jira/browse/AXIS2C-1169 > Project: Axis2-C > Issue Type: Bug >Affects Versions: 1.4.0 > Environment: linux fc6 >Reporter: Frederic Heem >Priority: Blocker > Attachments: echoString.txt > > > Use the following netcat command to trigger a 100% CPU for axis2_http_server: > nc 127.0.0.1 9090 < echoString.txt -- 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] Updated: (AXIS2C-1125) Getting linking error while creating client for WSDL
[ https://issues.apache.org/jira/browse/AXIS2C-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal updated AXIS2C-1125: Fix Version/s: (was: 1.3.0) 1.4.1 > Getting linking error while creating client for WSDL > > > Key: AXIS2C-1125 > URL: https://issues.apache.org/jira/browse/AXIS2C-1125 > Project: Axis2-C > Issue Type: Bug > Components: build system >Affects Versions: 1.3.0 > Environment: Project: Axis2C(axis2c-bin-1.3.0-win32.zip) > Environment: WinXP, Apache Axis2/C 1.3.0 , Visual studio ( Microsoft > VSExpress2005 edition) >Reporter: samir joshi >Priority: Minor > Fix For: 1.4.1 > > > Hi, > I am getting error while Linking the Client. > Following are the details for the Issue. > I will appretiate if you can help me out on this issue. > Project: Axis2C(axis2c-bin-1.3.0-win32.zip) > Environment: WinXP, Apache Axis2/C 1.3.0 , Visual studio ( Microsoft > VSExpress2005 edition) > Description: > D:\project3.2\axis2c\samples\client\pc\obj>"C:\Program Files\Microsoft Visual > Studio 9.0\VC\bin\link.exe" /LIBPATH:%AXIS2C_HOME%\l > ib axutil.lib axiom.lib axis2_parser.lib axis2_engine.lib > axis2_http_receiver.lib axis2_http_sender.lib mod_axis2_IIS.lib /OUT:D:\ > project3.2\axis2c\samples\client\pc\obj\pc.exe > D:\project3.2\axis2c\samples\client\pc\obj\*.obj > Microsoft (R) Incremental Linker Version 9.00.21022.08 > Copyright (C) Microsoft Corporation. All rights reserved. > adb_ServiceHeaderType.obj : error LNK2019: unresolved external symbol > _axutil_xml_quote_string referenced in function _adb_Service > [EMAIL PROTECTED] > adb_XXXType.obj : error LNK2001: unresolved external symbol > _axutil_xml_quote_string > adb_YYYType.obj : error LNK2001: unresolved external symbol > _axutil_xml_quote_string > adb_WarningType.obj : error LNK2001: unresolved external symbol > _axutil_xml_quote_string > adb_AAAType.obj : error LNK2001: unresolved external symbol > _axutil_xml_quote_string > adb_Type.obj : error LNK2001: unresolved external symbol > _axutil_xml_quote_string > adb_WWWType.obj : error LNK2001: unresolved external symbol > _axutil_xml_quote_string > adb_Type.obj : error LNK2001: unresolved external symbol > _axutil_xml_quote_string > adb_DDDType.obj : error LNK2001: unresolved external symbol > _axutil_xml_quote_string > adb_EEType.obj : error LNK2001: unresolved external symbol > _axutil_xml_quote_string > adb_EventType.obj : error LNK2001: unresolved external symbol > _axutil_xml_quote_string > adb_Type.obj : error LNK2001: unresolved external symbol > _axutil_xml_quote_string > adb_BusinessExceptionType.obj : error LNK2001: unresolved external symbol > _axutil_xml_quote_string > adb_RRR.obj : error LNK2001: unresolved external symbol > _axutil_xml_quote_string > adb_FFF.obj : error LNK2001: unresolved external symbol > _axutil_xml_quote_string > adb_III.obj : error LNK2001: unresolved external symbol > _axutil_xml_quote_string > axis2_stub_ABCService.obj : error LNK2019: unresolved external symbol > _axis2_msg_increment_ref referenced in function > _axis2_stub_populate_services_for_ABCService > D:\project3.2\axis2c\samples\client\pc\obj\pc.exe : fatal error LNK1120: 2 > unresolved externals -- 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] Updated: (AXIS2C-1111) INSTALL file should be updated to have information of Guththila parser as default
[ https://issues.apache.org/jira/browse/AXIS2C-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal updated AXIS2C-: Fix Version/s: (was: 1.4.0) 1.4.1 will fix in next release (1.4.1) > INSTALL file should be updated to have information of Guththila parser as > default > - > > Key: AXIS2C- > URL: https://issues.apache.org/jira/browse/AXIS2C- > Project: Axis2-C > Issue Type: Bug > Components: documentation >Affects Versions: Current (Nightly) > Environment: All >Reporter: Dushshantha Chandradasa > Fix For: 1.4.1 > > > INSTALL file should be updated to have information of Guththila parser as > default. This should go to html docs as well. -- 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] Updated: (AXIS2C-1114) Copy codegen samples into Windows Binary pack
[ https://issues.apache.org/jira/browse/AXIS2C-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal updated AXIS2C-1114: Fix Version/s: (was: 1.4.0) 1.4.1 will fix in next release (1.4.1) > Copy codegen samples into Windows Binary pack > - > > Key: AXIS2C-1114 > URL: https://issues.apache.org/jira/browse/AXIS2C-1114 > Project: Axis2-C > Issue Type: Bug > Components: build system (Windows) >Affects Versions: Current (Nightly) > Environment: Windows >Reporter: Dushshantha Chandradasa > Fix For: 1.4.1 > > > Copy codegen samples into Windows Binary pack. -- 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] Created: (AXIS2C-1127) make test doens't work in svn head
make test doens't work in svn head -- Key: AXIS2C-1127 URL: https://issues.apache.org/jira/browse/AXIS2C-1127 Project: Axis2-C Issue Type: Bug Components: build system, build system (Unix/Linux) Affects Versions: 1.4.0 Reporter: Dinesh Premalal Fix For: 1.4.1 though we have couple of tests in place , seems make tests doesn't work properly -- 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-1106) Build failures with --enable-tests on 64 bit linux with GCC
[ https://issues.apache.org/jira/browse/AXIS2C-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-1106. - Resolution: Fixed Fix Version/s: 1.3.1 patch applied ! Many thanks for Steve ! > Build failures with --enable-tests on 64 bit linux with GCC > --- > > Key: AXIS2C-1106 > URL: https://issues.apache.org/jira/browse/AXIS2C-1106 > Project: Axis2-C > Issue Type: Bug > Components: tests >Affects Versions: Current (Nightly) > Environment: CentOS 4.6 64 bit, gcc 3.4.6 >Reporter: Steve Nairn >Assignee: Dinesh Premalal >Priority: Minor > Fix For: 1.3.1 > > Attachments: axis2c.patch > > > There's a problem compiling some of the test modules on 64 bit linux with GCC > when configured with --enable-tests. > In all cases the problems are because some function declarations are not > visible in the test module so the functions are implicitly declared as > returning "int". This value os then cast to a pointer so generates a warning > about "cast to pointer from integer of different size". Because the > configuration script adds "-Werror" to CFLAGS if compiling with GCC this is > counted as an error. > The problem modules are all in util: > util/test/utils/utils_test.c > util/test/string_util/string_util_test.c > util/test/properties/property_test.c > The problems utils_test.c and string_util_test.c are easily solved by > "#include"ing the appropriate header. > The problem with property_test.c is not as simple as the offending function > (axutil_properties_read) does not appear in a header file. In this case it's > probably safest to just declare it in property_test.c (as I see it it can't > just be added to util/include/axutil_properties.h as it would need to be > marked AXIS2_EXTERN which would change the ABI of the axutil DSO). > The attached patch fixes the problem. > Cheers, > Steve Nairn -- 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-1106) Build failures with --enable-tests on 64 bit linux with GCC
[ https://issues.apache.org/jira/browse/AXIS2C-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal reassigned AXIS2C-1106: --- Assignee: Dinesh Premalal > Build failures with --enable-tests on 64 bit linux with GCC > --- > > Key: AXIS2C-1106 > URL: https://issues.apache.org/jira/browse/AXIS2C-1106 > Project: Axis2-C > Issue Type: Bug > Components: tests >Affects Versions: Current (Nightly) > Environment: CentOS 4.6 64 bit, gcc 3.4.6 >Reporter: Steve Nairn >Assignee: Dinesh Premalal >Priority: Minor > Attachments: axis2c.patch > > > There's a problem compiling some of the test modules on 64 bit linux with GCC > when configured with --enable-tests. > In all cases the problems are because some function declarations are not > visible in the test module so the functions are implicitly declared as > returning "int". This value os then cast to a pointer so generates a warning > about "cast to pointer from integer of different size". Because the > configuration script adds "-Werror" to CFLAGS if compiling with GCC this is > counted as an error. > The problem modules are all in util: > util/test/utils/utils_test.c > util/test/string_util/string_util_test.c > util/test/properties/property_test.c > The problems utils_test.c and string_util_test.c are easily solved by > "#include"ing the appropriate header. > The problem with property_test.c is not as simple as the offending function > (axutil_properties_read) does not appear in a header file. In this case it's > probably safest to just declare it in property_test.c (as I see it it can't > just be added to util/include/axutil_properties.h as it would need to be > marked AXIS2_EXTERN which would change the ABI of the axutil DSO). > The attached patch fixes the problem. > Cheers, > Steve Nairn -- 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] Commented: (AXIS2C-1109) axutil_network_handler_open_socket incorrectly assumes that all legal descriptors are >=0
[
https://issues.apache.org/jira/browse/AXIS2C-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589840#action_12589840
]
Dinesh Premalal commented on AXIS2C-1109:
-
Pim,
Could you please provide a patch ? It is more easier to test and apply to
svn head.
thanks,
Dinesh
> axutil_network_handler_open_socket incorrectly assumes that all legal
> descriptors are >=0
> -
>
> Key: AXIS2C-1109
> URL: https://issues.apache.org/jira/browse/AXIS2C-1109
> Project: Axis2-C
> Issue Type: Bug
>Affects Versions: 1.3.0
> Environment: windows xp, VS.2005
>Reporter: Pim Philipse
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> The line
> if ((sock = socket(AF_INET, SOCK_STREAM, 0)) < 0)
> does not work as expected under Windows, since winsock socket() returns
> INVALID_SOCKET on error, which happens to be 0.
> As a result, the next call to winsock fails, which is most confusing when
> trying to resolve a problem.
> Additionally, the error reporting is very terse. I have added a diagnostic
> function that gives the specific error (under windows):
> #define ERRBUFSIZE 300
> void
> get_socket_error(char *buf)
> {
> LPVOID lpMsgBuf;
> int rc = WSAGetLastError();
> sprintf( buf, "Winsock error %d: ", rc );
> FormatMessage(
>FORMAT_MESSAGE_ALLOCATE_BUFFER | FORMAT_MESSAGE_FROM_SYSTEM,
>NULL,
>rc,
>MAKELANGID(LANG_NEUTRAL, SUBLANG_DEFAULT), // Default language
>(LPTSTR) &lpMsgBuf,
>0,
>NULL
> );
> strncat( buf, (char*)lpMsgBuf, ERRBUFSIZE - strlen( buf ) - 1 );
> LocalFree( lpMsgBuf );
> }
> and then the error handling is invoked as, f.e.:
> if ((sock = socket(AF_INET, SOCK_STREAM, 0)) == AXIS2_INVALID_SOCKET)
> /*nnn AF_INET is not defined in sys/socket.h but PF_INET*/
> {
> char buf[ERRBUFSIZE];
> AXIS2_ERROR_SET(env->error, AXIS2_ERROR_SOCKET_ERROR, AXIS2_FAILURE);
> get_socket_error(buf);
> AXIS2_LOG_DEBUG(env->log, AXIS2_LOG_SI, buf);
> return AXIS2_INVALID_SOCKET;
> }
--
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-1105) libcurl stream not free properly
[ https://issues.apache.org/jira/browse/AXIS2C-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-1105. - Resolution: Fixed Fix Version/s: 1.3.1 patch applied ! Thanks Steve ! > libcurl stream not free properly > > > Key: AXIS2C-1105 > URL: https://issues.apache.org/jira/browse/AXIS2C-1105 > Project: Axis2-C > Issue Type: Bug > Components: core/transport >Affects Versions: 1.3.0, 1.3.1 > Environment: CentOS 4.6 >Reporter: Steve Nairn >Assignee: Dinesh Premalal > Fix For: 1.3.1 > > Attachments: axis2c.patch > > > When libcurl is enabled the function axis2_libcurl_send() in axis2_libcurl.c > creates an in stream by calling axutil_stream_create_libcurl(). This stream > should be freed with libcurl_stream_free() but it is freed with > axutil_stream_free_void_arg() instead. > In most cases this is not an issue. However, when > axutil_stream_create_libcurl() allocates space for a libcurl_stream_impl > struct it does not initialise the part of the struct that holds the > axutil_stream_t. If the space that is allocated happens to hold values such > that the stream_type field of the axutil_stream_t is set to zero and the > buffer_head field is set to non-zero then this will cause a segmentation > violation (this is how the bug affected me). > The solution is to set the free func on the property to libcurl_stream_free() > rather than axutil_stream_free_void_arg(). I'll try and attach a patch > against a Subversion checkout to this issue (I'm pretty new to Jira). > Cheers, > Steve Nairn -- 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-1105) libcurl stream not free properly
[ https://issues.apache.org/jira/browse/AXIS2C-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal reassigned AXIS2C-1105: --- Assignee: Dinesh Premalal > libcurl stream not free properly > > > Key: AXIS2C-1105 > URL: https://issues.apache.org/jira/browse/AXIS2C-1105 > Project: Axis2-C > Issue Type: Bug > Components: core/transport >Affects Versions: 1.3.0, 1.3.1 > Environment: CentOS 4.6 >Reporter: Steve Nairn >Assignee: Dinesh Premalal > Attachments: axis2c.patch > > > When libcurl is enabled the function axis2_libcurl_send() in axis2_libcurl.c > creates an in stream by calling axutil_stream_create_libcurl(). This stream > should be freed with libcurl_stream_free() but it is freed with > axutil_stream_free_void_arg() instead. > In most cases this is not an issue. However, when > axutil_stream_create_libcurl() allocates space for a libcurl_stream_impl > struct it does not initialise the part of the struct that holds the > axutil_stream_t. If the space that is allocated happens to hold values such > that the stream_type field of the axutil_stream_t is set to zero and the > buffer_head field is set to non-zero then this will cause a segmentation > violation (this is how the bug affected me). > The solution is to set the free func on the property to libcurl_stream_free() > rather than axutil_stream_free_void_arg(). I'll try and attach a patch > against a Subversion checkout to this issue (I'm pretty new to Jira). > Cheers, > Steve Nairn -- 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] Commented: (AXIS2C-595) XPath support in AXIOM
[ https://issues.apache.org/jira/browse/AXIS2C-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586778#action_12586778 ] Dinesh Premalal commented on AXIS2C-595: We have gsoc-2008 project related to issue. Whoever working on that project please make sure to update this issue accordingly . > XPath support in AXIOM > -- > > Key: AXIS2C-595 > URL: https://issues.apache.org/jira/browse/AXIS2C-595 > Project: Axis2-C > Issue Type: New Feature > Components: xml/om > Environment: Any >Reporter: Malinda Kaushalye Kapuruge > > We need to have the X-Path support in AXIOM/C. This is essential in many > scenarios where we need to specify a particular set of XML nodes. On example > comes with WS-Security Policy where we have to specify a particular node that > is needed to be encrypted/signed. Due to lack of X-Path support in AXIOM we > are forced to find alternative methods. -- 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-1086) In function axis2_op_register_op_ctx() failure is logged and returned in a working path.
[
https://issues.apache.org/jira/browse/AXIS2C-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Premalal resolved AXIS2C-1086.
-
Resolution: Fixed
Fix Version/s: 1.3.1
This was happened because of the incorrect sequence of the functions that we
called. I fixed this issue and change the log level into warning.
> In function axis2_op_register_op_ctx() failure is logged and returned in a
> working path.
>
>
> Key: AXIS2C-1086
> URL: https://issues.apache.org/jira/browse/AXIS2C-1086
> Project: Axis2-C
> Issue Type: Bug
>Reporter: Damitha Kumarage
>Assignee: Dinesh Premalal
> Fix For: 1.3.1
>
>
> In the following code of axis2_op_register_op_ctx() function
> msg_id = axis2_msg_ctx_get_msg_id(msg_ctx, env);
> if (!msg_id)
> {
> AXIS2_LOG_ERROR(env->log, AXIS2_LOG_SI,
> "Message id not found for message context while "\
> "registering operation context for operation %s", opname);
> return AXIS2_FAILURE;
> }
> When message id is not found in the messages context it is correctly logged
> as error and returned failure. However every places from which this function
> called, status is not handled and although error is logged and failure
> returned still code work successfully. This is behaviour is not acceptable.
--
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-1086) In function axis2_op_register_op_ctx() failure is logged and returned in a working path.
[
https://issues.apache.org/jira/browse/AXIS2C-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Premalal reassigned AXIS2C-1086:
---
Assignee: Dinesh Premalal
> In function axis2_op_register_op_ctx() failure is logged and returned in a
> working path.
>
>
> Key: AXIS2C-1086
> URL: https://issues.apache.org/jira/browse/AXIS2C-1086
> Project: Axis2-C
> Issue Type: Bug
>Reporter: Damitha Kumarage
>Assignee: Dinesh Premalal
>
> In the following code of axis2_op_register_op_ctx() function
> msg_id = axis2_msg_ctx_get_msg_id(msg_ctx, env);
> if (!msg_id)
> {
> AXIS2_LOG_ERROR(env->log, AXIS2_LOG_SI,
> "Message id not found for message context while "\
> "registering operation context for operation %s", opname);
> return AXIS2_FAILURE;
> }
> When message id is not found in the messages context it is correctly logged
> as error and returned failure. However every places from which this function
> called, status is not handled and although error is logged and failure
> returned still code work successfully. This is behaviour is not acceptable.
--
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-915) Axis2/C licensing issue with it's dependencies
[ https://issues.apache.org/jira/browse/AXIS2C-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-915. Resolution: Fixed > Axis2/C licensing issue with it's dependencies > --- > > Key: AXIS2C-915 > URL: https://issues.apache.org/jira/browse/AXIS2C-915 > Project: Axis2-C > Issue Type: Improvement >Affects Versions: 1.2.0 >Reporter: Dinesh Premalal >Assignee: Dinesh Premalal > Fix For: 1.3.0 > > Attachments: LICENSE > > > Need to figure out how to handle licensing of Axis2/C dependencies properly. -- 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] Created: (AXIS2C-1089) Hello Client in manual Broken
Hello Client in manual Broken - Key: AXIS2C-1089 URL: https://issues.apache.org/jira/browse/AXIS2C-1089 Project: Axis2-C Issue Type: Bug Components: documentation Affects Versions: 1.3.0 Reporter: Dinesh Premalal hello_client.c is broken, please follow this link for more info http://marc.info/?l=axis-c-dev&m=120658792802310&w=2 -- 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] Commented: (AXIS2C-1011) Docs doensn't copy into docs directory.
[ https://issues.apache.org/jira/browse/AXIS2C-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572779#action_12572779 ] Dinesh Premalal commented on AXIS2C-1011: - AUTHORS file is empty in "deploy" directory. "deploy" directory is a directory where axis2/c install after doing "make install". > Docs doensn't copy into docs directory. > --- > > Key: AXIS2C-1011 > URL: https://issues.apache.org/jira/browse/AXIS2C-1011 > Project: Axis2-C > Issue Type: Bug > Components: build system (Unix/Linux) >Affects Versions: 1.2.0, Current (Nightly) >Reporter: Dinesh Premalal > Fix For: 1.3.0 > > > Before release RC3, I'm doing some basic testing with release pack, After I > make install 1.3.0 RC3 release pack , no docs available in deploy/docs > directory. -- 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] Created: (AXIS2C-1011) Docs doensn't copy into docs directory.
Docs doensn't copy into docs directory. --- Key: AXIS2C-1011 URL: https://issues.apache.org/jira/browse/AXIS2C-1011 Project: Axis2-C Issue Type: Bug Components: build system (Unix/Linux) Affects Versions: 1.2.0, Current (Nightly) Reporter: Dinesh Premalal Fix For: 1.3.0 Before release RC3, I'm doing some basic testing with release pack, After I make install 1.3.0 RC3 release pack , no docs available in deploy/docs directory. -- 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] Commented: (AXIS2C-1011) Docs doensn't copy into docs directory.
[ https://issues.apache.org/jira/browse/AXIS2C-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572774#action_12572774 ] Dinesh Premalal commented on AXIS2C-1011: - This issue isn't available in svn head. > Docs doensn't copy into docs directory. > --- > > Key: AXIS2C-1011 > URL: https://issues.apache.org/jira/browse/AXIS2C-1011 > Project: Axis2-C > Issue Type: Bug > Components: build system (Unix/Linux) >Affects Versions: 1.2.0, Current (Nightly) >Reporter: Dinesh Premalal > Fix For: 1.3.0 > > > Before release RC3, I'm doing some basic testing with release pack, After I > make install 1.3.0 RC3 release pack , no docs available in deploy/docs > directory. -- 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] Created: (AXIS2C-1006) log levels doesn't work properly
log levels doesn't work properly Key: AXIS2C-1006 URL: https://issues.apache.org/jira/browse/AXIS2C-1006 Project: Axis2-C Issue Type: Bug Components: util Affects Versions: 1.2.0, Current (Nightly) Reporter: Dinesh Premalal Fix For: 1.3.0 I run axis2_http_server with following arguments ./axis2_http_server -l0 -p9091 Here log level set to "critical", In that case we are suppose to log down, critical errors only (correct me if I'm wrong), but it logs errors also. here is the log message: [Tue Feb 26 15:34:27 2008] [error] libxml2_reader_wrapper.c(945) Extra content at the end of the document -- SEVERITY_ERROR [Tue Feb 26 15:34:27 2008] [error] libxml2_reader_wrapper.c(456) error occured in reading xml stream [Tue Feb 26 15:34:27 2008] [critical] soap_builder.c(812) SOAP message does not have a SOAP envelope element -- 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] Created: (AXIS2C-1005) dual clients report an error in log
dual clients report an error in log --- Key: AXIS2C-1005 URL: https://issues.apache.org/jira/browse/AXIS2C-1005 Project: Axis2-C Issue Type: Bug Affects Versions: Current (Nightly) Reporter: Dinesh Premalal Fix For: 1.3.0 Although echo_blocking_dual and echo_non_blocking_dual clients executes successfully , they dump following message into log. [Tue Feb 26 15:30:01 2008] [error] libxml2_reader_wrapper.c(945) Extra content at the end of the document -- SEVERITY_ERROR [Tue Feb 26 15:30:01 2008] [error] libxml2_reader_wrapper.c(456) error occured in reading xml stream [Tue Feb 26 15:30:01 2008] [critical] soap_builder.c(812) SOAP message does not have a SOAP envelope element -- 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] Commented: (AXIS2C-675) Detach node does not handle namespaces
[ https://issues.apache.org/jira/browse/AXIS2C-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571325#action_12571325 ] Dinesh Premalal commented on AXIS2C-675: Bill, I applied the patch and tested in the svn head, for me It didn't give any problem. Ill commit it to the svn head. > Detach node does not handle namespaces > -- > > Key: AXIS2C-675 > URL: https://issues.apache.org/jira/browse/AXIS2C-675 > Project: Axis2-C > Issue Type: Bug > Components: xml/om >Reporter: Jamie Lyon >Assignee: Bill Mitchell > Attachments: diff.txt > > > When detaching a node from a parent, if the current node or any of it's > children have any namespaces declared in it's parent or above, when the node > is detached, and the parent freed, any namespace references are lost. -- 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] Reopened: (AXIS2C-677) Clone method required for axiom_node
[ https://issues.apache.org/jira/browse/AXIS2C-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal reopened AXIS2C-677: reopened the issue as discussed in this thread. http://marc.info/?t=12028790841&r=2&w=2 > Clone method required for axiom_node > > > Key: AXIS2C-677 > URL: https://issues.apache.org/jira/browse/AXIS2C-677 > Project: Axis2-C > Issue Type: Bug > Components: xml/om >Reporter: Jamie Lyon > > There is no clone method for axiom_node in the current implementation of > axiom/c, it should have one as the axiom/java version does. > Without a clone method, there is no easy way to alter a tree without > affecting the original. -- 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-985) There's a leak due to wrong token create
[ https://issues.apache.org/jira/browse/AXIS2C-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-985. Resolution: Fixed Fix Version/s: (was: Current (Nightly)) 1.3.0 Committed revision 627666. Patch applied ! Thanks Lahiru. > There's a leak due to wrong token create > - > > Key: AXIS2C-985 > URL: https://issues.apache.org/jira/browse/AXIS2C-985 > Project: Axis2-C > Issue Type: Bug >Affects Versions: Current (Nightly) > Environment: Ubuntu 7.10 >Reporter: Lahiru Gunathilake >Assignee: Dinesh Premalal > Fix For: 1.3.0 > > Attachments: diff_leak_fix.txt > > > There's a wrong token creation in guththila_init method and it cause a > memory leak. -- 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-972) axiom util tests installed in bin/samples directory
[ https://issues.apache.org/jira/browse/AXIS2C-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-972. Resolution: Fixed committed to 619302. > axiom util tests installed in bin/samples directory > --- > > Key: AXIS2C-972 > URL: https://issues.apache.org/jira/browse/AXIS2C-972 > Project: Axis2-C > Issue Type: Bug > Components: build system (Unix/Linux) >Affects Versions: 1.2.0 >Reporter: Dinesh Premalal >Assignee: Dinesh Premalal >Priority: Minor > Fix For: 1.3.0 > > > after installing I can see that , axiom util test binary get installed under > bin/samples/ directory. -- 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] Created: (AXIS2C-972) axiom util tests installed in bin/samples directory
axiom util tests installed in bin/samples directory --- Key: AXIS2C-972 URL: https://issues.apache.org/jira/browse/AXIS2C-972 Project: Axis2-C Issue Type: Bug Components: build system (Unix/Linux) Affects Versions: 1.2.0 Reporter: Dinesh Premalal Assignee: Dinesh Premalal Priority: Minor Fix For: 1.3.0 after installing I can see that , axiom util test binary get installed under bin/samples/ directory. -- 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-971) configure.ac carries entries with XMPP and iksemel
[ https://issues.apache.org/jira/browse/AXIS2C-971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-971. Resolution: Fixed Committed revision 619290. > configure.ac carries entries with XMPP and iksemel > -- > > Key: AXIS2C-971 > URL: https://issues.apache.org/jira/browse/AXIS2C-971 > Project: Axis2-C > Issue Type: Bug > Components: build system (Unix/Linux) >Affects Versions: 1.2.0 >Reporter: Dinesh Premalal >Assignee: Dinesh Premalal > Fix For: 1.3.0 > > > configure.ac have entries on XMPP and iksemel which is not part of Axis2/C -- 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] Created: (AXIS2C-971) configure.ac carries entries with XMPP and iksemel
configure.ac carries entries with XMPP and iksemel -- Key: AXIS2C-971 URL: https://issues.apache.org/jira/browse/AXIS2C-971 Project: Axis2-C Issue Type: Bug Components: build system (Unix/Linux) Affects Versions: 1.2.0 Reporter: Dinesh Premalal Assignee: Dinesh Premalal Fix For: 1.3.0 configure.ac have entries on XMPP and iksemel which is not part of Axis2/C -- 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] Updated: (AXIS2C-829) server crashes when loading services which are using a module which is not deployed
[ https://issues.apache.org/jira/browse/AXIS2C-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal updated AXIS2C-829: --- Fix Version/s: 1.3.0 I think we can resolve this for 1.3.0 > server crashes when loading services which are using a module which is not > deployed > --- > > Key: AXIS2C-829 > URL: https://issues.apache.org/jira/browse/AXIS2C-829 > Project: Axis2-C > Issue Type: Bug > Components: core/engine >Affects Versions: 1.2.0 > Environment: Windows XP >Reporter: S.Uthaiyashankar > Fix For: 1.3.0 > > > If a service is deployed which is using a module and that particular module > is not deployed, then when starting the server, it crashes. -- 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] Updated: (AXIS2C-902) echo_blocking_dual occasionally segfaulted the simple axis server.
[ https://issues.apache.org/jira/browse/AXIS2C-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal updated AXIS2C-902: --- Fix Version/s: 1.3.0 > echo_blocking_dual occasionally segfaulted the simple axis server. > -- > > Key: AXIS2C-902 > URL: https://issues.apache.org/jira/browse/AXIS2C-902 > Project: Axis2-C > Issue Type: Bug > Components: samples >Affects Versions: Current (Nightly) > Environment: Ubuntu 7.10 (Gutsy Gibbon), CURL + libxml2, TCPMon >Reporter: Senaka Fernando > Fix For: 1.3.0 > > > I have been running echo_blocking_dual in a loop and found out that > occasionally the simple axis http server segfaults. > My system memory consumption is 575MB/1011MB and swap is 1.5GB/3.8GB. Also > note that this problem occurred on Ubuntu 7.10 system, with CURL transport. > And, I ran with the TCPMon utility actively monitoring the payloads. > This is the tail of my axis2.log > [Thu Jan 17 00:27:36 2008] [debug] http_transport_sender.c(228) > ctx_epr:http://localhost:6060/axis2/services/__ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__ > [Thu Jan 17 00:27:36 2008] [debug] http_transport_sender.c(711) OP name > axutil_qname_get_localpart = http://www.w3.org/2004/08/wsdl/in-out > [Thu Jan 17 00:27:36 2008] [error] libxml2_reader_wrapper.c(945) Extra > content at the end of the document > -- SEVERITY_ERROR > [Thu Jan 17 00:27:36 2008] [error] libxml2_reader_wrapper.c(456) error > occured in reading xml stream > [Thu Jan 17 00:27:36 2008] [critical] soap_builder.c(803) SOAP message does > not have a SOAP envelope element > [Thu Jan 17 00:27:36 2008] [debug] engine.c(302) Axis2 engine receive > completed! > Please note that even though the server segfaulted, I got a response > "HTTP/1.1 202 Accepted > " for the last request, the one which made the server segfault. All further > requests failed as the server is not operational. -- 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] Commented: (AXIS2C-924) Compiling source on HP-UX11.11v2
[ https://issues.apache.org/jira/browse/AXIS2C-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566042#action_12566042 ] Dinesh Premalal commented on AXIS2C-924: Abhay, Did you able to resolve this issue ? > Compiling source on HP-UX11.11v2 > > > Key: AXIS2C-924 > URL: https://issues.apache.org/jira/browse/AXIS2C-924 > Project: Axis2-C > Issue Type: Bug > Components: build system (Unix/Linux) >Affects Versions: 1.2.0 > Environment: HP-UX 11.11v2 - aC++ compiler. >Reporter: Abhay Bhave > Attachments: diff.txt > > > I think I am able to configure and make (make & make install) the source > after lot of struggle. > I am using LIBXML2. I don't have Apache installed to test WSDL2C tool. > The sample services did not compile and didn't get installed. > The axis2c_http_server is created in AXIS2C_HOME/bin but it can not be > started. It complains with error 34. > The sample code complains about getopt.h, strcasecomp etc. > Has any one successfully installed and tested the samples on HP-UX 11.11 or > HP-UX11.23v1 (Itanium)? > How to get over the getopt.h and strcasecomp issue? > Is it possible to get the WSDL2C tool without Apache being installed? > Thanks -- 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] Commented: (AXIS2C-902) echo_blocking_dual occasionally segfaulted the simple axis server.
[ https://issues.apache.org/jira/browse/AXIS2C-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566041#action_12566041 ] Dinesh Premalal commented on AXIS2C-902: Senaka, Is this segfault still occur ? I tried on my debian machine but I was unable to reproduce it. > echo_blocking_dual occasionally segfaulted the simple axis server. > -- > > Key: AXIS2C-902 > URL: https://issues.apache.org/jira/browse/AXIS2C-902 > Project: Axis2-C > Issue Type: Bug > Components: samples >Affects Versions: Current (Nightly) > Environment: Ubuntu 7.10 (Gutsy Gibbon), CURL + libxml2, TCPMon >Reporter: Senaka Fernando > > I have been running echo_blocking_dual in a loop and found out that > occasionally the simple axis http server segfaults. > My system memory consumption is 575MB/1011MB and swap is 1.5GB/3.8GB. Also > note that this problem occurred on Ubuntu 7.10 system, with CURL transport. > And, I ran with the TCPMon utility actively monitoring the payloads. > This is the tail of my axis2.log > [Thu Jan 17 00:27:36 2008] [debug] http_transport_sender.c(228) > ctx_epr:http://localhost:6060/axis2/services/__ANONYMOUS_SERVICE__/__OPERATION_OUT_IN__ > [Thu Jan 17 00:27:36 2008] [debug] http_transport_sender.c(711) OP name > axutil_qname_get_localpart = http://www.w3.org/2004/08/wsdl/in-out > [Thu Jan 17 00:27:36 2008] [error] libxml2_reader_wrapper.c(945) Extra > content at the end of the document > -- SEVERITY_ERROR > [Thu Jan 17 00:27:36 2008] [error] libxml2_reader_wrapper.c(456) error > occured in reading xml stream > [Thu Jan 17 00:27:36 2008] [critical] soap_builder.c(803) SOAP message does > not have a SOAP envelope element > [Thu Jan 17 00:27:36 2008] [debug] engine.c(302) Axis2 engine receive > completed! > Please note that even though the server segfaulted, I got a response > "HTTP/1.1 202 Accepted > " for the last request, the one which made the server segfault. All further > requests failed as the server is not operational. -- 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] Commented: (AXIS2C-915) Axis2/C licensing issue with it's dependencies
[ https://issues.apache.org/jira/browse/AXIS2C-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566032#action_12566032 ] Dinesh Premalal commented on AXIS2C-915: I look into preparing check list for addressing licensing issue. After looking into details , I realize that that checklist will be more or less same as this document [1], we need to get almost all details from it. Therefore I think , it is better to use this document as our checklist or guideline document. AFAIU, It explains well all the issues that we need to address. Thoughts ?? 1. http://people.apache.org/~cliffs/3party.html > Axis2/C licensing issue with it's dependencies > --- > > Key: AXIS2C-915 > URL: https://issues.apache.org/jira/browse/AXIS2C-915 > Project: Axis2-C > Issue Type: Improvement >Affects Versions: 1.2.0 >Reporter: Dinesh Premalal >Assignee: Dinesh Premalal > Fix For: 1.3.0 > > Attachments: LICENSE > > > Need to figure out how to handle licensing of Axis2/C dependencies properly. -- 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] Commented: (AXIS2C-915) Axis2/C licensing issue with it's dependencies
[ https://issues.apache.org/jira/browse/AXIS2C-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566030#action_12566030 ] Dinesh Premalal commented on AXIS2C-915: Does somebody has an idea about how to deal with licensing with IIS module ? > Axis2/C licensing issue with it's dependencies > --- > > Key: AXIS2C-915 > URL: https://issues.apache.org/jira/browse/AXIS2C-915 > Project: Axis2-C > Issue Type: Improvement >Affects Versions: 1.2.0 >Reporter: Dinesh Premalal >Assignee: Dinesh Premalal > Fix For: 1.3.0 > > Attachments: LICENSE > > > Need to figure out how to handle licensing of Axis2/C dependencies properly. -- 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] Updated: (AXIS2C-941) IIS Module: fails with large data element
[ https://issues.apache.org/jira/browse/AXIS2C-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal updated AXIS2C-941: --- Priority: Major (was: Blocker) This issue is not a blocker for Axis2/C, I'm downgrading priority. > IIS Module: fails with large data element > - > > Key: AXIS2C-941 > URL: https://issues.apache.org/jira/browse/AXIS2C-941 > Project: Axis2-C > Issue Type: Bug > Components: transport/http >Affects Versions: Current (Nightly) > Environment: Windows XP, IIS 5.1 >Reporter: Dave Meier > Attachments: aewebservicesaxis70.wsdl > > > I have a web service that takes the following as input. Here is the wsdl: > > > > > > maxOccurs="1" nillable="false"/> > > > > > With the axis2_http_server.exe it works fine with a 163KB file, where the > contents of the file are written in base64 into the "encodedContents" > element. But when I run the IIS module and run the same client test, I get > back an error saying that the "encodedContents" element is NULL. > I tried a 1KB file with the IIS module and that worked great. So there > appears to be something limiting the sending of a large element when using > the IIS module. -- 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] Commented: (AXIS2C-791) On in-out message flow that fails with no response, no error code or misleading error code is returned, expected error number 3.
[
https://issues.apache.org/jira/browse/AXIS2C-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565396#action_12565396
]
Dinesh Premalal commented on AXIS2C-791:
Hi Bill,
If time permits , please look into this issue. I guess you could resolve
this issue.
> On in-out message flow that fails with no response, no error code or
> misleading error code is returned, expected error number 3.
> --
>
> Key: AXIS2C-791
> URL: https://issues.apache.org/jira/browse/AXIS2C-791
> Project: Axis2-C
> Issue Type: Bug
> Components: core/clientapi
>Affects Versions: 1.1.0
> Environment: Windows XP, Visual Studio 2005
>Reporter: Bill Mitchell
>Assignee: Dinesh Premalal
>Priority: Minor
>
> If a blocking I/O is requested for an in-out message exchange and no response
> is received, axis2_svc_client_send_receive et.al. return a zero response
> pointer. But one would expect the errno variable to contain some value
> indicating the error.
> In op_client.c in axis2_op_client_two_way_send() there is code at the very
> end, when there is no response envelope, to ensure that an error code is
> returned:
> if (AXIS2_ERROR_GET_STATUS_CODE(env->error) != AXIS2_SUCCESS)
> {
> AXIS2_ERROR_SET(env->error,
>
> AXIS2_ERROR_BLOCKING_INVOCATION_EXPECTS_RESPONSE,
> AXIS2_FAILURE);
> if (engine)
> {
> axis2_engine_free(engine, env);
> engine = NULL;
> }
> axis2_msg_ctx_free(response, env);
> return NULL;
> }
> As you can see, the !=AXIS2_SUCCESS test should be ==AXIS2_SUCCESS, as the
> intent is to return error number 3 when no other error has been diagnosed.
> Unfortunately, even after this fix, in the nightly build of 11/27/07, there
> is a new bug that causes error number 3 to be replaced with an uninformative
> error 2, invalid null parameter. In svc_client, when the empty response is
> returned, axis2_op_client_add_msg_ctx() is called with an intentional null
> value clear the ctx.
> In the post 1.1 source, parameter validation has been added to
> axis2_op_client_add_msg_ctx() to diagnose this intended result as an error:
> AXIS2_EXTERN axis2_status_t AXIS2_CALL
> axis2_op_client_add_msg_ctx(
> axis2_op_client_t * op_client,
> const axutil_env_t * env,
> axis2_msg_ctx_t * mc)
> {
> axis2_msg_ctx_t *out_msg_ctx = NULL,
> *in_msg_ctx = NULL;
> axis2_msg_ctx_t **msg_ctx_map = NULL;
> AXIS2_PARAM_CHECK (env->error, op_client, AXIS2_FAILURE);
> AXIS2_PARAM_CHECK (env->error, mc, AXIS2_FAILURE);
> The second AXIS2_PARAM_CHECK should be removed.
> After making both these changes in the development shapshot, when the client
> receives no response, for example if the URL points to a non-running server,
> the client correctly receives error 3, Blocking invocation expects response.
--
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] Updated: (AXIS2C-791) On in-out message flow that fails with no response, no error code or misleading error code is returned, expected error number 3.
[
https://issues.apache.org/jira/browse/AXIS2C-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Premalal updated AXIS2C-791:
---
Assignee: Bill Mitchell (was: Dinesh Premalal)
> On in-out message flow that fails with no response, no error code or
> misleading error code is returned, expected error number 3.
> --
>
> Key: AXIS2C-791
> URL: https://issues.apache.org/jira/browse/AXIS2C-791
> Project: Axis2-C
> Issue Type: Bug
> Components: core/clientapi
>Affects Versions: 1.1.0
> Environment: Windows XP, Visual Studio 2005
>Reporter: Bill Mitchell
>Assignee: Bill Mitchell
>Priority: Minor
>
> If a blocking I/O is requested for an in-out message exchange and no response
> is received, axis2_svc_client_send_receive et.al. return a zero response
> pointer. But one would expect the errno variable to contain some value
> indicating the error.
> In op_client.c in axis2_op_client_two_way_send() there is code at the very
> end, when there is no response envelope, to ensure that an error code is
> returned:
> if (AXIS2_ERROR_GET_STATUS_CODE(env->error) != AXIS2_SUCCESS)
> {
> AXIS2_ERROR_SET(env->error,
>
> AXIS2_ERROR_BLOCKING_INVOCATION_EXPECTS_RESPONSE,
> AXIS2_FAILURE);
> if (engine)
> {
> axis2_engine_free(engine, env);
> engine = NULL;
> }
> axis2_msg_ctx_free(response, env);
> return NULL;
> }
> As you can see, the !=AXIS2_SUCCESS test should be ==AXIS2_SUCCESS, as the
> intent is to return error number 3 when no other error has been diagnosed.
> Unfortunately, even after this fix, in the nightly build of 11/27/07, there
> is a new bug that causes error number 3 to be replaced with an uninformative
> error 2, invalid null parameter. In svc_client, when the empty response is
> returned, axis2_op_client_add_msg_ctx() is called with an intentional null
> value clear the ctx.
> In the post 1.1 source, parameter validation has been added to
> axis2_op_client_add_msg_ctx() to diagnose this intended result as an error:
> AXIS2_EXTERN axis2_status_t AXIS2_CALL
> axis2_op_client_add_msg_ctx(
> axis2_op_client_t * op_client,
> const axutil_env_t * env,
> axis2_msg_ctx_t * mc)
> {
> axis2_msg_ctx_t *out_msg_ctx = NULL,
> *in_msg_ctx = NULL;
> axis2_msg_ctx_t **msg_ctx_map = NULL;
> AXIS2_PARAM_CHECK (env->error, op_client, AXIS2_FAILURE);
> AXIS2_PARAM_CHECK (env->error, mc, AXIS2_FAILURE);
> The second AXIS2_PARAM_CHECK should be removed.
> After making both these changes in the development shapshot, when the client
> receives no response, for example if the URL points to a non-running server,
> the client correctly receives error 3, Blocking invocation expects response.
--
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-604) Axis2/C Local Transport Implementation.
[ https://issues.apache.org/jira/browse/AXIS2C-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-604. Resolution: Won't Fix Fix Version/s: 1.3.0 I think , local transport implementation not going to happen in near future. I'm resolving this. > Axis2/C Local Transport Implementation. > --- > > Key: AXIS2C-604 > URL: https://issues.apache.org/jira/browse/AXIS2C-604 > Project: Axis2-C > Issue Type: New Feature > Components: core/transport >Reporter: Dinesh Premalal >Assignee: Dinesh Premalal > Fix For: 1.3.0 > > > It is better to have local transport implementation, to handle use cases in > same physical machine. We should try to get an advantage by skipping > serializing/deserializing stages. -- 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] Updated: (AXIS2C-915) Axis2/C licensing issue with it's dependencies
[ https://issues.apache.org/jira/browse/AXIS2C-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal updated AXIS2C-915: --- Fix Version/s: (was: Current (Nightly)) > Axis2/C licensing issue with it's dependencies > --- > > Key: AXIS2C-915 > URL: https://issues.apache.org/jira/browse/AXIS2C-915 > Project: Axis2-C > Issue Type: Improvement >Affects Versions: 1.2.0 >Reporter: Dinesh Premalal >Assignee: Dinesh Premalal > Fix For: 1.3.0 > > Attachments: LICENSE > > > Need to figure out how to handle licensing of Axis2/C dependencies properly. -- 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] Updated: (AXIS2C-933) guththila parser does not handle incomplete messages well, leading to an infinite loop or seg fault
[ https://issues.apache.org/jira/browse/AXIS2C-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal updated AXIS2C-933: --- Fix Version/s: 1.3.0 > guththila parser does not handle incomplete messages well, leading to an > infinite loop or seg fault > --- > > Key: AXIS2C-933 > URL: https://issues.apache.org/jira/browse/AXIS2C-933 > Project: Axis2-C > Issue Type: Bug > Components: guththila >Affects Versions: Current (Nightly) > Environment: Windows XP, Visual Studio 2005, guththila, libcurl >Reporter: Bill Mitchell > Fix For: 1.3.0 > > Attachments: diff.txt, diff2.txt > > > The code in the guththila parser has a couple of problems when the first > allocated buffer fills up and it attempts to read more data. First, when > allocating another buffer it doubled the size of all the buffers allocated to > this point, but then recorded the new buffer size as only equal to the size > of all the previous buffers. Second, after fixing the buffer allocation > issue, I discovered that the read into the buffer tried to read as much as > all the buffers to date, instead of just the amount remaining in the buffer > just allocated. There is also a subtle problem in the guththila_next_no_char > routine if last_start is not set, that it did not assure that all the > characters since next are moved to the newly allocated buffer. > While debugging this, because of other issues, I walked through the path of > an unexpected EOF in the middle of the incoming message, and discovered that > several while loops in the parser do not stop on EOF, but just keep reading > and reading and reading... -- 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] Updated: (AXIS2C-859) guththila parser fails to handle escape sequences for ampersand, less than, greater than
[ https://issues.apache.org/jira/browse/AXIS2C-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal updated AXIS2C-859: --- Fix Version/s: 1.3.0 > guththila parser fails to handle escape sequences for ampersand, less than, > greater than > > > Key: AXIS2C-859 > URL: https://issues.apache.org/jira/browse/AXIS2C-859 > Project: Axis2-C > Issue Type: Bug > Components: guththila >Affects Versions: Current (Nightly) > Environment: Windows XP, Visual Studio 2005, guththila parser, libcurl >Reporter: Bill Mitchell > Fix For: 1.3.0 > > Attachments: diff.txt, diff_1.txt, diff_2.txt, > guththila_xml_writer.diff > > > When an incoming message contains within text the escaped ampersand sequence, > "&", this sequence is being passed to the client as raw text without > being converted to the single ampersand character. Clearly, this action must > take place at the level of the parser, as only the parser knows whether it is > seeing simple text, and conversion is required, or text embedded in a CDATA > section, where conversion is not allowed. I have tested the build with the > libxml parser, and of course the libxml parser behaves correctly: the text > passed to the client contains only the single ampersand character, not the > escaped sequence. (See section 2.4 of XML 1.0 spec.) > Looking at the code, I expect the same problem occurs with all escaped > sequences, less than and greater than as well as ampersand, on both input and > output. I also don't see where CDATA sections are handled, but as I am not > seeing CDATA in the messages from the service I am hitting, I have not tested > this case. -- 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] Updated: (AXIS2C-963) Guththila neglects spacing and formatting between nodes whereas libxml2 preserves it.
[ https://issues.apache.org/jira/browse/AXIS2C-963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal updated AXIS2C-963: --- Fix Version/s: 1.3.0 > Guththila neglects spacing and formatting between nodes whereas libxml2 > preserves it. > - > > Key: AXIS2C-963 > URL: https://issues.apache.org/jira/browse/AXIS2C-963 > Project: Axis2-C > Issue Type: Bug > Components: guththila, xml/parser >Reporter: Senaka Fernando > Fix For: 1.3.0 > > > Guththila neglects spacing and formatting between nodes. This behavior > contradicts to that of libxml2. Thus, If I open a file then deserialize it > and build our OM Model, then print it to the terminal, I have lost the > formatting in the file. This is because the parser simply filters out the > whitespace. This behavior would make our parsing inconsistent. > Regards, > Senaka -- 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] Updated: (AXIS2C-944) guththila parser ignores XML scope rules on namespace declarations with the same prefix
[
https://issues.apache.org/jira/browse/AXIS2C-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Premalal updated AXIS2C-944:
---
Fix Version/s: 1.3.0
> guththila parser ignores XML scope rules on namespace declarations with the
> same prefix
> ---
>
> Key: AXIS2C-944
> URL: https://issues.apache.org/jira/browse/AXIS2C-944
> Project: Axis2-C
> Issue Type: Bug
> Components: guththila
>Affects Versions: Current (Nightly)
> Environment: Windows XP, Visual Studio 2005, guththila, libcurl
>Reporter: Bill Mitchell
> Fix For: 1.3.0
>
>
> The guththila parser looks for a match on the namespace prefix/URI from the
> outermost element inwards. This violates the scope rules for XML namespaces,
> see http://www.w3.org/TR/REC-xml-names/. This problem holds for both
> incoming messages in guththila_xml_parser.c and outgoing messages in
> guththila_xml_writer.c. Essentially every loop involving
> guththila_stack_get_by_index() is suspect, and either needs to start at
> (stack_size - 1) and go backwards, or fetch the namespace at the (stack_size
> - 1 - i) index.
> I uncovered this by inspection, not by testing, so there is some chance that
> my understanding is incorrect. But I looked at guththila_stack.c and indeed
> for index 0 it returns the outermost/first element pushed, so there is no
> tricky logic there to get the stack in the other order. Of course, one could
> indeed fix this problem by changing guththila_stack_get_by_index() to return
> the elements from the innermost/most recently pushed back out to the
> outermost. This would be the easiest fix to make, and the safest in that it
> would not change the logic in any of the existing loops, although it would
> seem less clear to the casual reader.
> In other words, the current logic:
> guththila_stack_get_by_index(
> guththila_stack_t * stack,
> int index,
> const axutil_env_t * env)
> {
> return index < stack->top ? stack->data[index] : NULL;
> }
> could be changed to read:
> {
> return index < stack->top ? stack->data[stack->top - index - 1] : NULL;
> }
--
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] Updated: (AXIS2C-620) Error handling in Neethi/C
[ https://issues.apache.org/jira/browse/AXIS2C-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal updated AXIS2C-620: --- Fix Version/s: 1.3.0 > Error handling in Neethi/C > -- > > Key: AXIS2C-620 > URL: https://issues.apache.org/jira/browse/AXIS2C-620 > Project: Axis2-C > Issue Type: Improvement >Reporter: Manjula Peiris > Fix For: 1.3.0 > > > Need to add Axis2/C error handling mechanisms to Neethi/C code. -- 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] Updated: (AXIS2C-710) pkg-config not detected properly during configure
[ https://issues.apache.org/jira/browse/AXIS2C-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal updated AXIS2C-710: --- Fix Version/s: 1.3.0 Affects Version/s: (was: 1.3.0) 1.1.0 > pkg-config not detected properly during configure > - > > Key: AXIS2C-710 > URL: https://issues.apache.org/jira/browse/AXIS2C-710 > Project: Axis2-C > Issue Type: Bug > Components: build system (Unix/Linux) >Affects Versions: 1.1.0 > Environment: Red Hat Enterprise Linux 4 with pkgconfig-0.15 RPM > installed >Reporter: Stefano Pettini >Assignee: Sanjaya Ratnaweera > Fix For: 1.3.0 > > > I cannot compile Axis2/C on RHEL4 because: > checking for LIBXML2... configure: error: The pkg-config script could not be > found or is too old. Make sure it > is in your PATH or set the PKG_CONFIG environment variable to the full > path to pkg-config. > I don't see the need of version 0.20 or higher, since the installed version, > 0.15, is able to retrieve LIBS and CFLAGS of libxml-2.0 without any problem. > By the way: > Alternatively, you may set the environment variables LIBXML2_CFLAGS > and LIBXML2_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > This doesn't work too, since I manually set those variables, here they are, > just copied from "set" output: > LIBXML2_CFLAGS=-I/usr/include/libxml2 > LIBXML2_LIBS='-lxml2 -lpthread -lz -lm' > But configure still try to use the pkg-config utility it doesn't like. > Upgrading the RPM is not an option, this would require an upgraded C library > too. > I solved modifying the configure script of axiom, lowering the required > pkg-config version from 0.20 to 0.15 and works perfectly. I think this fix > should be included in next releases. > Thank you! > Stefano -- 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] Updated: (AXIS2C-930) content-type has extra double quote character when Axis2/C server sends response to an mtom client request
[ https://issues.apache.org/jira/browse/AXIS2C-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal updated AXIS2C-930: --- Fix Version/s: 1.3.0 Priority: Major (was: Critical) > content-type has extra double quote character when Axis2/C server sends > response to an mtom client request > -- > > Key: AXIS2C-930 > URL: https://issues.apache.org/jira/browse/AXIS2C-930 > Project: Axis2-C > Issue Type: Bug >Affects Versions: Current (Nightly) > Environment: Windows XP >Reporter: Dave Meier > Fix For: 1.3.0 > > > I have a C# client that is working successfully with my Axis2/C Server. When > I change the WSE 3.0 Settings on my C# project to turn on client side MTOM, > the client sends the request using MIME. The server successfully handles the > request, but there is an extra double quote character in the content-type on > the http header of the response. > > Request Header: > > > Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client > Protocol 2.0.50727.1433) > > uIDPo6KPbDOqx/pMt0VEKaHAs9QAYPx6oFZ50EyMXAkb8ljpTRlS5s4B47BKtm491da5ZMYACAAA > > "" > localhost:9091 > multipart/related; type="application/xop+xml"; > boundary=--MIMEBoundary633366130598523034; start="<[EMAIL PROTECTED]>"; > start-info="text/xml; charset=utf-8" > 3174 > 100-continue > Keep-Alive > > -- > Response Header: > -- > > text/xml;charset=utf-8" > Keep-Alive > 8107 > > So I get an error on the client side: > System.ArgumentException was unhandled > Message="WSE2166: The content type has an incomplete quoted parameter." > Source="Microsoft.Web.Services3" > StackTrace: >at > Microsoft.Web.Services3.Mime.ContentTypeParser.ConsumeQuotedString(StringBuilder > sb) >at Microsoft.Web.Services3.Mime.ContentTypeParser.GetToken() >at Microsoft.Web.Services3.Mime.ContentTypeParser..ctor(String s) >at Microsoft.Web.Services3.Mime.MtomHelper.IsXopContentType(String > contentType) >at > Microsoft.Web.Services3.WebServicesClientProtocol.GetResponse(WebRequest > request, IAsyncResult result) >at > Microsoft.Web.Services3.WebServicesClientProtocol.GetWebResponse(WebRequest > request) >at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String > methodName, Object[] parameters) >at axis2client.aeaxisweb.aewebservicesaxis70Wse.CreatePrimaryItem(Auth > auth, String projectID, TTItem item, String submitTransID) in > D:\axis2client\Web References\aeaxisweb\Reference.cs:line 431 >at axis2client.AEClient.TestCreatePrimaryItem(myaeaxiswebservices > aeserv) in D:\axis2client\Client.cs:line 372 >at axis2client.AEClient.TestCreateItems(myaeaxiswebservices aeserv) in > D:\axis2client\Client.cs:line 584 >at axis2client.AEClient.Main(String[] args) in > D:\axis2client\Client.cs:line 671 >at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args) >at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence > assemblySecurity, String[] args) >at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly() >at System.Threading.ThreadHelper.ThreadStart_Context(Object state) >at System.Threading.ExecutionContext.Run(ExecutionContext > executionContext, ContextCallback callback, Object state) >at System.Threading.ThreadHelper.ThreadStart() -- 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] Updated: (AXIS2C-710) pkg-config not detected properly during configure
[ https://issues.apache.org/jira/browse/AXIS2C-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal updated AXIS2C-710: --- Affects Version/s: (was: 1.1.0) 1.3.0 > pkg-config not detected properly during configure > - > > Key: AXIS2C-710 > URL: https://issues.apache.org/jira/browse/AXIS2C-710 > Project: Axis2-C > Issue Type: Bug > Components: build system (Unix/Linux) >Affects Versions: 1.3.0 > Environment: Red Hat Enterprise Linux 4 with pkgconfig-0.15 RPM > installed >Reporter: Stefano Pettini >Assignee: Sanjaya Ratnaweera > > I cannot compile Axis2/C on RHEL4 because: > checking for LIBXML2... configure: error: The pkg-config script could not be > found or is too old. Make sure it > is in your PATH or set the PKG_CONFIG environment variable to the full > path to pkg-config. > I don't see the need of version 0.20 or higher, since the installed version, > 0.15, is able to retrieve LIBS and CFLAGS of libxml-2.0 without any problem. > By the way: > Alternatively, you may set the environment variables LIBXML2_CFLAGS > and LIBXML2_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > This doesn't work too, since I manually set those variables, here they are, > just copied from "set" output: > LIBXML2_CFLAGS=-I/usr/include/libxml2 > LIBXML2_LIBS='-lxml2 -lpthread -lz -lm' > But configure still try to use the pkg-config utility it doesn't like. > Upgrading the RPM is not an option, this would require an upgraded C library > too. > I solved modifying the configure script of axiom, lowering the required > pkg-config version from 0.20 to 0.15 and works perfectly. I think this fix > should be included in next releases. > Thank you! > Stefano -- 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-962) property_test segfaults
[ https://issues.apache.org/jira/browse/AXIS2C-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-962. Resolution: Fixed Fix Version/s: 1.3.0 Committed revision 618015. > property_test segfaults > --- > > Key: AXIS2C-962 > URL: https://issues.apache.org/jira/browse/AXIS2C-962 > Project: Axis2-C > Issue Type: Sub-task > Components: tests > Environment: Linux (Debian/Sid) >Reporter: Dinesh Premalal >Assignee: Dinesh Premalal > Fix For: 1.3.0 > > > When input.doc and output.doc unavailable property_test 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]
[jira] Updated: (AXIS2C-962) property_test segfaults
[ https://issues.apache.org/jira/browse/AXIS2C-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal updated AXIS2C-962: --- Summary: property_test segfaults (was: property_check segfaults) > property_test segfaults > --- > > Key: AXIS2C-962 > URL: https://issues.apache.org/jira/browse/AXIS2C-962 > Project: Axis2-C > Issue Type: Sub-task > Components: tests > Environment: Linux (Debian/Sid) >Reporter: Dinesh Premalal >Assignee: Dinesh Premalal > > When input.doc and output.doc unavailable property_test 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]
[jira] Created: (AXIS2C-962) property_check segfaults
property_check segfaults Key: AXIS2C-962 URL: https://issues.apache.org/jira/browse/AXIS2C-962 Project: Axis2-C Issue Type: Sub-task Components: tests Environment: Linux (Debian/Sid) Reporter: Dinesh Premalal Assignee: Dinesh Premalal When input.doc and output.doc unavailable property_test 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]
[jira] Resolved: (AXIS2C-960) make check failed on axis2c 1.3.0 release pack
[
https://issues.apache.org/jira/browse/AXIS2C-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Premalal resolved AXIS2C-960.
Resolution: Fixed
Assignee: Dinesh Premalal
Committed revision 618007
> make check failed on axis2c 1.3.0 release pack
> --
>
> Key: AXIS2C-960
> URL: https://issues.apache.org/jira/browse/AXIS2C-960
> Project: Axis2-C
> Issue Type: Bug
> Components: build system, tests
>Affects Versions: Current (Nightly)
>Reporter: Dinesh Premalal
>Assignee: Dinesh Premalal
> Fix For: 1.3.0
>
>
> I tried "make check" on axis2c-src-1.3.0 source pack. It gives me a
> segmentation fault.
> make[4]: Entering directory
> `/home/dinesh/axis2c-src-1.3.0/util/test/allocator'
> /bin/sh: line 4: 11392 Segmentation fault ${dir}$tst
> FAIL: allocator_test
> ===
> 1 of 1 tests failed
> ===
> make[4]: *** [check-TESTS] Error 1
> make[4]: Leaving directory `/home/dinesh/axis2c-src-1.3.0/util/test/allocator'
> make[3]: *** [check-am] Error 2
> make[3]: Leaving directory `/home/dinesh/axis2c-src-1.3.0/util/test/allocator'
> make[2]: *** [check-recursive] Error 1
> make[2]: Leaving directory `/home/dinesh/axis2c-src-1.3.0/util/test'
> make[1]: *** [check-recursive] Error 1
> make[1]: Leaving directory `/home/dinesh/axis2c-src-1.3.0/util'
> make: *** [check-recursive] Error 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]
[jira] Resolved: (AXIS2C-961) util/src/base64_binary.c NULL checking miss
[ https://issues.apache.org/jira/browse/AXIS2C-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-961. Resolution: Fixed Committed revision 618007 > util/src/base64_binary.c NULL checking miss > --- > > Key: AXIS2C-961 > URL: https://issues.apache.org/jira/browse/AXIS2C-961 > Project: Axis2-C > Issue Type: Sub-task >Affects Versions: Current (Nightly) > Environment: Debian (Linux/Sid) >Reporter: Dinesh Premalal >Assignee: Dinesh Premalal > Fix For: 1.3.0 > > > while digg into axis2c- 960 "make check failed" issue, I came across that > there are some null checking missing in some functions of > util/src/base64_binary.c -- 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] Created: (AXIS2C-961) util/src/base64_binary.c NULL checking miss
util/src/base64_binary.c NULL checking miss --- Key: AXIS2C-961 URL: https://issues.apache.org/jira/browse/AXIS2C-961 Project: Axis2-C Issue Type: Sub-task Affects Versions: Current (Nightly) Environment: Debian (Linux/Sid) Reporter: Dinesh Premalal Assignee: Dinesh Premalal Fix For: 1.3.0 while digg into axis2c- 960 "make check failed" issue, I came across that there are some null checking missing in some functions of util/src/base64_binary.c -- 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] Commented: (AXIS2C-960) make check failed on axis2c 1.3.0 release pack
[
https://issues.apache.org/jira/browse/AXIS2C-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565182#action_12565182
]
Dinesh Premalal commented on AXIS2C-960:
This segmentation faults happen because of the unavailability of simple null
checking :( My understanding is code quality of newly added tests need to be
improved. If you observe those tests closely you can see that excessive use of
global variables and so on. Therefore I would like to suggest to remove those
tests from Axis2/C 1.3.0 release. I think , It is better to ship them after we
improving them.
Please share your thoughts on this?
> make check failed on axis2c 1.3.0 release pack
> --
>
> Key: AXIS2C-960
> URL: https://issues.apache.org/jira/browse/AXIS2C-960
> Project: Axis2-C
> Issue Type: Bug
> Components: build system, tests
>Affects Versions: Current (Nightly)
>Reporter: Dinesh Premalal
> Fix For: 1.3.0
>
>
> I tried "make check" on axis2c-src-1.3.0 source pack. It gives me a
> segmentation fault.
> make[4]: Entering directory
> `/home/dinesh/axis2c-src-1.3.0/util/test/allocator'
> /bin/sh: line 4: 11392 Segmentation fault ${dir}$tst
> FAIL: allocator_test
> ===
> 1 of 1 tests failed
> ===
> make[4]: *** [check-TESTS] Error 1
> make[4]: Leaving directory `/home/dinesh/axis2c-src-1.3.0/util/test/allocator'
> make[3]: *** [check-am] Error 2
> make[3]: Leaving directory `/home/dinesh/axis2c-src-1.3.0/util/test/allocator'
> make[2]: *** [check-recursive] Error 1
> make[2]: Leaving directory `/home/dinesh/axis2c-src-1.3.0/util/test'
> make[1]: *** [check-recursive] Error 1
> make[1]: Leaving directory `/home/dinesh/axis2c-src-1.3.0/util'
> make: *** [check-recursive] Error 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]
[jira] Created: (AXIS2C-960) make check failed on axis2c 1.3.0 release pack
make check failed on axis2c 1.3.0 release pack
--
Key: AXIS2C-960
URL: https://issues.apache.org/jira/browse/AXIS2C-960
Project: Axis2-C
Issue Type: Bug
Components: build system, tests
Affects Versions: Current (Nightly)
Reporter: Dinesh Premalal
Fix For: 1.3.0
I tried "make check" on axis2c-src-1.3.0 source pack. It gives me a
segmentation fault.
make[4]: Entering directory `/home/dinesh/axis2c-src-1.3.0/util/test/allocator'
/bin/sh: line 4: 11392 Segmentation fault ${dir}$tst
FAIL: allocator_test
===
1 of 1 tests failed
===
make[4]: *** [check-TESTS] Error 1
make[4]: Leaving directory `/home/dinesh/axis2c-src-1.3.0/util/test/allocator'
make[3]: *** [check-am] Error 2
make[3]: Leaving directory `/home/dinesh/axis2c-src-1.3.0/util/test/allocator'
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory `/home/dinesh/axis2c-src-1.3.0/util/test'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/home/dinesh/axis2c-src-1.3.0/util'
make: *** [check-recursive] Error 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]
[jira] Created: (AXIS2C-958) axis2c-src-1.3.0 pack build failed.
axis2c-src-1.3.0 pack build failed. --- Key: AXIS2C-958 URL: https://issues.apache.org/jira/browse/AXIS2C-958 Project: Axis2-C Issue Type: Bug Components: build system Affects Versions: Current (Nightly) Environment: Linux (Debian/Sid) Reporter: Dinesh Premalal Assignee: Dinesh Premalal Fix For: 1.3.0 axis2c-src-1.3.0 release pack build failed saying create_env.h failed. -- 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-958) axis2c-src-1.3.0 pack build failed.
[ https://issues.apache.org/jira/browse/AXIS2C-958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-958. Resolution: Fixed Committed revision 617992 > axis2c-src-1.3.0 pack build failed. > --- > > Key: AXIS2C-958 > URL: https://issues.apache.org/jira/browse/AXIS2C-958 > Project: Axis2-C > Issue Type: Bug > Components: build system >Affects Versions: Current (Nightly) > Environment: Linux (Debian/Sid) >Reporter: Dinesh Premalal >Assignee: Dinesh Premalal > Fix For: 1.3.0 > > > axis2c-src-1.3.0 release pack build failed saying create_env.h failed. -- 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-957) Build Break with --enable-libcurl=yes option
[ https://issues.apache.org/jira/browse/AXIS2C-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-957. Resolution: Fixed Committed revision 617985 > Build Break with --enable-libcurl=yes option > > > Key: AXIS2C-957 > URL: https://issues.apache.org/jira/browse/AXIS2C-957 > Project: Axis2-C > Issue Type: Bug > Components: build system (Unix/Linux), core/transport >Affects Versions: Current (Nightly) > Environment: Linux (Debian/Sid) >Reporter: Dinesh Premalal >Assignee: Dinesh Premalal > Fix For: 1.3.0 > > > There was a build break when I tried to build with --enable-libcurl=yes , I > got following error. > In file included from http_transport_sender.c:35: > libcurl/axis2_libcurl.h:14: error: redefinition of typedef 'axis2_libcurl_t' > ../../../../../include/axis2_http_sender.h:79: error: previous declaration of > 'axis2_libcurl_t' was here > make[7]: *** [http_transport_sender.lo] Error 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]
[jira] Created: (AXIS2C-957) Build Break with --enable-libcurl=yes option
Build Break with --enable-libcurl=yes option Key: AXIS2C-957 URL: https://issues.apache.org/jira/browse/AXIS2C-957 Project: Axis2-C Issue Type: Bug Components: build system (Unix/Linux), core/transport Affects Versions: Current (Nightly) Environment: Linux (Debian/Sid) Reporter: Dinesh Premalal Assignee: Dinesh Premalal Fix For: 1.3.0 There was a build break when I tried to build with --enable-libcurl=yes , I got following error. In file included from http_transport_sender.c:35: libcurl/axis2_libcurl.h:14: error: redefinition of typedef 'axis2_libcurl_t' ../../../../../include/axis2_http_sender.h:79: error: previous declaration of 'axis2_libcurl_t' was here make[7]: *** [http_transport_sender.lo] Error 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]
[jira] Assigned: (AXIS2C-948) axutil_base64_binary_set_plain_binary crashes
[ https://issues.apache.org/jira/browse/AXIS2C-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal reassigned AXIS2C-948: -- Assignee: Dinesh Premalal > axutil_base64_binary_set_plain_binary crashes > - > > Key: AXIS2C-948 > URL: https://issues.apache.org/jira/browse/AXIS2C-948 > Project: Axis2-C > Issue Type: Bug > Components: util >Affects Versions: Current (Nightly) > Environment: Windows XP >Reporter: Dave Meier >Assignee: Dinesh Premalal >Priority: Critical > Fix For: 1.2.1 > > Attachments: base64_binary_c_diff.txt > > > axutil_base64_binary_set_plain_binary is written incorrectly where it does > the memcpy as it uses an unitialized length variable. I am attaching the > diff of the fix. -- 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-948) axutil_base64_binary_set_plain_binary crashes
[ https://issues.apache.org/jira/browse/AXIS2C-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-948. Resolution: Fixed Fix Version/s: 1.2.1 patch applied ! Thanks Dave for the patch. > axutil_base64_binary_set_plain_binary crashes > - > > Key: AXIS2C-948 > URL: https://issues.apache.org/jira/browse/AXIS2C-948 > Project: Axis2-C > Issue Type: Bug > Components: util >Affects Versions: Current (Nightly) > Environment: Windows XP >Reporter: Dave Meier >Assignee: Dinesh Premalal >Priority: Critical > Fix For: 1.2.1 > > Attachments: base64_binary_c_diff.txt > > > axutil_base64_binary_set_plain_binary is written incorrectly where it does > the memcpy as it uses an unitialized length variable. I am attaching the > diff of the fix. -- 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-951) build erros in axis2c/util/test
[ https://issues.apache.org/jira/browse/AXIS2C-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-951. Resolution: Fixed Fix Version/s: 1.2.1 patch applied. Thanks Manoj. > build erros in axis2c/util/test > --- > > Key: AXIS2C-951 > URL: https://issues.apache.org/jira/browse/AXIS2C-951 > Project: Axis2-C > Issue Type: Bug > Components: build system (Unix/Linux) >Reporter: Manoj Pushpakumara >Assignee: Dinesh Premalal >Priority: Minor > Fix For: 1.2.1 > > Attachments: corrections.diff > > > There were some build erros in axis2c/util/test. I fixed those bugs and > attached a patch. please review and attached it. -- 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-951) build erros in axis2c/util/test
[ https://issues.apache.org/jira/browse/AXIS2C-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal reassigned AXIS2C-951: -- Assignee: Dinesh Premalal > build erros in axis2c/util/test > --- > > Key: AXIS2C-951 > URL: https://issues.apache.org/jira/browse/AXIS2C-951 > Project: Axis2-C > Issue Type: Bug > Components: build system (Unix/Linux) >Reporter: Manoj Pushpakumara >Assignee: Dinesh Premalal >Priority: Minor > Fix For: 1.2.1 > > Attachments: corrections.diff > > > There were some build erros in axis2c/util/test. I fixed those bugs and > attached a patch. please review and attached it. -- 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-945) unit test program to test om_util.c
[ https://issues.apache.org/jira/browse/AXIS2C-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-945. Resolution: Fixed Fix Version/s: 1.2.1 patch applied ! Thanks Manoj. > unit test program to test om_util.c > --- > > Key: AXIS2C-945 > URL: https://issues.apache.org/jira/browse/AXIS2C-945 > Project: Axis2-C > Issue Type: Improvement > Components: tests >Reporter: Manoj Pushpakumara >Assignee: Dinesh Premalal >Priority: Minor > Fix For: 1.2.1 > > Attachments: axiom_util.diff > > > I wrote a unit test program to test om_util.c and attached it. please review > and apply this patch to axis2c/util/test location. -- 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-945) unit test program to test om_util.c
[ https://issues.apache.org/jira/browse/AXIS2C-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal reassigned AXIS2C-945: -- Assignee: Dinesh Premalal > unit test program to test om_util.c > --- > > Key: AXIS2C-945 > URL: https://issues.apache.org/jira/browse/AXIS2C-945 > Project: Axis2-C > Issue Type: Improvement > Components: tests >Reporter: Manoj Pushpakumara >Assignee: Dinesh Premalal >Priority: Minor > Fix For: 1.2.1 > > Attachments: axiom_util.diff > > > I wrote a unit test program to test om_util.c and attached it. please review > and apply this patch to axis2c/util/test location. -- 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-857) guththila parser drops xml:id attributes from incoming elements
[ https://issues.apache.org/jira/browse/AXIS2C-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-857. Resolution: Fixed Lahiru, Applied new patch ! Thanks. > guththila parser drops xml:id attributes from incoming elements > --- > > Key: AXIS2C-857 > URL: https://issues.apache.org/jira/browse/AXIS2C-857 > Project: Axis2-C > Issue Type: Bug > Components: guththila >Affects Versions: Current (Nightly) > Environment: Windows XP, Visual Studio 2005, guththila parser, libcurl >Reporter: Bill Mitchell >Assignee: Dinesh Premalal >Priority: Minor > Fix For: 1.2.1 > > Attachments: diff.txt, diff2.txt, diff_mod.txt > > > The XML specification allows an element to carry an xml:id attribute without > the xml namespace being declared explicitly. In fact, if the xml namespace > is declared, it must match http://www.w3.org/XML/1998/namespace. When the > namespace is not declared explicitly, it appears that the guththila parser > discards the incoming xml:id attributes without including them in the om. > For example, I receive a response message from a service that begins: > http://www.w3.org/2001/XMLSchema"; > xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:fw="http://frameware.xcentrisity.com/services/";> > > name="customer" supportedMethods="browse browseNext browsePrevious create > update delete retrieve"> > > > > > ... > When linked with libxml, the client code sees two attributes, a type > attribute and an xml:id attribute, attached to the element nodes. When > linked with the guththila parser, only the type attribute is present. -- 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-857) guththila parser drops xml:id attributes from incoming elements
[ https://issues.apache.org/jira/browse/AXIS2C-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-857. Resolution: Fixed Fix Version/s: 1.2.1 Assignee: Dinesh Premalal Patch applied ! Thanks Bill and Lahiru for the input. > guththila parser drops xml:id attributes from incoming elements > --- > > Key: AXIS2C-857 > URL: https://issues.apache.org/jira/browse/AXIS2C-857 > Project: Axis2-C > Issue Type: Bug > Components: guththila >Affects Versions: Current (Nightly) > Environment: Windows XP, Visual Studio 2005, guththila parser, libcurl >Reporter: Bill Mitchell >Assignee: Dinesh Premalal >Priority: Minor > Fix For: 1.2.1 > > Attachments: diff.txt, diff2.txt > > > The XML specification allows an element to carry an xml:id attribute without > the xml namespace being declared explicitly. In fact, if the xml namespace > is declared, it must match http://www.w3.org/XML/1998/namespace. When the > namespace is not declared explicitly, it appears that the guththila parser > discards the incoming xml:id attributes without including them in the om. > For example, I receive a response message from a service that begins: > http://www.w3.org/2001/XMLSchema"; > xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:fw="http://frameware.xcentrisity.com/services/";> > > name="customer" supportedMethods="browse browseNext browsePrevious create > update delete retrieve"> > > > > > ... > When linked with libxml, the client code sees two attributes, a type > attribute and an xml:id attribute, attached to the element nodes. When > linked with the guththila parser, only the type attribute is present. -- 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-845) samples configure command should be corrected.
[
https://issues.apache.org/jira/browse/AXIS2C-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Premalal resolved AXIS2C-845.
Resolution: Fixed
Fix Version/s: 1.2.1
Senaka has fixed this issue.
> samples configure command should be corrected.
> --
>
> Key: AXIS2C-845
> URL: https://issues.apache.org/jira/browse/AXIS2C-845
> Project: Axis2-C
> Issue Type: Bug
> Components: build system (Unix/Linux)
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Krishantha Samaraweera
>Assignee: Dinesh Premalal
>Priority: Minor
> Fix For: 1.2.1
>
> Attachments: diff.txt
>
>
> samples configure command specified in installation guide has a typing
> mistake, one curly bracket is missing.
> existing command:
> ./configure --prefix=${AXIS2C_HOME}
> --with-axis2=$AXIS2C_HOME}/include/axis2-1.2
> this should be changed as
> ./configure --prefix=${AXIS2C_HOME}
> --with-axis2=${AXIS2C_HOME}/include/axis2-1.2
--
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-845) samples configure command should be corrected.
[
https://issues.apache.org/jira/browse/AXIS2C-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Premalal reassigned AXIS2C-845:
--
Assignee: Dinesh Premalal
> samples configure command should be corrected.
> --
>
> Key: AXIS2C-845
> URL: https://issues.apache.org/jira/browse/AXIS2C-845
> Project: Axis2-C
> Issue Type: Bug
> Components: build system (Unix/Linux)
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Krishantha Samaraweera
>Assignee: Dinesh Premalal
>Priority: Minor
> Attachments: diff.txt
>
>
> samples configure command specified in installation guide has a typing
> mistake, one curly bracket is missing.
> existing command:
> ./configure --prefix=${AXIS2C_HOME}
> --with-axis2=$AXIS2C_HOME}/include/axis2-1.2
> this should be changed as
> ./configure --prefix=${AXIS2C_HOME}
> --with-axis2=${AXIS2C_HOME}/include/axis2-1.2
--
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] Commented: (AXIS2C-861) Enable client session management through http cookies in libcurl
[ https://issues.apache.org/jira/browse/AXIS2C-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563909#action_12563909 ] Dinesh Premalal commented on AXIS2C-861: Hi Bill, I tried to commit this patch, but I couldn't. I think some line numbers are changed. If you could find some time please commit it. > Enable client session management through http cookies in libcurl > > > Key: AXIS2C-861 > URL: https://issues.apache.org/jira/browse/AXIS2C-861 > Project: Axis2-C > Issue Type: Improvement > Components: transport/http >Affects Versions: Current (Nightly) > Environment: Windows XP, Visual Studio 2005, libxml, libcurl >Reporter: Bill Mitchell > Attachments: libcurl_diff > > > Many existing SOAP services maintain session context through HTTP cookies. > This can be seen in the prevalence of some mechanism to enable client cookies > in various SOAP stacks, including the Axis versions in Java and C++. Without > re-implementing all of this in the Axis2C http transport, it would be easy > and convenient to provide this support for Axis2C clients built with libcurl. > Libcurl already provides the underlying cookie support, all that is needed > is some mechanism to enable/disable this support with, say, the defined but > unused maintain_session option. -- 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] Commented: (AXIS2C-933) guththila parser does not handle incomplete messages well, leading to an infinite loop or seg fault
[ https://issues.apache.org/jira/browse/AXIS2C-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563906#action_12563906 ] Dinesh Premalal commented on AXIS2C-933: Ok, That would be fine. > guththila parser does not handle incomplete messages well, leading to an > infinite loop or seg fault > --- > > Key: AXIS2C-933 > URL: https://issues.apache.org/jira/browse/AXIS2C-933 > Project: Axis2-C > Issue Type: Bug > Components: guththila >Affects Versions: Current (Nightly) > Environment: Windows XP, Visual Studio 2005, guththila, libcurl >Reporter: Bill Mitchell > Attachments: diff.txt, diff2.txt > > > The code in the guththila parser has a couple of problems when the first > allocated buffer fills up and it attempts to read more data. First, when > allocating another buffer it doubled the size of all the buffers allocated to > this point, but then recorded the new buffer size as only equal to the size > of all the previous buffers. Second, after fixing the buffer allocation > issue, I discovered that the read into the buffer tried to read as much as > all the buffers to date, instead of just the amount remaining in the buffer > just allocated. There is also a subtle problem in the guththila_next_no_char > routine if last_start is not set, that it did not assure that all the > characters since next are moved to the newly allocated buffer. > While debugging this, because of other issues, I walked through the path of > an unexpected EOF in the middle of the incoming message, and discovered that > several while loops in the parser do not stop on EOF, but just keep reading > and reading and reading... -- 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] Commented: (AXIS2C-926) unit test program to test linked_list.c
[ https://issues.apache.org/jira/browse/AXIS2C-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563895#action_12563895 ] Dinesh Premalal commented on AXIS2C-926: Manoj, Could you provide a patch relevant to these changes please. It makes our life easier. > unit test program to test linked_list.c > --- > > Key: AXIS2C-926 > URL: https://issues.apache.org/jira/browse/AXIS2C-926 > Project: Axis2-C > Issue Type: Improvement > Components: tests >Reporter: Manoj Pushpakumara >Priority: Minor > Attachments: build.sh, link_list_test.c > > > I wrote a unit test program to test linked_list.c. Please review it and apply > the patch to axis2c/util/test location. To apply the patch you have to create > a folder call linked_list and put test_linked_list.c and build.sh file to > that. -- 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-925) seg fault in axiom_soap_fault_get_text if SOAP 1.1
[ https://issues.apache.org/jira/browse/AXIS2C-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-925. Resolution: Fixed Fix Version/s: 1.2.1 Assignee: Dinesh Premalal patch applied ! Thanks Bill . > seg fault in axiom_soap_fault_get_text if SOAP 1.1 > -- > > Key: AXIS2C-925 > URL: https://issues.apache.org/jira/browse/AXIS2C-925 > Project: Axis2-C > Issue Type: Bug > Components: xml/soap >Affects Versions: Current (Nightly) > Environment: Windows XP, Visual Studio 2005, libxml2, libcurl >Reporter: Bill Mitchell >Assignee: Dinesh Premalal > Fix For: 1.2.1 > > Attachments: soapfault.diff > > > If a SOAP 1.1 server returns a SOAP fault, a seg fault can happen if the > client calls axiom_soap_fault_get_text. At the time of the crash, using the > debugger the om_ele_node in the fault_value points to memory that has been > reused, probably as a result of being released. When axiom_element_get_text > is called, the data_element it is passed appears to be overwritten or reused, > so axiom_element_get_text sees om_element->text_value as nonzero, tries to > free it, and the C runtime diagnoses a memory management error on the free. > Stepping through with the debugger, the crux of the problem lies in > soap_body.c, where axiom_soap_body_convert_fault_to_soap11 detaches the > fault_value_node, converts its contents to text, issues the free_tree to free > the node and its children, but leaves the pointer as the > axiom_soap_fault_value_base_node. So the later call to > axiom_soap_fault_get_text believes there is still a node tree structure > present. The same oversight occurs when processing the fault_reason. The > axiom_soap_fault_text_base_node is detached, converted to a single text > string, the node tree is freed, but the pointer is left as the > axiom_soap_fault_base_node. -- 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-927) axiom_element_declare_default_namespace fails when no namespace already declared
[
https://issues.apache.org/jira/browse/AXIS2C-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Premalal resolved AXIS2C-927.
Resolution: Fixed
Fix Version/s: 1.2.1
Assignee: Dinesh Premalal
patch applied ! Thanks Bill for the patch.
> axiom_element_declare_default_namespace fails when no namespace already
> declared
>
>
> Key: AXIS2C-927
> URL: https://issues.apache.org/jira/browse/AXIS2C-927
> Project: Axis2-C
> Issue Type: Bug
> Environment: Windows XP, Visual Studio 2005, guththila, libcurl
>Reporter: Bill Mitchell
>Assignee: Dinesh Premalal
> Fix For: 1.2.1
>
> Attachments: om_element_diff
>
>
> If axiom_element_declare_default_namespace() is called before any named
> namespace is declared, it fails to perform the axutil_hash_make and as a
> result axutil_hash_set crashes on the empty namespace pointer.
> The code fragment:
> if (om_element->namespaces)
> {
> om_element->namespaces = axutil_hash_make(env);
> if (!(om_element->namespaces))
> {
> return NULL;
> }
> }
> should read:
> if (!om_element->namespaces)
> {
> om_element->namespaces = axutil_hash_make(env);
> if (!(om_element->namespaces))
> {
> return NULL;
> }
> }
--
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-932) IIS module fails with service that has the name "services" in it
[
https://issues.apache.org/jira/browse/AXIS2C-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Premalal resolved AXIS2C-932.
Resolution: Fixed
Fix Version/s: 1.2.1
Assignee: Dinesh Premalal
patch applied ! Thanks Dave for the patch.
> IIS module fails with service that has the name "services" in it
>
>
> Key: AXIS2C-932
> URL: https://issues.apache.org/jira/browse/AXIS2C-932
> Project: Axis2-C
> Issue Type: Bug
> Components: transport/http
>Affects Versions: Current (Nightly)
> Environment: Windows XP.
>Reporter: Dave Meier
>Assignee: Dinesh Premalal
>Priority: Critical
> Fix For: 1.2.1
>
> Attachments: utils_c_diff.txt
>
>
> When I use the IIS module and try to call my service it fails to find the
> service. The name of my service is "aewebservices70", so the URL is
> "http://localhost:80/axis2/services/aewebservices70";. The service is not
> found.
> I found that there is a loop in axutil_parse_request_url_for_svc_and_op(...)
> where it keeps looking for "services" so it end up returning "70" as the
> service name.
> I modified the code to break out of the loop after the first "services" is
> found and that fixed it. I'm not sure if the loop is there for a reason:
> while (1)
> {
> tmp = strstr(tmp, axis2_request_url_prefix);
> if (!tmp)
> {
> break;
> }
> else
> {
> service_str = tmp;
> tmp += axutil_strlen(axis2_request_url_prefix);
> break;// I added this line to get it to work...
> }
> }
--
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] Commented: (AXIS2C-933) guththila parser does not handle incomplete messages well, leading to an infinite loop or seg fault
[ https://issues.apache.org/jira/browse/AXIS2C-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563862#action_12563862 ] Dinesh Premalal commented on AXIS2C-933: Hi Devs, Is this patches are complete? Can I commit them into svn ? > guththila parser does not handle incomplete messages well, leading to an > infinite loop or seg fault > --- > > Key: AXIS2C-933 > URL: https://issues.apache.org/jira/browse/AXIS2C-933 > Project: Axis2-C > Issue Type: Bug > Components: guththila >Affects Versions: Current (Nightly) > Environment: Windows XP, Visual Studio 2005, guththila, libcurl >Reporter: Bill Mitchell > Attachments: diff.txt, diff2.txt > > > The code in the guththila parser has a couple of problems when the first > allocated buffer fills up and it attempts to read more data. First, when > allocating another buffer it doubled the size of all the buffers allocated to > this point, but then recorded the new buffer size as only equal to the size > of all the previous buffers. Second, after fixing the buffer allocation > issue, I discovered that the read into the buffer tried to read as much as > all the buffers to date, instead of just the amount remaining in the buffer > just allocated. There is also a subtle problem in the guththila_next_no_char > routine if last_start is not set, that it did not assure that all the > characters since next are moved to the newly allocated buffer. > While debugging this, because of other issues, I walked through the path of > an unexpected EOF in the middle of the incoming message, and discovered that > several while loops in the parser do not stop on EOF, but just keep reading > and reading and reading... -- 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] Commented: (AXIS2C-916) C++ style comments found in code.
[ https://issues.apache.org/jira/browse/AXIS2C-916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563857#action_12563857 ] Dinesh Premalal commented on AXIS2C-916: I tried on Linux, but I couldn't apply it too. > C++ style comments found in code. > - > > Key: AXIS2C-916 > URL: https://issues.apache.org/jira/browse/AXIS2C-916 > Project: Axis2-C > Issue Type: Bug >Affects Versions: Current (Nightly) >Reporter: Senaka Fernando >Priority: Minor > Attachments: diff.txt > > > C++ style comments found in code. Inspired by AXIS2C-911, I decided to remove > all such occurrences. Refer diff.txt. However, some of the patched files > contains ^M characters and trying to remove them either using dos2unix or > manually makes the diff invalid. Due to this reason I have left them the way > they were. > Regards, > Senaka -- 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-866) REOPEN - /util/src/base64.c incorrect calculation of length in 'axutil_base64_decode_len'
[
https://issues.apache.org/jira/browse/AXIS2C-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Premalal resolved AXIS2C-866.
Resolution: Fixed
Fix Version/s: 1.2.1
Issue is fixed by Shankar.
> REOPEN - /util/src/base64.c incorrect calculation of length in
> 'axutil_base64_decode_len'
> -
>
> Key: AXIS2C-866
> URL: https://issues.apache.org/jira/browse/AXIS2C-866
> Project: Axis2-C
> Issue Type: Bug
> Components: util
>Affects Versions: 1.2.0
>Reporter: Frank Huebbers
>Assignee: Dinesh Premalal
>Priority: Critical
> Fix For: 1.2.1
>
>
> Hi,
> First off, I am opening a new issue here because I don't seem to be able to
> reopen case AXIS2C-731 which does not yet seem to be fixed either for the
> release candidate 1.2.0 (Take 4) nor on head.
> Specifically, it appears as if the proposed bug fix in AXIS2C-731 did not
> make it 1-to-1 into CVS. To reiterate, the proposed bug fix was:
> AXIS2_EXTERN int AXIS2_CALL axutil_base64_decode_len(const char *bufcoded)
> {
> int nbytesdecoded;
> register const unsigned char *bufin;
> register int nprbytes;
> bufin = (const unsigned char *) bufcoded;
> while (pr2six[*(bufin++)] <= 63);
> nprbytes = (bufin - (const unsigned char *) bufcoded) - 1;
> nbytesdecoded = ((nprbytes >> 2) * 3);
> if (nprbytes & 0x03) nbytesdecoded += (nprbytes & 0x03) - 1;
> return nbytesdecoded;
> }
> What actually made it into 1.2.0 and head is the following:
> AXIS2_EXTERN int AXIS2_CALL axutil_base64_decode_len(const char *bufcoded)
> {
> int nbytesdecoded;
> register const unsigned char *bufin;
> register int nprbytes;
> bufin = (const unsigned char *) bufcoded;
> while (pr2six[*(bufin++)] <= 63);
> nprbytes = (bufin - (const unsigned char *) bufcoded) - 1;
> nbytesdecoded = ((nprbytes >> 2) * 3);
> if (nprbytes & 0x03) nbytesdecoded += (nprbytes & 0x03) - 1;
> return nbytesdecoded + 1;
> }
> => Note the "+1" on the return type.
> Frank
--
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-866) REOPEN - /util/src/base64.c incorrect calculation of length in 'axutil_base64_decode_len'
[
https://issues.apache.org/jira/browse/AXIS2C-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Premalal reassigned AXIS2C-866:
--
Assignee: Dinesh Premalal
> REOPEN - /util/src/base64.c incorrect calculation of length in
> 'axutil_base64_decode_len'
> -
>
> Key: AXIS2C-866
> URL: https://issues.apache.org/jira/browse/AXIS2C-866
> Project: Axis2-C
> Issue Type: Bug
> Components: util
>Affects Versions: 1.2.0
>Reporter: Frank Huebbers
>Assignee: Dinesh Premalal
>Priority: Critical
> Fix For: 1.2.1
>
>
> Hi,
> First off, I am opening a new issue here because I don't seem to be able to
> reopen case AXIS2C-731 which does not yet seem to be fixed either for the
> release candidate 1.2.0 (Take 4) nor on head.
> Specifically, it appears as if the proposed bug fix in AXIS2C-731 did not
> make it 1-to-1 into CVS. To reiterate, the proposed bug fix was:
> AXIS2_EXTERN int AXIS2_CALL axutil_base64_decode_len(const char *bufcoded)
> {
> int nbytesdecoded;
> register const unsigned char *bufin;
> register int nprbytes;
> bufin = (const unsigned char *) bufcoded;
> while (pr2six[*(bufin++)] <= 63);
> nprbytes = (bufin - (const unsigned char *) bufcoded) - 1;
> nbytesdecoded = ((nprbytes >> 2) * 3);
> if (nprbytes & 0x03) nbytesdecoded += (nprbytes & 0x03) - 1;
> return nbytesdecoded;
> }
> What actually made it into 1.2.0 and head is the following:
> AXIS2_EXTERN int AXIS2_CALL axutil_base64_decode_len(const char *bufcoded)
> {
> int nbytesdecoded;
> register const unsigned char *bufin;
> register int nprbytes;
> bufin = (const unsigned char *) bufcoded;
> while (pr2six[*(bufin++)] <= 63);
> nprbytes = (bufin - (const unsigned char *) bufcoded) - 1;
> nbytesdecoded = ((nprbytes >> 2) * 3);
> if (nprbytes & 0x03) nbytesdecoded += (nprbytes & 0x03) - 1;
> return nbytesdecoded + 1;
> }
> => Note the "+1" on the return type.
> Frank
--
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-880) Function axis2_svc_client_add_header[Alastair FETTES]
[ https://issues.apache.org/jira/browse/AXIS2C-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-880. Resolution: Fixed Fix Version/s: (was: Current (Nightly)) 1.2.1 patch applied. Thanks Senaka, Alastair and Lahiru for the input. > Function axis2_svc_client_add_header[Alastair FETTES] > - > > Key: AXIS2C-880 > URL: https://issues.apache.org/jira/browse/AXIS2C-880 > Project: Axis2-C > Issue Type: Bug > Components: core/clientapi >Affects Versions: Current (Nightly) > Environment: Ubuntu 7.04 >Reporter: Lahiru Gunathilake >Assignee: Dinesh Premalal > Fix For: 1.2.1 > > Attachments: diff.txt > > > > AXIS2_EXTERN > axis2_status_t axis2_svc_client_add_header( > axis2_svc_client_t* svc_client, > const axutil_env_t* env, > axiom_node_t* header) > > The parameter svc_client does not take responsibility for the memory > allocated for header, although it does maintain an internal pointer to the > data. This can result in dangling pointer situations if the caller deletes > the memory passed using header before svc_client has a chance to remove the > header. > Solution: Document memory ownership for parameters and return value. > Investigate the use of pointers in the internal structure to avoid dangling > pointer situations. -- 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-880) Function axis2_svc_client_add_header[Alastair FETTES]
[ https://issues.apache.org/jira/browse/AXIS2C-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal reassigned AXIS2C-880: -- Assignee: Dinesh Premalal > Function axis2_svc_client_add_header[Alastair FETTES] > - > > Key: AXIS2C-880 > URL: https://issues.apache.org/jira/browse/AXIS2C-880 > Project: Axis2-C > Issue Type: Bug > Components: core/clientapi >Affects Versions: Current (Nightly) > Environment: Ubuntu 7.04 >Reporter: Lahiru Gunathilake >Assignee: Dinesh Premalal > Fix For: Current (Nightly) > > Attachments: diff.txt > > > > AXIS2_EXTERN > axis2_status_t axis2_svc_client_add_header( > axis2_svc_client_t* svc_client, > const axutil_env_t* env, > axiom_node_t* header) > > The parameter svc_client does not take responsibility for the memory > allocated for header, although it does maintain an internal pointer to the > data. This can result in dangling pointer situations if the caller deletes > the memory passed using header before svc_client has a chance to remove the > header. > Solution: Document memory ownership for parameters and return value. > Investigate the use of pointers in the internal structure to avoid dangling > pointer situations. -- 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-774) echo_non_blocking.c sample's timeout value is too high
[ https://issues.apache.org/jira/browse/AXIS2C-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-774. Resolution: Fixed Fix Version/s: 1.2.1 Current (Nightly) Assignee: Dinesh Premalal (was: Sanjaya Ratnaweera) > echo_non_blocking.c sample's timeout value is too high > -- > > Key: AXIS2C-774 > URL: https://issues.apache.org/jira/browse/AXIS2C-774 > Project: Axis2-C > Issue Type: Bug > Components: samples > Environment: Ubuntu 7.10 (Gutsy Gibbon) >Reporter: Senaka Fernando >Assignee: Dinesh Premalal > Fix For: Current (Nightly), 1.2.1 > > Attachments: diff.txt > > > The echo_non_blocking.c sample's timeout value is too high. Please refer > proposed patch (diff.txt) -- 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] Commented: (AXIS2C-774) echo_non_blocking.c sample's timeout value is too high
[ https://issues.apache.org/jira/browse/AXIS2C-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563650#action_12563650 ] Dinesh Premalal commented on AXIS2C-774: There is a problem in the compiler options that we used. In samples we used "$CFLAGS -ansi -Wall -D_LARGEFILE64_SOURCE " where as to build the core we use CFLAGS as "CFLAGS="$CFLAGS -ansi -Wall -Wno-implicit-function-declaration" . At src/core/clientapi/svc_client.c we don't get above warning because we have used -Wno-implicit-function-declaration. Adding -Wno-implicit-function-declaration into samples/configure.ac will solve the problem. > echo_non_blocking.c sample's timeout value is too high > -- > > Key: AXIS2C-774 > URL: https://issues.apache.org/jira/browse/AXIS2C-774 > Project: Axis2-C > Issue Type: Bug > Components: samples > Environment: Ubuntu 7.10 (Gutsy Gibbon) >Reporter: Senaka Fernando >Assignee: Sanjaya Ratnaweera > Attachments: diff.txt > > > The echo_non_blocking.c sample's timeout value is too high. Please refer > proposed patch (diff.txt) -- 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] Reopened: (AXIS2C-774) echo_non_blocking.c sample's timeout value is too high
[ https://issues.apache.org/jira/browse/AXIS2C-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal reopened AXIS2C-774: Hi, I'm getting this warning for following compiler versions. gcc-4.2 (GCC) 4.2.3 20080114 (prerelease) (Debian 4.2.2-7) 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. gcc (GCC) 4.1.3 20080114 (prerelease) (Debian 4.1.2-19) Copyright (C) 2006 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. gcc (GCC) 4.0.4 20060904 (prerelease) (Debian 4.0.3-7) Copyright (C) 2006 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. cc1: warnings being treated as errors echo_non_blocking.c: In function 'main': echo_non_blocking.c:128: warning: implicit declaration of function 'usleep' make: *** [echo_non_blocking.o] Error 1 I think , It is not because something wrong in compiler but in our code. > echo_non_blocking.c sample's timeout value is too high > -- > > Key: AXIS2C-774 > URL: https://issues.apache.org/jira/browse/AXIS2C-774 > Project: Axis2-C > Issue Type: Bug > Components: samples > Environment: Ubuntu 7.10 (Gutsy Gibbon) >Reporter: Senaka Fernando >Assignee: Sanjaya Ratnaweera > Attachments: diff.txt > > > The echo_non_blocking.c sample's timeout value is too high. Please refer > proposed patch (diff.txt) -- 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] Commented: (AXIS2C-866) REOPEN - /util/src/base64.c incorrect calculation of length in 'axutil_base64_decode_len'
[
https://issues.apache.org/jira/browse/AXIS2C-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563594#action_12563594
]
Dinesh Premalal commented on AXIS2C-866:
Devs, Can we get this done for 1.2.1 release Or does it take some more time ?
> REOPEN - /util/src/base64.c incorrect calculation of length in
> 'axutil_base64_decode_len'
> -
>
> Key: AXIS2C-866
> URL: https://issues.apache.org/jira/browse/AXIS2C-866
> Project: Axis2-C
> Issue Type: Bug
> Components: util
>Affects Versions: 1.2.0
>Reporter: Frank Huebbers
>Priority: Critical
>
> Hi,
> First off, I am opening a new issue here because I don't seem to be able to
> reopen case AXIS2C-731 which does not yet seem to be fixed either for the
> release candidate 1.2.0 (Take 4) nor on head.
> Specifically, it appears as if the proposed bug fix in AXIS2C-731 did not
> make it 1-to-1 into CVS. To reiterate, the proposed bug fix was:
> AXIS2_EXTERN int AXIS2_CALL axutil_base64_decode_len(const char *bufcoded)
> {
> int nbytesdecoded;
> register const unsigned char *bufin;
> register int nprbytes;
> bufin = (const unsigned char *) bufcoded;
> while (pr2six[*(bufin++)] <= 63);
> nprbytes = (bufin - (const unsigned char *) bufcoded) - 1;
> nbytesdecoded = ((nprbytes >> 2) * 3);
> if (nprbytes & 0x03) nbytesdecoded += (nprbytes & 0x03) - 1;
> return nbytesdecoded;
> }
> What actually made it into 1.2.0 and head is the following:
> AXIS2_EXTERN int AXIS2_CALL axutil_base64_decode_len(const char *bufcoded)
> {
> int nbytesdecoded;
> register const unsigned char *bufin;
> register int nprbytes;
> bufin = (const unsigned char *) bufcoded;
> while (pr2six[*(bufin++)] <= 63);
> nprbytes = (bufin - (const unsigned char *) bufcoded) - 1;
> nbytesdecoded = ((nprbytes >> 2) * 3);
> if (nprbytes & 0x03) nbytesdecoded += (nprbytes & 0x03) - 1;
> return nbytesdecoded + 1;
> }
> => Note the "+1" on the return type.
> Frank
--
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] Updated: (AXIS2C-939) IIS Module does not set dll path and LoadLibrary call does not specify libraries current dir as start of search path
[
https://issues.apache.org/jira/browse/AXIS2C-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Premalal updated AXIS2C-939:
---
Priority: Major (was: Blocker)
> IIS Module does not set dll path and LoadLibrary call does not specify
> libraries current dir as start of search path
>
>
> Key: AXIS2C-939
> URL: https://issues.apache.org/jira/browse/AXIS2C-939
> Project: Axis2-C
> Issue Type: Bug
> Components: transport/http
>Affects Versions: Current (Nightly)
> Environment: Windows XP, IIS 5.1
>Reporter: Dave Meier
> Attachments: axis2_isapi_plugin_c_diff.txt, axutils_windows_c_diff.txt
>
>
> I have a services dll that depends on other dlls. When I use
> axis2_http_server.exe it works fine, but under the IIS module, my service dll
> fails to load with a "Failed in creating DLL" message.
> I modified the code and was able to get it to work and can provide a diff
> once I learn how to do that. The change involved setting the dll path in the
> IIS module code and modifying the LoadLibrary call that Axis2C uses to load
> the service dll. The second change involves telling LoadLibrary to search
> the same directory where the dll is located first when looking for other dlls
> that the service dll depends upon. This change avoids a problem where an
> incorrect dll is picked up from somewhere else in the search path (aka "dll
> hell").
> --
> Change 1 - file "axis2_isapi_plugin.c", method
> "HttpExtensionProc(LPEXTENSION_CONTROL_BLOCK lpECB)"
> --
> DWORD WINAPI HttpExtensionProc(LPEXTENSION_CONTROL_BLOCK lpECB)
> {
> DWORD rc = HSE_STATUS_ERROR;
> lpECB->dwHttpStatusCode = HTTP_INTERNAL_SERVER_ERROR;
> if (axis2_worker)
> {
> // windows cannot find the correct dlls unless the dir is set
> // but we want to reset to previous dir after the load
> char szOriginalPath[_MAX_PATH + 1];
> char szPath[_MAX_PATH + 1];
> DWORD dwBufferSize = 0;
> ZeroMemory(szOriginalPath, sizeof szOriginalPath);
> dwBufferSize = sizeof szOriginalPath;
> #if _WIN32_WINNT >= 0x0502 // we stop supporting old WIN OSs
> GetDllDirectory( dwBufferSize, szOriginalPath );
> #else
> GetCurrentDirectory( dwBufferSize, szOriginalPath );
> #endif // _WIN32_WINNT >= 0x050
> ZeroMemory(szPath, sizeof szPath);
> dwBufferSize = sizeof szPath;
> lpECB->GetServerVariable(lpECB->ConnID, "APPL_PHYSICAL_PATH", szPath,
> &dwBufferSize);
> if ( strlen( szPath ) > 0 )
> {
> // windows cannot find the correct dlls unless the path is set
> #if _WIN32_WINNT >= 0x0502 // we stop supporting old WIN OSs
> SetDllDirectory( szPath );
> #else
> SetCurrentDirectory( szPath );
> #endif // _WIN32_WINNT >= 0x050
> }
> AXIS2_IIS_WORKER_PROCESS_REQUEST(axis2_worker, axutil_env, lpECB);
> // windows cannot find the correct dlls unless the dir is set
> // but we want to reset to previous dir after the load
> #if _WIN32_WINNT >= 0x0502 // we stop supporting old WIN OSs
> SetDllDirectory( szOriginalPath );
> #else
> SetCurrentDirectory( szOriginalPath );
> #endif // _WIN32_WINNT >= 0x050
> }
> else
> return HSE_STATUS_ERROR;
> return HSE_STATUS_SUCCESS;
> }
> --
> Change 2 - file "axutil_windows.c", method "callLoadLib(char *lib)":
> --
> return LoadLibraryEx(lib, NULL, LOAD_WITH_ALTERED_SEARCH_PATH); // was
> "return LoadLibrary(lib);"
--
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] Commented: (AXIS2C-890) IssuedToken and SAMLToken assertion support for neethi
[ https://issues.apache.org/jira/browse/AXIS2C-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561405#action_12561405 ] Dinesh Premalal commented on AXIS2C-890: Milinda, I think you can commit your self these patches. Do we have any special reason to attach them here. Just wondering :) > IssuedToken and SAMLToken assertion support for neethi > -- > > Key: AXIS2C-890 > URL: https://issues.apache.org/jira/browse/AXIS2C-890 > Project: Axis2-C > Issue Type: Improvement >Affects Versions: Current (Nightly) >Reporter: Milinda Lakmal Pathirage > Fix For: Current (Nightly) > > Attachments: saml_iss_new.patch, saml_issued.patch > > > Neethi implementation doesn't support IssuedToken assertion and SAMLToken > assertion currently. But to implement SAML Token support for Rampart/C and > automate some parts in Trust implementation we need those two assertions to > be supported by neethi implementation. -- 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-606) Need to write an installation guide and a user manual for Savan/C web site
[ https://issues.apache.org/jira/browse/AXIS2C-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-606. Resolution: Fixed Fix Version/s: Current (Nightly) This document has committed to Savan/C trunk. Thanks Buddhika for the input. > Need to write an installation guide and a user manual for Savan/C web site > -- > > Key: AXIS2C-606 > URL: https://issues.apache.org/jira/browse/AXIS2C-606 > Project: Axis2-C > Issue Type: Improvement > Components: documentation >Affects Versions: Current (Nightly) >Reporter: Malinda Kaushalye Kapuruge >Assignee: Dinesh Premalal > Fix For: Current (Nightly) > > Attachments: installationguide.html > > > We need to write an installation guide and a user manual for Savan/C web > site. -- 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-331) SwA support
[ https://issues.apache.org/jira/browse/AXIS2C-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-331. Resolution: Won't Fix Fix Version/s: Current (Nightly) Martin, Thanks for the quick reply. I'm resolving this issue. If somebody thinks it is need to be in our open jira list please feel free to reopen. > SwA support > --- > > Key: AXIS2C-331 > URL: https://issues.apache.org/jira/browse/AXIS2C-331 > Project: Axis2-C > Issue Type: New Feature >Reporter: Martin Voelkle >Assignee: Dinesh Premalal > Fix For: Current (Nightly) > > > Axis2/c doesn't support SwA. It would be usefull to implement it. > If I'm not mistaken, the only open source C/C++ SOAP toolkit that supports it > is gSOAP. -- 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-606) Need to write an installation guide and a user manual for Savan/C web site
[ https://issues.apache.org/jira/browse/AXIS2C-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal reassigned AXIS2C-606: -- Assignee: Dinesh Premalal > Need to write an installation guide and a user manual for Savan/C web site > -- > > Key: AXIS2C-606 > URL: https://issues.apache.org/jira/browse/AXIS2C-606 > Project: Axis2-C > Issue Type: Improvement > Components: documentation >Affects Versions: Current (Nightly) >Reporter: Malinda Kaushalye Kapuruge >Assignee: Dinesh Premalal > Attachments: installationguide.html > > > We need to write an installation guide and a user manual for Savan/C web > site. -- 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-331) SwA support
[ https://issues.apache.org/jira/browse/AXIS2C-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal reassigned AXIS2C-331: -- Assignee: Dinesh Premalal > SwA support > --- > > Key: AXIS2C-331 > URL: https://issues.apache.org/jira/browse/AXIS2C-331 > Project: Axis2-C > Issue Type: New Feature >Reporter: Martin Voelkle >Assignee: Dinesh Premalal > > Axis2/c doesn't support SwA. It would be usefull to implement it. > If I'm not mistaken, the only open source C/C++ SOAP toolkit that supports it > is gSOAP. -- 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] Commented: (AXIS2C-331) SwA support
[ https://issues.apache.org/jira/browse/AXIS2C-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561084#action_12561084 ] Dinesh Premalal commented on AXIS2C-331: I think since we have MTOM implementation, this not going to happen in near future. However if somebody needs it badly always welcome to implement it. Thoughts ?? > SwA support > --- > > Key: AXIS2C-331 > URL: https://issues.apache.org/jira/browse/AXIS2C-331 > Project: Axis2-C > Issue Type: New Feature >Reporter: Martin Voelkle > > Axis2/c doesn't support SwA. It would be usefull to implement it. > If I'm not mistaken, the only open source C/C++ SOAP toolkit that supports it > is gSOAP. -- 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]
