date:20071114

I see that AXIS2_IS_SVR_SIDE property  is being added to figure out 
whether we are on client side or server side.


However, I have doubts if this would work as expected always.

Say, you have already build a conf context on server side, and create a 
service client to consume another service using the same context, from 
within a service. Now form that service client instance, when you access 
the property, it would look like as if you are on server side, but 
actually you are invoking a client.


How are we supposed to deal with such a situation?


Samisa...

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

[jira] Created: (AXIS2C-765) Include exact download location for libxml2 in docs

Include exact download location for libxml2 in docs
---

 Key: AXIS2C-765
 URL: https://issues.apache.org/jira/browse/AXIS2C-765
 Project: Axis2-C
  Issue Type: Improvement
  Components: documentation
Affects Versions: Current (Nightly)
Reporter: Samisa Abeysinghe
Priority: Trivial
 Fix For: 1.2.0


It says, 
libxml2.dll [http://www.xmlsoft.org - download the version = 
libxml2-2.6.27.win32] 

I think the binaries are in ftp://xmlsoft.org/libxml2/win32/. So better to 
mention that in the doc.



-- 
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-755) Codegen segmentation fault when null value is passed


 [ 
https://issues.apache.org/jira/browse/AXIS2C-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Samisa Abeysinghe resolved AXIS2C-755.
--

   Resolution: Fixed
Fix Version/s: 1.2.0

Dimuthu has fixed this issue

 Codegen segmentation fault when null value is passed 
 -

 Key: AXIS2C-755
 URL: https://issues.apache.org/jira/browse/AXIS2C-755
 Project: Axis2-C
  Issue Type: Bug
  Components: build system (Unix/Linux)
Affects Versions: Current (Nightly)
 Environment: Ubuntu
Reporter: Lahiru Gunathilake
Priority: Minor
 Fix For: 1.2.0


 I used Axis2c codegen tool to generate test services and when i'm sending 
 bigger xml file to the service client get timeout then xml stream breaks 
 before sending whole xml file.So there's a null value when axiom get text 
 elements one by one.But generated code doesn't check the null value then this 
 cause a segmentation fault when it pass a null value to atof() method.

-- 
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-757) allow for proxy username/password


 [ 
https://issues.apache.org/jira/browse/AXIS2C-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Samisa Abeysinghe updated AXIS2C-757:
-

Fix Version/s: 1.2.0
 Assignee: Dinesh Premalal

 allow for proxy username/password
 -

 Key: AXIS2C-757
 URL: https://issues.apache.org/jira/browse/AXIS2C-757
 Project: Axis2-C
  Issue Type: New Feature
  Components: core/clientapi
Affects Versions: Current (Nightly)
Reporter: Plamen Neykov
Assignee: Dinesh Premalal
Priority: Blocker
 Fix For: 1.2.0


 Currently the client api allows only proxy_host and proxy_port to be 
 specified. However in most corporate environments the proxy servers require 
 the client to authenticate itself with username/password before it is allowed 
 to connect to internet. This is therefore a critical functionality to allow 
 the use of axis2/c in corpotrate environments.

-- 
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-754) Simple Axis server segfaults when a ?wsdl request is send .


 [ 
https://issues.apache.org/jira/browse/AXIS2C-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dinesh Premalal updated AXIS2C-754:
---

Fix Version/s: 1.2.0

 Simple Axis server segfaults when  a ?wsdl request is send .
 

 Key: AXIS2C-754
 URL: https://issues.apache.org/jira/browse/AXIS2C-754
 Project: Axis2-C
  Issue Type: Bug
  Components: build system (Unix/Linux)
Affects Versions: Current (Nightly)
Reporter: Manjula Peiris
Assignee: Dinesh Premalal
 Fix For: 1.2.0


 when I add parameter name=wsdl_pathpath/of/the/wsdl/parameter to a 
 service and request the wsdl through ,
 http://localhost:9090/axis2/sevices/service_name?wsdl the simple axis server 
 segfaults. Following is the back trace.
 0xb7e36b4b in axis2_http_transport_utils_get_services_static_wsdl 
 (env=0x82731f8, conf_ctx=0x826cba8, 
 request_url=0x8273e20 
 http://127.0.0.1:9090/axis2/sevices/sec_echo?wsdl;) at 
 http_transport_utils.c:896
 896 len = strlen(url_tok[0]);
 (gdb) bt
 #0  0xb7e36b4b in axis2_http_transport_utils_get_services_static_wsdl 
 (env=0x82731f8, conf_ctx=0x826cba8, 
 request_url=0x8273e20 
 http://127.0.0.1:9090/axis2/sevices/sec_echo?wsdl;) at 
 http_transport_utils.c:896
 #1  0xb7e34167 in axis2_http_worker_process_request (http_worker=0x826f408, 
 env=0x82731f8, svr_conn=0x82737c0, simple_request=0x8274190)
 at http_worker.c:280
 #2  0xb7dbd00a in axis2_svr_thread_worker_func (thd=0x8270fa8, 
 data=0x82733c8) at http_svr_thread.c:254
 #3  0xb7e59b85 in dummy_worker (opaque=0x8270fa8) at thread_unix.c:93
 #4  0xb7d8b183 in start_thread () from /lib/libpthread.so.0
 #5  0xb7cf7d2e in clone () from /lib/libc.so.6
 BTW this is working accordingly wit Apache. 

-- 
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-764) Wrong xml write in guththila parser


 [ 
https://issues.apache.org/jira/browse/AXIS2C-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Samisa Abeysinghe updated AXIS2C-764:
-

Fix Version/s: (was: Current (Nightly))
   1.2.0
 Assignee: Dinesh Premalal

 Wrong xml write in guththila parser
 ---

 Key: AXIS2C-764
 URL: https://issues.apache.org/jira/browse/AXIS2C-764
 Project: Axis2-C
  Issue Type: Bug
  Components: guththila
Affects Versions: Current (Nightly)
 Environment: ubuntu
Reporter: Lahiru Gunathilake
Assignee: Dinesh Premalal
Priority: Minor
 Fix For: 1.2.0


 When test some test service with axis2c build with guththila parser I get 
 some wrong output xml from axis.Here's my input xml and out put xml.After 
 building axis2c with libxml2 out put xml is Ok.
 With guththila parser what happened is it doesn't put the closing tag  in 
 correct place
 for tag ns1:echoDoublesResponse 
 xmlns:ns1=http://www.extreme.indiana.edu/wsdl/Benchmark1;
 
 Input xml
 
 ?xml version='1.0' encoding='utf-8'?
soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
   soapenv:Header /
   soapenv:Body
  ns1:echoDoubles 
 xmlns:ns1=http://www.extreme.indiana.edu/wsdl/Benchmark1;
 ns1:input0.0/ns1:input
  /ns1:echoDoubles
   /soapenv:Body
/soapenv:Envelope
 -
 
 output xml with guththila parser
 
 soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
soapenv:Header/soapenv:Header
soapenv:Body xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
   ns1:echoDoublesResponse 
 xmlns:ns1=http://www.extreme.indiana.edu/wsdl/Benchmark1;
  ns1:echoDoublesReturn0.00/ns1:echoDoublesReturn
   /ns1:echoDoublesResponse
/soapenv:Body/soapenv:Envelope
 --
 output xml with libxml2
 ---
 soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;
soapenv:Header/
soapenv:Body
   ns1:echoDoublesResponse 
 xmlns:ns1=http://www.extreme.indiana.edu/wsdl/Benchmark1;
  ns1:echoDoublesReturn0.00/ns1:echoDoublesReturn
   /ns1:echoDoublesResponse
/soapenv:Body/soapenv:Envelope
 

-- 
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-765) Include exact download location for libxml2 in docs


[ 
https://issues.apache.org/jira/browse/AXIS2C-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542361
 ] 

Samisa Abeysinghe commented on AXIS2C-765:
--

BTW, http://www.zlatkovic.com/pub/libxml/ has the latest Windows binaries. 

ftp://xmlsoft.org/libxml2/win32/ does not have the latest

 Include exact download location for libxml2 in docs
 ---

 Key: AXIS2C-765
 URL: https://issues.apache.org/jira/browse/AXIS2C-765
 Project: Axis2-C
  Issue Type: Improvement
  Components: documentation
Affects Versions: Current (Nightly)
Reporter: Samisa Abeysinghe
Priority: Trivial
 Fix For: 1.2.0


 It says, 
 libxml2.dll [http://www.xmlsoft.org - download the version = 
 libxml2-2.6.27.win32] 
 I think the binaries are in ftp://xmlsoft.org/libxml2/win32/. So better to 
 mention that in the doc.

-- 
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-763) Adding AXIS2_IS_SVR_SIDE property to axis2_build_conf_ctx and axis2_build_client_conf_ctx


 [ 
https://issues.apache.org/jira/browse/AXIS2C-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Samisa Abeysinghe updated AXIS2C-763:
-

Fix Version/s: 1.2.0
 Assignee: Damitha Kumarage

 Adding AXIS2_IS_SVR_SIDE property to axis2_build_conf_ctx and 
 axis2_build_client_conf_ctx
 -

 Key: AXIS2C-763
 URL: https://issues.apache.org/jira/browse/AXIS2C-763
 Project: Axis2-C
  Issue Type: Bug
Reporter: Damitha Kumarage
Assignee: Damitha Kumarage
Priority: Trivial
 Fix For: 1.2.0


 I am adding following lines to axis2_build_conf_ctx function
 conf_ctx_base = axis2_conf_ctx_get_base(conf_ctx, env);
 property = axutil_property_create_with_args(env, 2, 0, 0, 
 AXIS2_VALUE_TRUE);
 axis2_ctx_set_property(conf_ctx_base, env, AXIS2_IS_SVR_SIDE, property);
 and adding following to axis2_build_client_conf_ctx function
 conf_ctx_base = axis2_conf_ctx_get_base(conf_ctx, env);
 property = axutil_property_create_with_args(env, 2, 0, 0, 
 AXIS2_VALUE_FALSE);
 axis2_ctx_set_property(conf_ctx_base, env, AXIS2_IS_SVR_SIDE, property);
 This is needed in sandesha2c to identify whether to create a client database 
 or a server database. 

-- 
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-762) Add an option to specify axis2.xml


 [ 
https://issues.apache.org/jira/browse/AXIS2C-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Samisa Abeysinghe updated AXIS2C-762:
-

Fix Version/s: 1.2.0

 Add an option to specify axis2.xml
 --

 Key: AXIS2C-762
 URL: https://issues.apache.org/jira/browse/AXIS2C-762
 Project: Axis2-C
  Issue Type: New Feature
  Components: core/deployment
Affects Versions: 1.1.0
Reporter: Dinesh Premalal
Assignee: Dinesh Premalal
 Fix For: 1.2.0


 Specify a way to give axis2.xml , In axis2.xml which should point to modules 
 and services directories.

-- 
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-760) To build the samples section of the Apache Axis2/C Installation Guide should be modified to include correct configuration command.


 [ 
https://issues.apache.org/jira/browse/AXIS2C-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Samisa Abeysinghe updated AXIS2C-760:
-

Fix Version/s: 1.2.0
 Assignee: Sanjaya Ratnaweera

 To build the samples section of the Apache Axis2/C Installation Guide 
 should be modified to include correct configuration command.
 

 Key: AXIS2C-760
 URL: https://issues.apache.org/jira/browse/AXIS2C-760
 Project: Axis2-C
  Issue Type: Bug
  Components: build system (Unix/Linux)
Affects Versions: 1.1.0
 Environment: Linux
Reporter: Krishantha Samaraweera
Assignee: Sanjaya Ratnaweera
Priority: Trivial
 Fix For: 1.2.0


 Axis2c samples make failed.
 I have download the Apache Axis2/C 1.1.0 Release and installed the source 
 Distribution successfully on Linux. But once I try to build Axis2c samples, 
 make failed with following error messages. 
 echo.h:21:32: error: axis2_svc_skeleton.h: No such file or directory
 echo.h:22:32: error: axutil_log_default.h: No such file or directory
 echo.h:23:34: error: axutil_error_default.h: No such file or directory
 echo.h:24:24: error: axiom_text.h: No such file or directory
 echo.h:25:24: error: axiom_node.h: No such file or directory
 echo.h:26:27: error: axiom_element.h: No such file or directory
 I followed the Apache Axis2/C Installation Guide and used the following 
 configuration option to build samples
 ./configure --prefix=${AXIS2C_HOME} --with-axis2_util=${AXIS2C_HOME}/include 
 -with-axiom=${AXIS2C_HOME}/include
 once  I checked inside the ${AXIS2C_HOME}/include/ , another directory name 
  axis2-1.1 has been found and all the .h fills reside inside this 
 axis2-1.1 directory. So I changed my configuration option as ./configure 
 --prefix=${AXIS2C_HOME} --with-axis2=$AXIS2C_HOME}/include/axis2-1.1  and 
 successfully build the samples.
 To build the samples section of the Apache Axis2/C Installation Guide 
 should be modified to include correct configuration command.

-- 
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-752) Memory leak in raw_xml_in_out_msg_recv.c


 [ 
https://issues.apache.org/jira/browse/AXIS2C-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera reassigned AXIS2C-752:
-

Assignee: Sanjaya Ratnaweera

 Memory leak in raw_xml_in_out_msg_recv.c
 

 Key: AXIS2C-752
 URL: https://issues.apache.org/jira/browse/AXIS2C-752
 Project: Axis2-C
  Issue Type: Bug
  Components: core/receivers
 Environment: Ubuntu 7.10 (Gutsy Gibbon)
Reporter: Senaka Fernando
Assignee: Sanjaya Ratnaweera
 Attachments: diff.txt


 A duplicate svc_skeleton is created inside the 
 axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync() method which is 
 not freed.
 I have modified the code and freed the resource, and tested the samples. The 
 samples executed successfully. Refer diff.txt for proposed patch.

-- 
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-752) Memory leak in raw_xml_in_out_msg_recv.c


 [ 
https://issues.apache.org/jira/browse/AXIS2C-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Damitha Kumarage reassigned AXIS2C-752:
---

Assignee: Damitha Kumarage  (was: Sanjaya Ratnaweera)

 Memory leak in raw_xml_in_out_msg_recv.c
 

 Key: AXIS2C-752
 URL: https://issues.apache.org/jira/browse/AXIS2C-752
 Project: Axis2-C
  Issue Type: Bug
  Components: core/receivers
 Environment: Ubuntu 7.10 (Gutsy Gibbon)
Reporter: Senaka Fernando
Assignee: Damitha Kumarage
 Attachments: diff.txt


 A duplicate svc_skeleton is created inside the 
 axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync() method which is 
 not freed.
 I have modified the code and freed the resource, and tested the samples. The 
 samples executed successfully. Refer diff.txt for proposed patch.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

[jira] Closed: (AXIS2C-747) AXIS2C_LOG_TRACE does not work


 [ 
https://issues.apache.org/jira/browse/AXIS2C-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Damitha Kumarage closed AXIS2C-747.
---


done

 AXIS2C_LOG_TRACE does not work
 --

 Key: AXIS2C-747
 URL: https://issues.apache.org/jira/browse/AXIS2C-747
 Project: Axis2-C
  Issue Type: Bug
Reporter: Damitha Kumarage

 I built axis2c with --enable-trace option and then started server as
 ./axis2_http_server -l5   (Log level trace)
 But I cannot see any traces printed in the axis2.log.
 As I remember even some time back I tried to use trace but it did not work.
 Am I doing a silly mistake or this is not really working with axis2c?

-- 
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-711) Log messages when deployed to apache written to wrong file


 [ 
https://issues.apache.org/jira/browse/AXIS2C-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Damitha Kumarage updated AXIS2C-711:


Fix Version/s: 1.2.0
 Assignee: (was: Damitha Kumarage)

 Log messages when deployed to apache written to wrong file
 --

 Key: AXIS2C-711
 URL: https://issues.apache.org/jira/browse/AXIS2C-711
 Project: Axis2-C
  Issue Type: Bug
  Components: core/deployment
Affects Versions: 1.0.0, 1.1.0
 Environment: RedHat Enterprise Linux 4 running Apache 2.0.52
Reporter: Stefano Pettini
Priority: Minor
 Fix For: 1.2.0


 According to user manual:
 PATH_TO_LOG_FILE has to be replaced with the full path to where you wish to 
 have the Axis2/C log file, for example, /tmp/axis2.log. Note that the log 
 file path should have write access to the daemon user account under which the 
 Apache2 HTTPD process is run.
 It doesn't seem to work: Axis log messages are written to apache's error_log 
 file, not the file specified with PATH_TO_LOG_FILE.

-- 
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-711) Log messages when deployed to apache written to wrong file


 [ 
https://issues.apache.org/jira/browse/AXIS2C-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Damitha Kumarage reassigned AXIS2C-711:
---

Assignee: Damitha Kumarage

 Log messages when deployed to apache written to wrong file
 --

 Key: AXIS2C-711
 URL: https://issues.apache.org/jira/browse/AXIS2C-711
 Project: Axis2-C
  Issue Type: Bug
  Components: core/deployment
Affects Versions: 1.0.0, 1.1.0
 Environment: RedHat Enterprise Linux 4 running Apache 2.0.52
Reporter: Stefano Pettini
Assignee: Damitha Kumarage
Priority: Minor
 Fix For: 1.2.0


 According to user manual:
 PATH_TO_LOG_FILE has to be replaced with the full path to where you wish to 
 have the Axis2/C log file, for example, /tmp/axis2.log. Note that the log 
 file path should have write access to the daemon user account under which the 
 Apache2 HTTPD process is run.
 It doesn't seem to work: Axis log messages are written to apache's error_log 
 file, not the file specified with PATH_TO_LOG_FILE.

-- 
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-725) Parsing WS response with an item without namespace


 [ 
https://issues.apache.org/jira/browse/AXIS2C-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera updated AXIS2C-725:
--

Fix Version/s: 1.2.0

 Parsing WS response with an item without namespace
 --

 Key: AXIS2C-725
 URL: https://issues.apache.org/jira/browse/AXIS2C-725
 Project: Axis2-C
  Issue Type: Bug
  Components: code generation
Affects Versions: 1.1.0
 Environment: Linux
Reporter: Antonio Chiurla
Assignee: Sanjaya Ratnaweera
 Fix For: 1.2.0

 Attachments: pack.tar.gz


 I created stub using wsdl2c (distributed with 1.3 version) with -d adb option.
 The deserialize function failed parsing if Response contains an item without 
 namespace contained in an array.
 I have fixed generated code substituting third parameter in 
 axutil_qname_create with NULL value to the place of an empty string.
 cheers
 Antonio

-- 
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-725) Parsing WS response with an item without namespace


 [ 
https://issues.apache.org/jira/browse/AXIS2C-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera reassigned AXIS2C-725:
-

Assignee: Sanjaya Ratnaweera

 Parsing WS response with an item without namespace
 --

 Key: AXIS2C-725
 URL: https://issues.apache.org/jira/browse/AXIS2C-725
 Project: Axis2-C
  Issue Type: Bug
  Components: code generation
Affects Versions: 1.1.0
 Environment: Linux
Reporter: Antonio Chiurla
Assignee: Sanjaya Ratnaweera
 Fix For: 1.2.0

 Attachments: pack.tar.gz


 I created stub using wsdl2c (distributed with 1.3 version) with -d adb option.
 The deserialize function failed parsing if Response contains an item without 
 namespace contained in an array.
 I have fixed generated code substituting third parameter in 
 axutil_qname_create with NULL value to the place of an empty string.
 cheers
 Antonio

-- 
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-736) Unable to build Axis2/C on Solaris 9


 [ 
https://issues.apache.org/jira/browse/AXIS2C-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera reassigned AXIS2C-736:
-

Assignee: Sanjaya Ratnaweera

 Unable to build Axis2/C on Solaris 9
 

 Key: AXIS2C-736
 URL: https://issues.apache.org/jira/browse/AXIS2C-736
 Project: Axis2-C
  Issue Type: Bug
  Components: build system (Unix/Linux)
Affects Versions: 1.1.0
 Environment: SunOS raphael 5.9 Generic_112233-11 sun4u sparc 
 SUNW,Sun-Fire-280R
 gcc (GCC) 3.3.6
Reporter: Chris Rose
Assignee: Sanjaya Ratnaweera

 I am unable to configure and build Axis2/C 1.1.0 on Solaris 9.
 /bin/bash ../../../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 -Werror  -c -o uuid_gen_unix.lo 
 uuid_gen_unix.c
  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 -Werror 
 -c uuid_gen_unix.c  -fPIC -DPIC -o .libs/uuid_gen_unix.o
 In file included from 
 ../../../include/platforms/axutil_platform_auto_sense.h:51,
  from uuid_gen_unix.c:50:
 ../../../include/platforms/unix/axutil_unix.h:115:20: getopt.h: No such file 
 or directory
 This is basically the first step of the build; at least it fails fast! ;)

-- 
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-743) some return paths in axiom_data_handler_read_from() does not call fclose() on the open file stream, in data_handler.c


 [ 
https://issues.apache.org/jira/browse/AXIS2C-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera reassigned AXIS2C-743:
-

Assignee: Sanjaya Ratnaweera

 some return paths in axiom_data_handler_read_from() does not call fclose() on 
 the open file stream, in data_handler.c
 -

 Key: AXIS2C-743
 URL: https://issues.apache.org/jira/browse/AXIS2C-743
 Project: Axis2-C
  Issue Type: Bug
  Components: xml/om
 Environment: Ubuntu 7.10 (Gutsy Gibbon)
Reporter: Senaka Fernando
Assignee: Sanjaya Ratnaweera
Priority: Minor

 in axis2/c/axiom/src/attachments/data_handler.c 
 axiom_data_handler_read_from() some return paths do not close the open file 
 stream.

-- 
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-737) Unable to build Axis2/C on Linux RHEL3


 [ 
https://issues.apache.org/jira/browse/AXIS2C-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera reassigned AXIS2C-737:
-

Assignee: Sanjaya Ratnaweera

 Unable to build Axis2/C on Linux RHEL3
 --

 Key: AXIS2C-737
 URL: https://issues.apache.org/jira/browse/AXIS2C-737
 Project: Axis2-C
  Issue Type: Bug
  Components: build system (Unix/Linux)
Affects Versions: 1.1.0
 Environment: Linux matisse 2.4.21-47.0.1.ELsmp #1 SMP Fri Oct 13 
 17:56:20 EDT 2006 i686 i686 i386 GNU/Linux
 gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-56)
 ./configure  --enable-guththila=yes --enable-libxml2=no
Reporter: Chris Rose
Assignee: Sanjaya Ratnaweera

 Build eventually fails at this point:
  gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../include 
 -I../../../src/core/description -I../../../src/core/engine 
 -I../../../src/core/phaseresolver -I../../../src/core/deployment 
 -I../../../src/core/util -I../../../axiom/include -I../../../neethi/include 
 -I../../../util/include -g -O2 -D_LARGEFILE64_SOURCE -ansi -Wall -Werror 
 -Wno-implicit-function-declaration -g -DAXIS2_SVR_MULTI_THREADED -MT 
 conf_builder.lo -MD -MP -MF .deps/conf_builder.Tpo -c conf_builder.c  -fPIC 
 -DPIC -o .libs/conf_builder.o
 cc1: warnings being treated as errors
 conf_builder.c: In function `axis2_conf_builder_process_transport_senders':
 conf_builder.c:669: warning: `transport_enum' might be used uninitialized in 
 this function
 make[4]: *** [conf_builder.lo] Error 1
 make[4]: Leaving directory 
 `/home/rosec/modules/pkg_tree/pkg_src/axis2c-1.1.0/obj.i686-redhat-linux-es3/axis2c-src-1.1.0/src/core/deployment'
 Patching configure to remove -Werror from the CFLAGS in the base configure 
 script allows the build to succeed.

-- 
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-738) Unreachable code found in http_reciever.c


 [ 
https://issues.apache.org/jira/browse/AXIS2C-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera reassigned AXIS2C-738:
-

Assignee: Sanjaya Ratnaweera

 Unreachable code found in http_reciever.c
 -

 Key: AXIS2C-738
 URL: https://issues.apache.org/jira/browse/AXIS2C-738
 Project: Axis2-C
  Issue Type: Bug
  Components: transport/http
 Environment: Ubuntu 7.10 (Gutsy Gibbon)
Reporter: Senaka Fernando
Assignee: Sanjaya Ratnaweera
Priority: Minor
 Attachments: diff.txt


 Line 296 in /axis2/c/src/core/transport/http/receiver/http_reciever.c, is 
 never reached.

-- 
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-741) axis2_any_content_type_add_value(...), in any_content_type.c always returns AXIS2_SUCCESS.


 [ 
https://issues.apache.org/jira/browse/AXIS2C-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera reassigned AXIS2C-741:
-

Assignee: Sanjaya Ratnaweera

 axis2_any_content_type_add_value(...), in any_content_type.c always returns 
 AXIS2_SUCCESS.
 --

 Key: AXIS2C-741
 URL: https://issues.apache.org/jira/browse/AXIS2C-741
 Project: Axis2-C
  Issue Type: Bug
  Components: core/addressing
 Environment: Ubuntu 7.10 (Gutsy Gibbon)
Reporter: Senaka Fernando
Assignee: Sanjaya Ratnaweera
 Attachments: diff.txt


 AXIS2_EXTERN axis2_status_t AXIS2_CALL
 axis2_any_content_type_add_value(
 axis2_any_content_type_t * any_content_type,
 const axutil_env_t * env,
 const axutil_qname_t * qname,
 const axis2_char_t * value)
 In c/src/core/addr/any_content_type.c returns AXIS2_SUCCESS, irrespective of 
 a successful operation.

-- 
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-744) wsdl2c tool generated call to non-existent AXIS2_QNAME_TO_STRING


 [ 
https://issues.apache.org/jira/browse/AXIS2C-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera reassigned AXIS2C-744:
-

Assignee: Sanjaya Ratnaweera

 wsdl2c tool generated call to non-existent AXIS2_QNAME_TO_STRING
 

 Key: AXIS2C-744
 URL: https://issues.apache.org/jira/browse/AXIS2C-744
 Project: Axis2-C
  Issue Type: Bug
  Components: code generation
Affects Versions: 1.1.0
 Environment: I'm running Windows XP SP2, but this looks like it is 
 not platform specific.
Reporter: Michael Mole
Assignee: Sanjaya Ratnaweera
Priority: Minor
 Fix For: Current (Nightly)


 The WSDL2C code generation tool released with Axis2/Java 1.3 is generating 
 calls to a non-existent AXIS2_QNAME_TO_STRING.  This is causing linker 
 errors.  I did a search through the Axis2/C 1.1 source and couldn't find this 
 function.  There is, however, a function called axutil_qname_to_string 
 located in axutil_qname.c.  It appears that somewhere along the line, the 
 code generation tool, and the Axis2/C source got out of sync.

-- 
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-751) Major Memory leak in http_transport_utils.c with REST


 [ 
https://issues.apache.org/jira/browse/AXIS2C-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Samisa Abeysinghe updated AXIS2C-751:
-

Fix Version/s: 1.2.0
 Assignee: Damitha Kumarage

 Major Memory leak in http_transport_utils.c with REST
 -

 Key: AXIS2C-751
 URL: https://issues.apache.org/jira/browse/AXIS2C-751
 Project: Axis2-C
  Issue Type: Bug
  Components: transport/http, xml/om, xml/soap
 Environment: Ubuntu 7.10 (Gutsy Gibbon)
Reporter: Senaka Fernando
Assignee: Damitha Kumarage
 Fix For: 1.2.0

 Attachments: diff.txt


 We are not freeing the om_builder that we create when using the REST mode 
 within the axis2_http_transport_utils_process_http_post_request() method. 
 This leads to a major memory leak, amounting to somewhere around 26KB 
 (indirect leaks) -- according to valgrind when running the echo_rest sample 
 just once. Therefore, I believe this needs a reasonable amount of attention.
 Unlike, non-REST invocations where the soap_builder frees the om_builder, in 
 REST as we don't create a soap_builder, the om_builder basically does not get 
 freed.
 I have done a modification in http_transport_utils.c, so that if the 
 om_builder is not freed when the soap_builder is null, it will get freed 
 before we leave the axis2_http_transport_utils_process_http_post_request() 
 method block. Therefore, even for a non-REST invocation if the soap_builder 
 has been freed (or if it is null) but, the om_builder is not, the om_builder 
 will automatically get freed within the 
 axis2_http_transport_utils_process_http_post_request() method before we leave 
 the method.
 I have tested the modification with all the samples and all were invoked 
 successfully.
 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-748) Memory leak in dep_engine.c


 [ 
https://issues.apache.org/jira/browse/AXIS2C-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Damitha Kumarage updated AXIS2C-748:


Fix Version/s: 1.2.0

 Memory leak in dep_engine.c
 ---

 Key: AXIS2C-748
 URL: https://issues.apache.org/jira/browse/AXIS2C-748
 Project: Axis2-C
  Issue Type: Bug
  Components: core/deployment
 Environment: Ubuntu 7.04 (Feisty Fawn)
Reporter: Senaka Fernando
 Fix For: 1.2.0

 Attachments: diff.txt


 When we load the dep_engine, we fetch the out-fault phases and assign them to 
 the configuration. During the fetching process a new array list is created. 
 This contains the phases. However, before assigning it, we have duplicated 
 the array list and assigned the duplicate. And, during the process we have 
 not freed the initial (fetched) array list.
 While going through the code, I understood that a duplicate is not necessary 
 as the fetching process already creates a duplicate. Thus, I have removed the 
 duplicate (new_out_fault_phases) and assigned the array list that was fetched 
 (out_fault_phases), to the configuration.
 This resolves the memory leak. (refer 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] Updated: (AXIS2C-752) Memory leak in raw_xml_in_out_msg_recv.c


 [ 
https://issues.apache.org/jira/browse/AXIS2C-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Damitha Kumarage updated AXIS2C-752:


Fix Version/s: 1.2.0

 Memory leak in raw_xml_in_out_msg_recv.c
 

 Key: AXIS2C-752
 URL: https://issues.apache.org/jira/browse/AXIS2C-752
 Project: Axis2-C
  Issue Type: Bug
  Components: core/receivers
 Environment: Ubuntu 7.10 (Gutsy Gibbon)
Reporter: Senaka Fernando
Assignee: Damitha Kumarage
 Fix For: 1.2.0

 Attachments: diff.txt


 A duplicate svc_skeleton is created inside the 
 axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync() method which is 
 not freed.
 I have modified the code and freed the resource, and tested the samples. The 
 samples executed successfully. Refer diff.txt for proposed patch.

-- 
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-748) Memory leak in dep_engine.c


 [ 
https://issues.apache.org/jira/browse/AXIS2C-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Damitha Kumarage reassigned AXIS2C-748:
---

Assignee: Damitha Kumarage

 Memory leak in dep_engine.c
 ---

 Key: AXIS2C-748
 URL: https://issues.apache.org/jira/browse/AXIS2C-748
 Project: Axis2-C
  Issue Type: Bug
  Components: core/deployment
 Environment: Ubuntu 7.04 (Feisty Fawn)
Reporter: Senaka Fernando
Assignee: Damitha Kumarage
 Fix For: 1.2.0

 Attachments: diff.txt


 When we load the dep_engine, we fetch the out-fault phases and assign them to 
 the configuration. During the fetching process a new array list is created. 
 This contains the phases. However, before assigning it, we have duplicated 
 the array list and assigned the duplicate. And, during the process we have 
 not freed the initial (fetched) array list.
 While going through the code, I understood that a duplicate is not necessary 
 as the fetching process already creates a duplicate. Thus, I have removed the 
 duplicate (new_out_fault_phases) and assigned the array list that was fetched 
 (out_fault_phases), to the configuration.
 This resolves the memory leak. (refer 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] Assigned: (AXIS2C-740) Definition of type axis2_bool_t based on an enumeration


 [ 
https://issues.apache.org/jira/browse/AXIS2C-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera reassigned AXIS2C-740:
-

Assignee: Sanjaya Ratnaweera

 Definition of type axis2_bool_t based on an enumeration
 ---

 Key: AXIS2C-740
 URL: https://issues.apache.org/jira/browse/AXIS2C-740
 Project: Axis2-C
  Issue Type: Improvement
  Components: util
 Environment: Ubuntu 7.10 (Gutsy Gibbon)
Reporter: Senaka Fernando
Assignee: Sanjaya Ratnaweera
 Attachments: diff.txt


 Boolean types have only two states.
 As C does not have such a type, an alternate mechanism has been used as, 
 typedef int axis2_bool_t;
 Now, legally axis2_bool_t types can have any integer value.
 I propose that it should only be limited to two values.
 Thus it should be defined as typedef enum {AXIS2_FALSE, AXIS2_TRUE} 
 axis2_bool_t;
 in C, types defined in such a manner do accept any integer value. But, when 
 compiled using a C++ compiler, it would flag an error which should be the 
 desired behavior.
 Ex:- in C++, axis2_bool_t myVar = 100; would result in, error: invalid 
 conversion from 'int' to 'axis2_bool_t'

-- 
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-742) Improper placement of code in data_handler.c leads to increased time overhead and memory leaks.


 [ 
https://issues.apache.org/jira/browse/AXIS2C-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera reassigned AXIS2C-742:
-

Assignee: Sanjaya Ratnaweera

 Improper placement of code in data_handler.c leads to increased time overhead 
 and memory leaks.
 ---

 Key: AXIS2C-742
 URL: https://issues.apache.org/jira/browse/AXIS2C-742
 Project: Axis2-C
  Issue Type: Bug
  Components: xml/om
 Environment: Ubuntu 7.10 (Gutsy Gibbon)
Reporter: Senaka Fernando
Assignee: Sanjaya Ratnaweera
 Attachments: diff.txt


 The code portion
 struct stat stat_p;
 if (-1 == stat(data_handler-file_name, stat_p))
 {
 return AXIS2_FAILURE;
 }
 else if (stat_p.st_size == 0)
 {
 *output_stream = NULL;
 *output_stream_size = 0;
 return AXIS2_SUCCESS;
 }
 in axis2/c/axiom/src/attachments/data_handler.c (line 175) is repeatedly 
 executed and thus leads to increased time overhead.
 Nevertheless, if the function is to return, resources occupied by byte_stream 
 is not freed, and thus leads to a memory leak.
 I propose to move this portion of code out of the do-while loop.
 Reasons:
  * Evaluation of stat() just one time is enough as any other error that could 
 occur during reading the file is returned by the fread() and ferror() 
 combination.
  * Therefore, repeated evaluation of a parameter that is technically not 
 supposed to change, is not worth it.
  * Even it does change, that particular change may occur just after stat() 
 was evaluated, and thus makes the above argument base-less.
 Thus, it seems to be the best 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] Assigned: (AXIS2C-739) Function Definition does not match declaration in soap_builder.c


 [ 
https://issues.apache.org/jira/browse/AXIS2C-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera reassigned AXIS2C-739:
-

Assignee: Sanjaya Ratnaweera

 Function Definition does not match declaration in soap_builder.c
 

 Key: AXIS2C-739
 URL: https://issues.apache.org/jira/browse/AXIS2C-739
 Project: Axis2-C
  Issue Type: Bug
  Components: xml/om
 Environment: Ubuntu 7.10 (Gutsy Gibbon)
Reporter: Senaka Fernando
Assignee: Sanjaya Ratnaweera
 Attachments: diff.txt


 Function Definition does not match declaration in soap_builder.c, in Line 726.
 The type should in fact be axis2_bool_t, but is stated as int, which violates 
 the convention, and thus leading to potential bugs.

-- 
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-719) v2.0.x apache module compilation error

[
https://issues.apache.org/jira/browse/AXIS2C-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dushshantha Chandradasa reassigned AXIS2C-719:
--

Assignee: Dushshantha Chandradasa

v2.0.x apache module compilation error
--

Key: AXIS2C-719
URL: https://issues.apache.org/jira/browse/AXIS2C-719
Project: Axis2-C
Issue Type: Bug
Components: build system (Windows)
Affects Versions: 1.1.0
Environment: Visual Studio 2005
apache v2.0.59
apache v2.0.61
DEBUG=1
APACHE_VERSION_2_0_X = 1
Reporter: David Klassen
Assignee: Dushshantha Chandradasa

I read how to install the apache module, and naturally decided to use 2.2.x.
Everything installed fine. However after finding the apache httpd.exe memory
size was growing fast for 25 concurrent users (AXIS2C-717), I decided to
install an older version of apache to make sure this was not related to some
apache 2.2.x features interfering with axis2c. Looking on-line I remembered
seeing that special configuration changes were needed to work with 2.0.x
version of apache:
http://ws.apache.org/axis2/c/docs/axis2c_manual.html#mod_axis2
I set the configuration setting:
APACHE_VERSION_2_0_59 = 1
However a compilation error still occurrs:
C:\SOAP\axis2c-src-1.1.0\axis2c-src-1.1.0\build\win32nmake
axis2_apache_module
Microsoft (R) Program Maintenance Utility Version 8.00.50727.42
Copyright (C) Microsoft Corporation. All rights reserved.
Creating library ..\deploy\lib\mod_axis2.lib and object
..\deploy\lib\mod_axis2.exp
mod_axis2.obj : error LNK2019: unresolved external symbol
__imp__ap_real_exit_code referenced in function _axis2_module_init
..\deploy\lib\mod_axis2.dll : fatal error LNK1120: 1 unresolved externals
NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio
8\VC\BIN\link.exe' : return code '0x460'
Stop.
Unfortunately I am not sure of the best remedy yet. Perhaps axis2c does not
support apache 2.0.x ? If so the on-line documentation should be updated.
However I would like to make sure the memory leak is not constrained to 2.2.x
alone...

--
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-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
]

Sanjaya Ratnaweera reassigned AXIS2C-710:
-

Assignee: Sanjaya Ratnaweera

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

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] Assigned: (AXIS2C-706) google sample fails when the message is chunked.


 [ 
https://issues.apache.org/jira/browse/AXIS2C-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dushshantha Chandradasa reassigned AXIS2C-706:
--

Assignee: Dushshantha Chandradasa

 google sample fails when the message is chunked.
 

 Key: AXIS2C-706
 URL: https://issues.apache.org/jira/browse/AXIS2C-706
 Project: Axis2-C
  Issue Type: Bug
  Components: core/transport
 Environment: Linux
Reporter: Dushshantha Chandradasa
Assignee: Dushshantha Chandradasa

 google sample fails when the message is chunked. The fault string says that 
 Content length must be specified.

-- 
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-707) broken link in axis2/c manual


 [ 
https://issues.apache.org/jira/browse/AXIS2C-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera reassigned AXIS2C-707:
-

Assignee: Sanjaya Ratnaweera

 broken link in axis2/c manual
 -

 Key: AXIS2C-707
 URL: https://issues.apache.org/jira/browse/AXIS2C-707
 Project: Axis2-C
  Issue Type: Bug
  Components: documentation
 Environment: webpage
Reporter: Ryan Jarvis
Assignee: Sanjaya Ratnaweera
Priority: Minor

 The link to the hello_svc.c file displayed in the 1.1 Hello Service section 
 is not valid.  Link should take user to appropriate file.

-- 
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-721) Requesting step-by-step guides


 [ 
https://issues.apache.org/jira/browse/AXIS2C-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dushshantha Chandradasa reassigned AXIS2C-721:
--

Assignee: Dushshantha Chandradasa

 Requesting step-by-step guides
 --

 Key: AXIS2C-721
 URL: https://issues.apache.org/jira/browse/AXIS2C-721
 Project: Axis2-C
  Issue Type: Wish
  Components: documentation
Reporter: Senaka Fernando
Assignee: Dushshantha Chandradasa

 It would be great if someone could create a step-by-step guide in creating a 
 service and a client, instead of just adding an example in the manual. What I 
 mean is an example which is gradually built from the most basic step into a 
 really advanced implimentation.

-- 
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-694) Memory leak occurs when inserting element to hash table


 [ 
https://issues.apache.org/jira/browse/AXIS2C-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dushshantha Chandradasa reassigned AXIS2C-694:
--

Assignee: Dushshantha Chandradasa

 Memory leak occurs when inserting element to hash table
 ---

 Key: AXIS2C-694
 URL: https://issues.apache.org/jira/browse/AXIS2C-694
 Project: Axis2-C
  Issue Type: Bug
  Components: util
Affects Versions: 1.1.0
 Environment: windows
Reporter: S.Uthaiyashankar
Assignee: Dushshantha Chandradasa

 If an non null element is inserted to hash table when the hash table is full, 
 and the key is not available in the hash table, then memory leaks occur.  
 refer the following stack trace:
 axutil_allocator_malloc_impl 
 [d:\manjula\axis2\util\src\allocator.c:65]
 axutil_hash_find_entry [d:\manjula\axis2\util\src\hash.c:294]
 axutil_hash_set [d:\manjula\axis2\util\src\hash.c:362]
 rampart_set_security_processed_result 
 [d:\manjula\rampart\src\util\rampart_sec_processed_result.c:41]
 rampart_shp_process_encrypted_key 
 [d:\manjula\rampart\src\util\rampart_sec_header_processor.c:558]
 rampart_shp_process_message 
 [d:\manjula\rampart\src\util\rampart_sec_header_processor.c:1135]
 rampart_in_handler_invoke 
 [d:\manjula\rampart\src\handlers\rampart_in_handler.c:138]
 axis2_handler_invoke 
 [d:\manjula\axis2\src\core\engine\handler.c:91]
 axis2_phase_invoke [d:\manjula\axis2\src\core\engine\phase.c:199]

-- 
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-663) There are no guides provided for Code Generation in Axis2C


 [ 
https://issues.apache.org/jira/browse/AXIS2C-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dushshantha Chandradasa reassigned AXIS2C-663:
--

Assignee: Dushshantha Chandradasa

 There are no guides provided for Code Generation in Axis2C
 --

 Key: AXIS2C-663
 URL: https://issues.apache.org/jira/browse/AXIS2C-663
 Project: Axis2-C
  Issue Type: Bug
  Components: documentation
Reporter: Evanthika Amarasiri
Assignee: Dushshantha Chandradasa

 There are no guides provided for code generation. Please provide such a guide

-- 
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-682) WSDL2C tool


 [ 
https://issues.apache.org/jira/browse/AXIS2C-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dushshantha Chandradasa reassigned AXIS2C-682:
--

Assignee: Dushshantha Chandradasa

 WSDL2C tool
 ---

 Key: AXIS2C-682
 URL: https://issues.apache.org/jira/browse/AXIS2C-682
 Project: Axis2-C
  Issue Type: Wish
 Environment: Windows
Reporter: Sneha Jain
Assignee: Dushshantha Chandradasa
 Attachments: wsdl2c.bat


 Hi,
 I am using axis2/c 1.0.0. release .. 
 I want to generate code using tools. But the binary distribution does not 
 contain the WSDL2C tool.
 Where can i download this tool from. i tried searching the apache site...It 
 just said it comes alond with Axis2/java code generation project..but i 
 couldnot get which binary to download.
 Could you please help me out of this, its very urgent.
 Thank you,
 Sneha

-- 
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-720) The example file, hello_svc.c given in the documentation is not available


 [ 
https://issues.apache.org/jira/browse/AXIS2C-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dushshantha Chandradasa reassigned AXIS2C-720:
--

Assignee: Dushshantha Chandradasa

 The example file, hello_svc.c given in the documentation is not available
 -

 Key: AXIS2C-720
 URL: https://issues.apache.org/jira/browse/AXIS2C-720
 Project: Axis2-C
  Issue Type: Task
Reporter: Senaka Fernando
Assignee: Dushshantha Chandradasa
Priority: Minor

 The example files given in the documentation are not available. Please check 
 on that. This is the link 
 http://ws.apache.org/axis2/c/docs/axis2c_manual.html#quick_start and the 
 missing file is hello_svc.c
 Thanks,
 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-682) WSDL2C tool


 [ 
https://issues.apache.org/jira/browse/AXIS2C-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dushshantha Chandradasa updated AXIS2C-682:
---

Fix Version/s: 1.2.0

 WSDL2C tool
 ---

 Key: AXIS2C-682
 URL: https://issues.apache.org/jira/browse/AXIS2C-682
 Project: Axis2-C
  Issue Type: Wish
 Environment: Windows
Reporter: Sneha Jain
Assignee: Dushshantha Chandradasa
 Fix For: 1.2.0

 Attachments: wsdl2c.bat


 Hi,
 I am using axis2/c 1.0.0. release .. 
 I want to generate code using tools. But the binary distribution does not 
 contain the WSDL2C tool.
 Where can i download this tool from. i tried searching the apache site...It 
 just said it comes alond with Axis2/java code generation project..but i 
 couldnot get which binary to download.
 Could you please help me out of this, its very urgent.
 Thank you,
 Sneha

-- 
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-663) There are no guides provided for Code Generation in Axis2C


 [ 
https://issues.apache.org/jira/browse/AXIS2C-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dushshantha Chandradasa updated AXIS2C-663:
---

Fix Version/s: 1.2.0

 There are no guides provided for Code Generation in Axis2C
 --

 Key: AXIS2C-663
 URL: https://issues.apache.org/jira/browse/AXIS2C-663
 Project: Axis2-C
  Issue Type: Bug
  Components: documentation
Reporter: Evanthika Amarasiri
Assignee: Dushshantha Chandradasa
 Fix For: 1.2.0


 There are no guides provided for code generation. Please provide such a guide

-- 
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-744) wsdl2c tool generated call to non-existent AXIS2_QNAME_TO_STRING


 [ 
https://issues.apache.org/jira/browse/AXIS2C-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera updated AXIS2C-744:
--

Fix Version/s: (was: Current (Nightly))
   1.2.0

 wsdl2c tool generated call to non-existent AXIS2_QNAME_TO_STRING
 

 Key: AXIS2C-744
 URL: https://issues.apache.org/jira/browse/AXIS2C-744
 Project: Axis2-C
  Issue Type: Bug
  Components: code generation
Affects Versions: 1.1.0
 Environment: I'm running Windows XP SP2, but this looks like it is 
 not platform specific.
Reporter: Michael Mole
Assignee: Sanjaya Ratnaweera
Priority: Minor
 Fix For: 1.2.0


 The WSDL2C code generation tool released with Axis2/Java 1.3 is generating 
 calls to a non-existent AXIS2_QNAME_TO_STRING.  This is causing linker 
 errors.  I did a search through the Axis2/C 1.1 source and couldn't find this 
 function.  There is, however, a function called axutil_qname_to_string 
 located in axutil_qname.c.  It appears that somewhere along the line, the 
 code generation tool, and the Axis2/C source got out of sync.

-- 
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-707) broken link in axis2/c manual


 [ 
https://issues.apache.org/jira/browse/AXIS2C-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera updated AXIS2C-707:
--

Fix Version/s: 1.2.0

 broken link in axis2/c manual
 -

 Key: AXIS2C-707
 URL: https://issues.apache.org/jira/browse/AXIS2C-707
 Project: Axis2-C
  Issue Type: Bug
  Components: documentation
 Environment: webpage
Reporter: Ryan Jarvis
Assignee: Sanjaya Ratnaweera
Priority: Minor
 Fix For: 1.2.0


 The link to the hello_svc.c file displayed in the 1.1 Hello Service section 
 is not valid.  Link should take user to appropriate file.

-- 
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
]

Sanjaya Ratnaweera updated AXIS2C-710:
--

Fix Version/s: 1.2.0

pkg-config not detected properly during configure
-

--
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-737) Unable to build Axis2/C on Linux RHEL3


 [ 
https://issues.apache.org/jira/browse/AXIS2C-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera updated AXIS2C-737:
--

Fix Version/s: 1.2.0

 Unable to build Axis2/C on Linux RHEL3
 --

 Key: AXIS2C-737
 URL: https://issues.apache.org/jira/browse/AXIS2C-737
 Project: Axis2-C
  Issue Type: Bug
  Components: build system (Unix/Linux)
Affects Versions: 1.1.0
 Environment: Linux matisse 2.4.21-47.0.1.ELsmp #1 SMP Fri Oct 13 
 17:56:20 EDT 2006 i686 i686 i386 GNU/Linux
 gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-56)
 ./configure  --enable-guththila=yes --enable-libxml2=no
Reporter: Chris Rose
Assignee: Sanjaya Ratnaweera
 Fix For: 1.2.0


 Build eventually fails at this point:
  gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../include 
 -I../../../src/core/description -I../../../src/core/engine 
 -I../../../src/core/phaseresolver -I../../../src/core/deployment 
 -I../../../src/core/util -I../../../axiom/include -I../../../neethi/include 
 -I../../../util/include -g -O2 -D_LARGEFILE64_SOURCE -ansi -Wall -Werror 
 -Wno-implicit-function-declaration -g -DAXIS2_SVR_MULTI_THREADED -MT 
 conf_builder.lo -MD -MP -MF .deps/conf_builder.Tpo -c conf_builder.c  -fPIC 
 -DPIC -o .libs/conf_builder.o
 cc1: warnings being treated as errors
 conf_builder.c: In function `axis2_conf_builder_process_transport_senders':
 conf_builder.c:669: warning: `transport_enum' might be used uninitialized in 
 this function
 make[4]: *** [conf_builder.lo] Error 1
 make[4]: Leaving directory 
 `/home/rosec/modules/pkg_tree/pkg_src/axis2c-1.1.0/obj.i686-redhat-linux-es3/axis2c-src-1.1.0/src/core/deployment'
 Patching configure to remove -Werror from the CFLAGS in the base configure 
 script allows the build to succeed.

-- 
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-739) Function Definition does not match declaration in soap_builder.c


 [ 
https://issues.apache.org/jira/browse/AXIS2C-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera updated AXIS2C-739:
--

Fix Version/s: 1.2.0

 Function Definition does not match declaration in soap_builder.c
 

 Key: AXIS2C-739
 URL: https://issues.apache.org/jira/browse/AXIS2C-739
 Project: Axis2-C
  Issue Type: Bug
  Components: xml/om
 Environment: Ubuntu 7.10 (Gutsy Gibbon)
Reporter: Senaka Fernando
Assignee: Sanjaya Ratnaweera
 Fix For: 1.2.0

 Attachments: diff.txt


 Function Definition does not match declaration in soap_builder.c, in Line 726.
 The type should in fact be axis2_bool_t, but is stated as int, which violates 
 the convention, and thus leading to potential bugs.

-- 
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-740) Definition of type axis2_bool_t based on an enumeration


 [ 
https://issues.apache.org/jira/browse/AXIS2C-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera updated AXIS2C-740:
--

Fix Version/s: 1.2.0

 Definition of type axis2_bool_t based on an enumeration
 ---

 Key: AXIS2C-740
 URL: https://issues.apache.org/jira/browse/AXIS2C-740
 Project: Axis2-C
  Issue Type: Improvement
  Components: util
 Environment: Ubuntu 7.10 (Gutsy Gibbon)
Reporter: Senaka Fernando
Assignee: Sanjaya Ratnaweera
 Fix For: 1.2.0

 Attachments: diff.txt


 Boolean types have only two states.
 As C does not have such a type, an alternate mechanism has been used as, 
 typedef int axis2_bool_t;
 Now, legally axis2_bool_t types can have any integer value.
 I propose that it should only be limited to two values.
 Thus it should be defined as typedef enum {AXIS2_FALSE, AXIS2_TRUE} 
 axis2_bool_t;
 in C, types defined in such a manner do accept any integer value. But, when 
 compiled using a C++ compiler, it would flag an error which should be the 
 desired behavior.
 Ex:- in C++, axis2_bool_t myVar = 100; would result in, error: invalid 
 conversion from 'int' to 'axis2_bool_t'

-- 
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-719) v2.0.x apache module compilation error

[
https://issues.apache.org/jira/browse/AXIS2C-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dushshantha Chandradasa updated AXIS2C-719:
---

Fix Version/s: 1.2.0

v2.0.x apache module compilation error
--

--
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-706) google sample fails when the message is chunked.


 [ 
https://issues.apache.org/jira/browse/AXIS2C-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dushshantha Chandradasa updated AXIS2C-706:
---

Fix Version/s: 1.2.0

 google sample fails when the message is chunked.
 

 Key: AXIS2C-706
 URL: https://issues.apache.org/jira/browse/AXIS2C-706
 Project: Axis2-C
  Issue Type: Bug
  Components: core/transport
 Environment: Linux
Reporter: Dushshantha Chandradasa
Assignee: Dushshantha Chandradasa
 Fix For: 1.2.0


 google sample fails when the message is chunked. The fault string says that 
 Content length must be specified.

-- 
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-720) The example file, hello_svc.c given in the documentation is not available


 [ 
https://issues.apache.org/jira/browse/AXIS2C-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dushshantha Chandradasa updated AXIS2C-720:
---

Fix Version/s: 1.2.0

 The example file, hello_svc.c given in the documentation is not available
 -

 Key: AXIS2C-720
 URL: https://issues.apache.org/jira/browse/AXIS2C-720
 Project: Axis2-C
  Issue Type: Task
Reporter: Senaka Fernando
Assignee: Dushshantha Chandradasa
Priority: Minor
 Fix For: 1.2.0


 The example files given in the documentation are not available. Please check 
 on that. This is the link 
 http://ws.apache.org/axis2/c/docs/axis2c_manual.html#quick_start and the 
 missing file is hello_svc.c
 Thanks,
 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-742) Improper placement of code in data_handler.c leads to increased time overhead and memory leaks.


 [ 
https://issues.apache.org/jira/browse/AXIS2C-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera updated AXIS2C-742:
--

Fix Version/s: 1.2.0

 Improper placement of code in data_handler.c leads to increased time overhead 
 and memory leaks.
 ---

 Key: AXIS2C-742
 URL: https://issues.apache.org/jira/browse/AXIS2C-742
 Project: Axis2-C
  Issue Type: Bug
  Components: xml/om
 Environment: Ubuntu 7.10 (Gutsy Gibbon)
Reporter: Senaka Fernando
Assignee: Sanjaya Ratnaweera
 Fix For: 1.2.0

 Attachments: diff.txt


 The code portion
 struct stat stat_p;
 if (-1 == stat(data_handler-file_name, stat_p))
 {
 return AXIS2_FAILURE;
 }
 else if (stat_p.st_size == 0)
 {
 *output_stream = NULL;
 *output_stream_size = 0;
 return AXIS2_SUCCESS;
 }
 in axis2/c/axiom/src/attachments/data_handler.c (line 175) is repeatedly 
 executed and thus leads to increased time overhead.
 Nevertheless, if the function is to return, resources occupied by byte_stream 
 is not freed, and thus leads to a memory leak.
 I propose to move this portion of code out of the do-while loop.
 Reasons:
  * Evaluation of stat() just one time is enough as any other error that could 
 occur during reading the file is returned by the fread() and ferror() 
 combination.
  * Therefore, repeated evaluation of a parameter that is technically not 
 supposed to change, is not worth it.
  * Even it does change, that particular change may occur just after stat() 
 was evaluated, and thus makes the above argument base-less.
 Thus, it seems to be the best 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] Updated: (AXIS2C-738) Unreachable code found in http_reciever.c


 [ 
https://issues.apache.org/jira/browse/AXIS2C-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera updated AXIS2C-738:
--

Fix Version/s: 1.2.0

 Unreachable code found in http_reciever.c
 -

 Key: AXIS2C-738
 URL: https://issues.apache.org/jira/browse/AXIS2C-738
 Project: Axis2-C
  Issue Type: Bug
  Components: transport/http
 Environment: Ubuntu 7.10 (Gutsy Gibbon)
Reporter: Senaka Fernando
Assignee: Sanjaya Ratnaweera
Priority: Minor
 Fix For: 1.2.0

 Attachments: diff.txt


 Line 296 in /axis2/c/src/core/transport/http/receiver/http_reciever.c, is 
 never reached.

-- 
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-743) some return paths in axiom_data_handler_read_from() does not call fclose() on the open file stream, in data_handler.c


 [ 
https://issues.apache.org/jira/browse/AXIS2C-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera updated AXIS2C-743:
--

Fix Version/s: 1.2.0

 some return paths in axiom_data_handler_read_from() does not call fclose() on 
 the open file stream, in data_handler.c
 -

 Key: AXIS2C-743
 URL: https://issues.apache.org/jira/browse/AXIS2C-743
 Project: Axis2-C
  Issue Type: Bug
  Components: xml/om
 Environment: Ubuntu 7.10 (Gutsy Gibbon)
Reporter: Senaka Fernando
Assignee: Sanjaya Ratnaweera
Priority: Minor
 Fix For: 1.2.0


 in axis2/c/axiom/src/attachments/data_handler.c 
 axiom_data_handler_read_from() some return paths do not close the open file 
 stream.

-- 
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-741) axis2_any_content_type_add_value(...), in any_content_type.c always returns AXIS2_SUCCESS.


 [ 
https://issues.apache.org/jira/browse/AXIS2C-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera updated AXIS2C-741:
--

Fix Version/s: 1.2.0

 axis2_any_content_type_add_value(...), in any_content_type.c always returns 
 AXIS2_SUCCESS.
 --

 Key: AXIS2C-741
 URL: https://issues.apache.org/jira/browse/AXIS2C-741
 Project: Axis2-C
  Issue Type: Bug
  Components: core/addressing
 Environment: Ubuntu 7.10 (Gutsy Gibbon)
Reporter: Senaka Fernando
Assignee: Sanjaya Ratnaweera
 Fix For: 1.2.0

 Attachments: diff.txt


 AXIS2_EXTERN axis2_status_t AXIS2_CALL
 axis2_any_content_type_add_value(
 axis2_any_content_type_t * any_content_type,
 const axutil_env_t * env,
 const axutil_qname_t * qname,
 const axis2_char_t * value)
 In c/src/core/addr/any_content_type.c returns AXIS2_SUCCESS, irrespective of 
 a successful operation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: [Axis2] AXIS2_IS_SVR_SIDE property in configuration context

2007-11-14 Thread Damitha Kumarage


Samisa Abeysinghe wrote:

I see that AXIS2_IS_SVR_SIDE property  is being added to figure out 
whether we are on client side or server side.


However, I have doubts if this would work as expected always.

Say, you have already build a conf context on server side, and create 
a service client to consume another service using the same context, 
from within a service. Now form that service client instance, when you 
access the property, it would look like as if you are on server side, 
but actually you are invoking a client.




How are we supposed to deal with such a situation?


Yes the problem you said is there when we  use a conf_ctx created using 
build_conf_ctx function to create a service client. But if we restrict 
to use just axis2_svc_client_create() function then problem is solved 
:-\ . Can we do that?.  Is there any gain in using that function except 
the save of resources in creating a new conf_ctx?


Damitha





Samisa...

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





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

[jira] Updated: (AXIS2C-694) Memory leak occurs when inserting element to hash table


 [ 
https://issues.apache.org/jira/browse/AXIS2C-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dushshantha Chandradasa updated AXIS2C-694:
---

Fix Version/s: 1.2.0
Affects Version/s: (was: 1.1.0)
   Current (Nightly)

 Memory leak occurs when inserting element to hash table
 ---

 Key: AXIS2C-694
 URL: https://issues.apache.org/jira/browse/AXIS2C-694
 Project: Axis2-C
  Issue Type: Bug
  Components: util
Affects Versions: Current (Nightly)
 Environment: windows
Reporter: S.Uthaiyashankar
Assignee: Dushshantha Chandradasa
 Fix For: 1.2.0


 If an non null element is inserted to hash table when the hash table is full, 
 and the key is not available in the hash table, then memory leaks occur.  
 refer the following stack trace:
 axutil_allocator_malloc_impl 
 [d:\manjula\axis2\util\src\allocator.c:65]
 axutil_hash_find_entry [d:\manjula\axis2\util\src\hash.c:294]
 axutil_hash_set [d:\manjula\axis2\util\src\hash.c:362]
 rampart_set_security_processed_result 
 [d:\manjula\rampart\src\util\rampart_sec_processed_result.c:41]
 rampart_shp_process_encrypted_key 
 [d:\manjula\rampart\src\util\rampart_sec_header_processor.c:558]
 rampart_shp_process_message 
 [d:\manjula\rampart\src\util\rampart_sec_header_processor.c:1135]
 rampart_in_handler_invoke 
 [d:\manjula\rampart\src\handlers\rampart_in_handler.c:138]
 axis2_handler_invoke 
 [d:\manjula\axis2\src\core\engine\handler.c:91]
 axis2_phase_invoke [d:\manjula\axis2\src\core\engine\phase.c:199]

-- 
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-699) Even thought the image is missing inside the resources folder, the mtom samples displays success message


 [ 
https://issues.apache.org/jira/browse/AXIS2C-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera updated AXIS2C-699:
--

Fix Version/s: 1.2.0

 Even thought the image is missing inside the resources folder, the mtom 
 samples displays success message
 

 Key: AXIS2C-699
 URL: https://issues.apache.org/jira/browse/AXIS2C-699
 Project: Axis2-C
  Issue Type: Bug
  Components: platforms/windows
Affects Versions: 1.1.0
 Environment: Windows XP, libxml2-2.6.27.win32
Reporter: Evanthika Amarasiri
Assignee: Sanjaya Ratnaweera
Priority: Minor
 Fix For: 1.2.0


 1. Assume that the axis2.jpeg is missing in the folder 
 axis2c\bin\samples\resources
 2. Execute the mtom sample
 3. The client does not fail and it creates a blank image at the server side
 This is invalid. If the image is missing, the client should fail

-- 
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-699) Even thought the image is missing inside the resources folder, the mtom samples displays success message


 [ 
https://issues.apache.org/jira/browse/AXIS2C-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera reassigned AXIS2C-699:
-

Assignee: Sanjaya Ratnaweera

 Even thought the image is missing inside the resources folder, the mtom 
 samples displays success message
 

 Key: AXIS2C-699
 URL: https://issues.apache.org/jira/browse/AXIS2C-699
 Project: Axis2-C
  Issue Type: Bug
  Components: platforms/windows
Affects Versions: 1.1.0
 Environment: Windows XP, libxml2-2.6.27.win32
Reporter: Evanthika Amarasiri
Assignee: Sanjaya Ratnaweera
Priority: Minor
 Fix For: 1.2.0


 1. Assume that the axis2.jpeg is missing in the folder 
 axis2c\bin\samples\resources
 2. Execute the mtom sample
 3. The client does not fail and it creates a blank image at the server side
 This is invalid. If the image is missing, the client should fail

-- 
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-700) The INSTALL file states about a conf folder which does not exist in the binary distribution


 [ 
https://issues.apache.org/jira/browse/AXIS2C-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera reassigned AXIS2C-700:
-

Assignee: Sanjaya Ratnaweera

 The INSTALL file states about a conf folder which does not exist in the 
 binary distribution
 ---

 Key: AXIS2C-700
 URL: https://issues.apache.org/jira/browse/AXIS2C-700
 Project: Axis2-C
  Issue Type: Bug
  Components: documentation
Affects Versions: 1.1.0
 Environment: Windows XP
Reporter: Evanthika Amarasiri
Assignee: Sanjaya Ratnaweera
Priority: Trivial
 Fix For: 1.2.0


 In the INSTALL file of the binary distribution, it mentions about a conf 
 folder which should be included in the axis2c folder structure.
 Such folder does not exist in the binary distribution, therefore the INSTALL 
 file should be updated

-- 
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-700) The INSTALL file states about a conf folder which does not exist in the binary distribution


 [ 
https://issues.apache.org/jira/browse/AXIS2C-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera updated AXIS2C-700:
--

Fix Version/s: 1.2.0

 The INSTALL file states about a conf folder which does not exist in the 
 binary distribution
 ---

 Key: AXIS2C-700
 URL: https://issues.apache.org/jira/browse/AXIS2C-700
 Project: Axis2-C
  Issue Type: Bug
  Components: documentation
Affects Versions: 1.1.0
 Environment: Windows XP
Reporter: Evanthika Amarasiri
Assignee: Sanjaya Ratnaweera
Priority: Trivial
 Fix For: 1.2.0


 In the INSTALL file of the binary distribution, it mentions about a conf 
 folder which should be included in the axis2c folder structure.
 Such folder does not exist in the binary distribution, therefore the INSTALL 
 file should be updated

-- 
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-721) Requesting step-by-step guides


 [ 
https://issues.apache.org/jira/browse/AXIS2C-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dushshantha Chandradasa updated AXIS2C-721:
---

Fix Version/s: 1.2.0

 Requesting step-by-step guides
 --

 Key: AXIS2C-721
 URL: https://issues.apache.org/jira/browse/AXIS2C-721
 Project: Axis2-C
  Issue Type: Wish
  Components: documentation
Reporter: Senaka Fernando
Assignee: Dushshantha Chandradasa
 Fix For: 1.2.0


 It would be great if someone could create a step-by-step guide in creating a 
 service and a client, instead of just adding an example in the manual. What I 
 mean is an example which is gradually built from the most basic step into a 
 really advanced implimentation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: [Axis2] AXIS2_IS_SVR_SIDE property in configuration context


Damitha Kumarage wrote:

Samisa Abeysinghe wrote:

I see that AXIS2_IS_SVR_SIDE property  is being added to figure out 
whether we are on client side or server side.


However, I have doubts if this would work as expected always.

Say, you have already build a conf context on server side, and create 
a service client to consume another service using the same context, 
from within a service. Now form that service client instance, when 
you access the property, it would look like as if you are on server 
side, but actually you are invoking a client.




How are we supposed to deal with such a situation?


Yes the problem you said is there when we  use a conf_ctx created 
using build_conf_ctx function to create a service client. But if we 
restrict to use just axis2_svc_client_create() function then problem 
is solved :-\ . Can we do that?.  Is there any gain in using that 
function except the save of resources in creating a new conf_ctx?
There are advantages of using the current conf context. Resource 
utilization is one. Also, there may b situations where you want to 
communicate the session info etc. through the shared context.


I understand that this property would be used in case of Sandesha. How 
does the Java guys do this? Also, is the client db structure different 
form the server db structure?



Samisa...


Damitha





Samisa...

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





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






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

[Axis2] Ready To Release 1.2.0?

2007-11-14 Thread Damitha Kumarage


Hi Devs,
We have some major improvements that is worth releasing:
  - Improved Code Generation
  - Improved Policy
  - Improvements to thread environment
  - Improvements to error handling
  - Lot of bug fixes

  If we agree on 1.2.0, I could volunteer to be the release manager.
Damitha


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

Re: [Axis2] Ready To Release 1.2.0?


Damitha Kumarage wrote:

Hi Devs,
We have some major improvements that is worth releasing:
  - Improved Code Generation
  - Improved Policy
  - Improvements to thread environment
  - Improvements to error handling
  - Lot of bug fixes


Yes I think it would be good to do a release before the end of this 
year. We have come a long way since 1.1.




  If we agree on 1.2.0, I could volunteer to be the release manager.


Excellent. I would call a vote proposing you as RM.

Samisa...


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

[Vote] [Axis2] Damitha as Release Manager for Apache Axis2/C 1.2.0 Release


Hi All,
  I would like to propose Damitha as the release manager for Apache 
Axis2/C 1.2.0 release.
  Damitha, a WS PMC as well as an active committer for Apache Axis2/C, 
has expressed his willingness to be the release manager for Apache 
Axis2/C 1.2.0 and I would like to welcome him for this role.


  Here is my +1.


Thanks,
Samisa...

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

Re: [Axis2] AXIS2_IS_SVR_SIDE property in configuration context

2007-11-14 Thread Damitha Kumarage


Samisa Abeysinghe wrote:


Damitha Kumarage wrote:


Samisa Abeysinghe wrote:

I see that AXIS2_IS_SVR_SIDE property  is being added to figure out 
whether we are on client side or server side.


However, I have doubts if this would work as expected always.

Say, you have already build a conf context on server side, and 
create a service client to consume another service using the same 
context, from within a service. Now form that service client 
instance, when you access the property, it would look like as if you 
are on server side, but actually you are invoking a client.





How are we supposed to deal with such a situation?



Yes the problem you said is there when we  use a conf_ctx created 
using build_conf_ctx function to create a service client. But if we 
restrict to use just axis2_svc_client_create() function then problem 
is solved :-\ . Can we do that?.  Is there any gain in using that 
function except the save of resources in creating a new conf_ctx?


There are advantages of using the current conf context. Resource 
utilization is one. Also, there may b situations where you want to 
communicate the session info etc. through the shared context.


I understand that this property would be used in case of Sandesha. How 
does the Java guys do this? 


Java guys don't need to worry about these things as they use hibernate.


Also, is the client db structure different form the server db structure?


server and client database structures are not different. But if we use 
server and client database same then there occurs file locking in 
sqlite. As I remember there is no problem with mysql when using same 
database for sever and client.

Damitha




Samisa...



Damitha





Samisa...

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





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






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






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

Re: [Vote] [Axis2] Damitha as Release Manager for Apache Axis2/C 1.2.0 Release

2007-11-14 Thread senaka

 Hi All,
I would like to propose Damitha as the release manager for Apache
 Axis2/C 1.2.0 release.
Damitha, a WS PMC as well as an active committer for Apache Axis2/C,
 has expressed his willingness to be the release manager for Apache
 Axis2/C 1.2.0 and I would like to welcome him for this role.

Here is my +1.

Here is my +1.

Regards,
Senaka



 Thanks,
 Samisa...

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




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

Re: [Vote] [Axis2] Damitha as Release Manager for Apache Axis2/C 1.2.0 Release

2007-11-14 Thread Nadir Amra

+1

Nadir K. Amra


Samisa Abeysinghe [EMAIL PROTECTED] wrote on 11/14/2007 09:58:50 AM:

 Hi All,
I would like to propose Damitha as the release manager for Apache 
 Axis2/C 1.2.0 release.
Damitha, a WS PMC as well as an active committer for Apache Axis2/C, 
 has expressed his willingness to be the release manager for Apache 
 Axis2/C 1.2.0 and I would like to welcome him for this role.
 
Here is my +1.
 
 
 Thanks,
 Samisa...
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


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

Re: [Vote] [Axis2] Damitha as Release Manager for Apache Axis2/C 1.2.0 Release

2007-11-14 Thread Manjula Peiris

+1

-Manjula.


On Wed, 2007-11-14 at 11:54 -0600, Nadir Amra wrote:
 +1
 
 Nadir K. Amra
 
 
 Samisa Abeysinghe [EMAIL PROTECTED] wrote on 11/14/2007 09:58:50 AM:
 
  Hi All,
 I would like to propose Damitha as the release manager for Apache 
  Axis2/C 1.2.0 release.
 Damitha, a WS PMC as well as an active committer for Apache Axis2/C, 
  has expressed his willingness to be the release manager for Apache 
  Axis2/C 1.2.0 and I would like to welcome him for this role.
  
 Here is my +1.
  
  
  Thanks,
  Samisa...
  
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
  
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


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

Re: [Vote] [Axis2] Damitha as Release Manager for Apache Axis2/C 1.2.0 Release

2007-11-14 Thread Dushshantha Chadradasa


Here's my +1

regards,
Dushshantha

Manjula Peiris wrote:

+1

-Manjula.


On Wed, 2007-11-14 at 11:54 -0600, Nadir Amra wrote:
  

+1

Nadir K. Amra


Samisa Abeysinghe [EMAIL PROTECTED] wrote on 11/14/2007 09:58:50 AM:



Hi All,
   I would like to propose Damitha as the release manager for Apache 
Axis2/C 1.2.0 release.
   Damitha, a WS PMC as well as an active committer for Apache Axis2/C, 
has expressed his willingness to be the release manager for Apache 
Axis2/C 1.2.0 and I would like to welcome him for this role.


   Here is my +1.


Thanks,
Samisa...

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

  

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





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


  



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

Re: [Vote] [Axis2] Damitha as Release Manager for Apache Axis2/C 1.2.0 Release

2007-11-14 Thread Milinda Pathirage

+1

Milinda..

On Nov 15, 2007 8:42 AM, Dushshantha Chadradasa 
[EMAIL PROTECTED] wrote:

 Here's my +1

 regards,
 Dushshantha

 Manjula Peiris wrote:
  +1
 
  -Manjula.
 
 
  On Wed, 2007-11-14 at 11:54 -0600, Nadir Amra wrote:
 
  +1
 
  Nadir K. Amra
 
 
  Samisa Abeysinghe [EMAIL PROTECTED] wrote on 11/14/2007 09:58:50 AM:
 
 
  Hi All,
 I would like to propose Damitha as the release manager for Apache
  Axis2/C 1.2.0 release.
 Damitha, a WS PMC as well as an active committer for Apache
 Axis2/C,
  has expressed his willingness to be the release manager for Apache
  Axis2/C 1.2.0 and I would like to welcome him for this role.
 
 Here is my +1.
 
 
  Thanks,
  Samisa...
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 


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




-- 
http://think2ed.blogspot.com thinksquared
http://wsaxc.blogspot.com Web Services With Axis2/C

Re: [Vote] [Axis2] Damitha as Release Manager for Apache Axis2/C 1.2.0 Release

2007-11-14 Thread Dinesh Premalal

+1

-- 
Dinesh Premalal
http://xydinesh.wordpress.com

[jira] Updated: (AXIS2C-735) bug in fuction axis2_http_svr_thread_is_running() in src/core/transport/http/receiver/http_svr_thread.c


 [ 
https://issues.apache.org/jira/browse/AXIS2C-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dinesh Premalal updated AXIS2C-735:
---

Fix Version/s: 1.2.0

 bug in fuction axis2_http_svr_thread_is_running() in 
 src/core/transport/http/receiver/http_svr_thread.c
 ---

 Key: AXIS2C-735
 URL: https://issues.apache.org/jira/browse/AXIS2C-735
 Project: Axis2-C
  Issue Type: Bug
  Components: transport/http
Affects Versions: Current (Nightly)
 Environment: Gnu/Linux 
Reporter: Rajika Kumarasiri
Assignee: Dinesh Premalal
Priority: Minor
 Fix For: 1.2.0

 Attachments: diff.txt, http_svr_thread.patch


 The function is to check weather the sever thread is running. But it returns 
 the port. 
 I think it should be correct as  return svr_thread-stopped;
 in /core/transport/http/receiver/http_svr_thread.c, line 198 to be returned 
 the check for weather the server thread is running. 

-- 
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-735) bug in fuction axis2_http_svr_thread_is_running() in src/core/transport/http/receiver/http_svr_thread.c


 [ 
https://issues.apache.org/jira/browse/AXIS2C-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dinesh Premalal reassigned AXIS2C-735:
--

Assignee: Dinesh Premalal

 bug in fuction axis2_http_svr_thread_is_running() in 
 src/core/transport/http/receiver/http_svr_thread.c
 ---

 Key: AXIS2C-735
 URL: https://issues.apache.org/jira/browse/AXIS2C-735
 Project: Axis2-C
  Issue Type: Bug
  Components: transport/http
Affects Versions: Current (Nightly)
 Environment: Gnu/Linux 
Reporter: Rajika Kumarasiri
Assignee: Dinesh Premalal
Priority: Minor
 Fix For: 1.2.0

 Attachments: diff.txt, http_svr_thread.patch


 The function is to check weather the sever thread is running. But it returns 
 the port. 
 I think it should be correct as  return svr_thread-stopped;
 in /core/transport/http/receiver/http_svr_thread.c, line 198 to be returned 
 the check for weather the server thread is running. 

-- 
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-729) Code Formatting in Guththila and data type formatting


 [ 
https://issues.apache.org/jira/browse/AXIS2C-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dinesh Premalal updated AXIS2C-729:
---

Fix Version/s: (was: Current (Nightly))
   1.2.0

 Code Formatting in Guththila and data type formatting
 -

 Key: AXIS2C-729
 URL: https://issues.apache.org/jira/browse/AXIS2C-729
 Project: Axis2-C
  Issue Type: Improvement
  Components: build system (Unix/Linux)
Affects Versions: Current (Nightly)
 Environment: Unix
Reporter: Lahiru Gunathilake
Assignee: Dinesh Premalal
Priority: Minor
 Fix For: 1.2.0

 Attachments: guththila_formattings, svn_diff


 There are some unformatted codings in Guththila Parser code and some other 
 data type formating are not there.
 As an example in guththila.h file data type, char is defined as 
 guththila_chat_t but most of the places it doesn't use that defined data type 
 but used char again.And there are some other unformatted codings in all the 
 header files and source files.  

-- 
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-727) Performace Testing with Guththila Parser


 [ 
https://issues.apache.org/jira/browse/AXIS2C-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dinesh Premalal reassigned AXIS2C-727:
--

Assignee: Dinesh Premalal

 Performace Testing with Guththila Parser
 

 Key: AXIS2C-727
 URL: https://issues.apache.org/jira/browse/AXIS2C-727
 Project: Axis2-C
  Issue Type: Bug
  Components: guththila
Affects Versions: Current (Nightly)
 Environment: Ubuntu
Reporter: Lahiru Gunathilake
Assignee: Dinesh Premalal
 Fix For: 1.2.0


 While Testing Perfomance of Guththila Parser and Libxml2 Response soap 
 message I got are different.There's a difference other than the Additional 
 Namespace Problem as I raised last time there's small different with two soap 
 messages.
 With Guththila Parser  this is the soap message body starts like this 
 soapenv:Body xmlns:soapenv = http://www.w3.org/2003/05/soap-envelope;
 In this line there are two additional spaces before the equal sign and just 
 after the equal sign.But with Libxml2 there's no additional spaces.
 Then there'll be more data transferring with Guththila Parser.
 But with Libxml2 there's no any line like previous once since that namespace 
 is included as a Soap Header
 Regs
 lahiru

-- 
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-726) Issue In Guththila Parser


 [ 
https://issues.apache.org/jira/browse/AXIS2C-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dinesh Premalal reassigned AXIS2C-726:
--

Assignee: Dinesh Premalal

 Issue In Guththila Parser
 -

 Key: AXIS2C-726
 URL: https://issues.apache.org/jira/browse/AXIS2C-726
 Project: Axis2-C
  Issue Type: Bug
  Components: guththila
Affects Versions: Current (Nightly)
 Environment: Ubuntu
Reporter: Lahiru Gunathilake
Assignee: Dinesh Premalal
Priority: Minor
 Attachments: diff.txt


 I did some performance testings using apache benchmark by using Libxml2 and 
 Guththila Parser with the the math sample which ships with apache 
 Axis2c.Response of the math service with Guththila parser is slightly 
 different to the response with Libxml2.With Guththila parser it add  
 Namespace  http://www.w3.org/2003/05/soap-envelope; in to soap header and 
 soap body as well. Then the document size is different when using two  XML 
 parsers.Here are the two soap response soap messages got with two XML parsers.
 -- with Guththila Parser 
 ---
 soapenv:Envelope xmlns:soapenv = 
 http://www.w3.org/2003/05/soap-envelope;soapenv:Header/soapenv:Headersoapenv:Body
  xmlns:soapenv = http://www.w3.org/2003/05/soap-envelope;ns1:result 
 xmlns:ns1 = 
 http://axis2/test/namespace1;18/ns1:result/soapenv:Body/soapenv:Envelope
 ---
 --with Libxml2 
 Parser--
 soapenv:Envelope 
 xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;soapenv:Header/soapenv:Bodyns1:result
  
 xmlns:ns1=http://axis2/test/namespace1;18/ns1:result/soapenv:Body/soapenv:Envelope
 -
 This is probably cause to reduce the speed of Guththila parser since it send 
 nearly 78 more bytes of data in the response message with a simple service 
 like math.But with more data still the Guththila Parser is much faster than 
 with Libxml2.

-- 
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-729) Code Formatting in Guththila and data type formatting


 [ 
https://issues.apache.org/jira/browse/AXIS2C-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dinesh Premalal reassigned AXIS2C-729:
--

Assignee: Dinesh Premalal

 Code Formatting in Guththila and data type formatting
 -

 Key: AXIS2C-729
 URL: https://issues.apache.org/jira/browse/AXIS2C-729
 Project: Axis2-C
  Issue Type: Improvement
  Components: build system (Unix/Linux)
Affects Versions: Current (Nightly)
 Environment: Unix
Reporter: Lahiru Gunathilake
Assignee: Dinesh Premalal
Priority: Minor
 Fix For: 1.2.0

 Attachments: guththila_formattings, svn_diff


 There are some unformatted codings in Guththila Parser code and some other 
 data type formating are not there.
 As an example in guththila.h file data type, char is defined as 
 guththila_chat_t but most of the places it doesn't use that defined data type 
 but used char again.And there are some other unformatted codings in all the 
 header files and source files.  

-- 
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-715) SOAP faults not always detected by Axis2/C client


 [ 
https://issues.apache.org/jira/browse/AXIS2C-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dinesh Premalal reassigned AXIS2C-715:
--

Assignee: Dinesh Premalal

 SOAP faults not always detected by Axis2/C client
 -

 Key: AXIS2C-715
 URL: https://issues.apache.org/jira/browse/AXIS2C-715
 Project: Axis2-C
  Issue Type: Bug
  Components: core/clientapi, core/receivers, xml/soap
Affects Versions: 1.0.0, 1.1.0
 Environment: SOAP client based on Axis2/C 1.0.0 (couldn't test 1.1.0 
 client yet) and different SOAP servers
Reporter: Stefano Pettini
Assignee: Dinesh Premalal
 Fix For: 1.2.0


 The first SOAP fault is detected by 
 axis2_svc_client_get_last_response_has_fault. The second is not.
 1) Here is an HTTP conversation between a SOAP client based on Axis2/C 1.0.0 
 and a SOAP server based on J2EE JAX-WS default SOAP implementation over 
 Tomcat over Apache. SOAP fault IS detected:
 Sent:
 POST /WebServiceTest/MMMC_Service HTTP/1.1
 User-Agent: Axis2/C
 SOAPAction: 
 Content-Length: 166
 Content-Type: text/xml;charset=UTF-8
 Host: 10.3.4.169:8084
 soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
 soapenv:Header/soapenv:Header
 soapenv:Body
 hi/hi
 /soapenv:Body
 /soapenv:Envelope
 Received:
 HTTP/1.1 500 Internal Server Error
 Server: Apache-Coyote/1.1
 Content-Type: text/xml;charset=utf-8
 Transfer-Encoding: chunked
 Date: Thu, 04 Oct 2007 09:05:36 GMT
 Connection: close
 18a
 ?xml version=1.0 ?
 S:Envelope xmlns:S=http://schemas.xmlsoap.org/soap/envelope/;
 S:Body
 ns2:Fault xmlns:ns2=http://schemas.xmlsoap.org/soap/envelope/; 
 xmlns:ns3=http://www.w3.org/2003/05/soap-envelope;
 faultcodens2:Client/faultcode
 faultstringCannot find dispatch method for {null}hi using quot;Payload 
 QName-based Dispatcherquot;/faultstring
 /ns2:Fault
 /S:Body
 /S:Envelope
 0
 2) Here is an HTTP conversation between a SOAP client based on Axis2/C 1.0.0 
 and a SOAP server based on Axis2/C 1.1.0 over Apache. SOAP fault IS NOT 
 detected:
 Sent:
 POST /ws/services/mmmc HTTP/1.1
 User-Agent: Axis2/C
 SOAPAction: 
 Content-Length: 166
 Content-Type: text/xml;charset=UTF-8
 Host: 10.3.1.198:80
 soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
 soapenv:Header/soapenv:Header
 soapenv:Bodyhi/hi/soapenv:Body
 /soapenv:Envelope
 Received:
 HTTP/1.1 500 Internal Server Error
 Date: Tue, 27 Mar 2007 17:30:35 GMT
 Server: Apache/2.0.52 (Red Hat)
 Content-Length: 255
 Connection: close
 Content-Type: text/xml
 soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
 soapenv:Header/
 soapenv:Body
 soapenv:Fault
 faultcodesoapenv:Server/faultcode
 faultstringOperation Not Found/faultstring
 /soapenv:Fault
 /soapenv:Body
 /soapenv:Envelope

-- 
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-726) Issue In Guththila Parser


 [ 
https://issues.apache.org/jira/browse/AXIS2C-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dinesh Premalal updated AXIS2C-726:
---

Fix Version/s: 1.2.0

 Issue In Guththila Parser
 -

 Key: AXIS2C-726
 URL: https://issues.apache.org/jira/browse/AXIS2C-726
 Project: Axis2-C
  Issue Type: Bug
  Components: guththila
Affects Versions: Current (Nightly)
 Environment: Ubuntu
Reporter: Lahiru Gunathilake
Assignee: Dinesh Premalal
Priority: Minor
 Fix For: 1.2.0

 Attachments: diff.txt


 I did some performance testings using apache benchmark by using Libxml2 and 
 Guththila Parser with the the math sample which ships with apache 
 Axis2c.Response of the math service with Guththila parser is slightly 
 different to the response with Libxml2.With Guththila parser it add  
 Namespace  http://www.w3.org/2003/05/soap-envelope; in to soap header and 
 soap body as well. Then the document size is different when using two  XML 
 parsers.Here are the two soap response soap messages got with two XML parsers.
 -- with Guththila Parser 
 ---
 soapenv:Envelope xmlns:soapenv = 
 http://www.w3.org/2003/05/soap-envelope;soapenv:Header/soapenv:Headersoapenv:Body
  xmlns:soapenv = http://www.w3.org/2003/05/soap-envelope;ns1:result 
 xmlns:ns1 = 
 http://axis2/test/namespace1;18/ns1:result/soapenv:Body/soapenv:Envelope
 ---
 --with Libxml2 
 Parser--
 soapenv:Envelope 
 xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope;soapenv:Header/soapenv:Bodyns1:result
  
 xmlns:ns1=http://axis2/test/namespace1;18/ns1:result/soapenv:Body/soapenv:Envelope
 -
 This is probably cause to reduce the speed of Guththila parser since it send 
 nearly 78 more bytes of data in the response message with a simple service 
 like math.But with more data still the Guththila Parser is much faster than 
 with Libxml2.

-- 
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-717) Unhandled Exception when using Gnuthilla


 [ 
https://issues.apache.org/jira/browse/AXIS2C-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dinesh Premalal reassigned AXIS2C-717:
--

Assignee: Dinesh Premalal

 Unhandled Exception when using Gnuthilla
 

 Key: AXIS2C-717
 URL: https://issues.apache.org/jira/browse/AXIS2C-717
 Project: Axis2-C
  Issue Type: Bug
  Components: guththila, platforms/windows
Affects Versions: 1.1.0
 Environment: Windows XP Professional SP2
 Apache 2.2.4 server with Axis2c 1.1.0 module
 - Remote stress test client script hosted by Fedora Core 7
Reporter: David Klassen
Assignee: Dinesh Premalal
 Fix For: 1.2.0


 I wanted to stress test axis2c deployed on apache, to see if using this SOAP 
 implementation would be reliable. Simulating 25 concurrent users (with a 
 shell script) making one request per second by using the 'echo' sample 
 program (recompiled to target the server from a remote machine[Linux]). With 
 Gnuthilla compiled-in axutil.dll suffered an Unhandled Exception 
 (repeatably). While Gnuthilla did suffer less memory consumption, when the 
 httpd.exe memory consumption reached around 77 MB the exception was 
 triggered. 
 Here is what my VS 2005 debug session provided me:
  non-debug modules excluded 
 'httpd.exe': Loaded 'C:\cygwin\thirdparty\axis2c\lib\axis2_http_sender.dll', 
 Symbols loaded.
 'httpd.exe': Loaded 
 'C:\cygwin\thirdparty\axis2c\lib\axis2_http_receiver.dll', Symbols loaded.
 'httpd.exe': Loaded 
 'C:\cygwin\thirdparty\axis2c\modules\addressing\axis2_mod_addr.dll', Symbols 
 loaded.
 'httpd.exe': Loaded 
 'C:\cygwin\thirdparty\axis2c\modules\logging\axis2_mod_log.dll', Symbols 
 loaded.
 'httpd.exe': Loaded 'C:\cygwin\thirdparty\axis2c\services\echo\echo.dll', 
 Symbols loaded.
 The thread 'Win32 Thread' (0x640) has exited with code 0 (0x0).
 Unhandled exception at 0x00ed10df (axutil.dll) in httpd.exe: 0xC005: 
 Access violation reading location 0x0001.
 Even though I compiled with symbols when I chose to break the following 
 assembly data was displayed:
 [EMAIL PROTECTED]:
 00ED10D0 56   pushesi  
 00ED10D1 8B 74 24 08  mov esi,dword ptr [esp+8] 
 00ED10D5 85 F6testesi,esi 
 00ED10D7 75 06jne [EMAIL PROTECTED] (0ED10DFh) 
 00ED10D9 33 C0xor eax,eax 
 00ED10DB 5E   pop esi  
 00ED10DC C2 04 00 ret 4
 00ED10DF 83 3E 00 cmp dword ptr [esi],0   
 --- location of debug session
 00ED10E2 57   pushedi  
 00ED10E3 8B 7E 20 mov edi,dword ptr [esi+20h] 
 00ED10E6 75 1Bjne [EMAIL PROTECTED] (0ED1103h) 
 00ED10E8 8D 46 08 lea eax,[esi+8] 
 00ED10EB 50   pusheax  
 00ED10EC FF 15 30 94 F1 00 calldword ptr [EMAIL PROTECTED] 
 (0F19430h)] 
 00ED10F2 8B 57 08 mov edx,dword ptr [edi+8] 
 00ED10F5 56   pushesi  
 00ED10F6 57   pushedi  
 00ED10F7 FF D2calledx  
 00ED10F9 5F   pop edi  
 00ED10FA B8 01 00 00 00   mov eax,1 
 00ED10FF 5E   pop esi  
 00ED1100 C2 04 00 ret 4
 00ED1103 8B 4E 04 mov ecx,dword ptr [esi+4] 
 00ED1106 51   pushecx  
 00ED1107 FF 15 0C 94 F1 00 calldword ptr [EMAIL PROTECTED] 
 (0F1940Ch)] 
 00ED110D 85 C0testeax,eax 
 00ED110F 75 E1jne [EMAIL PROTECTED] (0ED10F2h) 
 Seeing that this is a thread, I cannot be sure if the error was triggered by 
 apache or something else. I guess this might be something apache specific? It 
 is interesting to note however that this happens consistently with gnuthilla, 
 whereas without it a crash does not always occur (ie. Only some of the time). 
 Without gnuthilla the httpd.exe process sometimes reaches 200 MB or more 
 without crashing. Still trying to figure out what causes the net memory 
 consumption, since even when the 25 clients are stopped the httpd.exe memory 
 size does not decrease.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Re: [Vote] [Axis2] Damitha as Release Manager for Apache Axis2/C 1.2.0 Release

2007-11-14 Thread Kaushalye Kapuruge



+1
-Kaushalye

Samisa Abeysinghe wrote:

Hi All,
  I would like to propose Damitha as the release manager for Apache 
Axis2/C 1.2.0 release.
  Damitha, a WS PMC as well as an active committer for Apache Axis2/C, 
has expressed his willingness to be the release manager for Apache 
Axis2/C 1.2.0 and I would like to welcome him for this role.


  Here is my +1.


Thanks,
Samisa...

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





--
http://blog.kaushalye.org/
http://wso2.org/


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

Re: [Vote] [Axis2] Damitha as Release Manager for Apache Axis2/C 1.2.0 Release

2007-11-14 Thread Nandika Jayawardana

+1

- Nandika

On Nov 15, 2007 10:18 AM, Kaushalye Kapuruge [EMAIL PROTECTED] wrote:

 +1
 -Kaushalye


 Samisa Abeysinghe wrote:
  Hi All,
I would like to propose Damitha as the release manager for Apache
  Axis2/C 1.2.0 release.
Damitha, a WS PMC as well as an active committer for Apache Axis2/C,
  has expressed his willingness to be the release manager for Apache
  Axis2/C 1.2.0 and I would like to welcome him for this role.
 
Here is my +1.
 
 
  Thanks,
  Samisa...
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 


 --
 http://blog.kaushalye.org/
 http://wso2.org/



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





-- 
http://nandikajayawardana.blogspot.com/
WSO2 Inc: http://www.wso2.com

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

Re: [Vote] [Axis2] Damitha as Release Manager for Apache Axis2/C 1.2.0 Release

2007-11-14 Thread Dimuthu Gamage

+1

Dimuthu

On Nov 15, 2007 10:18 AM, Kaushalye Kapuruge [EMAIL PROTECTED] wrote:


 +1
 -Kaushalye

 Samisa Abeysinghe wrote:
  Hi All,
I would like to propose Damitha as the release manager for Apache
  Axis2/C 1.2.0 release.
Damitha, a WS PMC as well as an active committer for Apache Axis2/C,
  has expressed his willingness to be the release manager for Apache
  Axis2/C 1.2.0 and I would like to welcome him for this role.
 
Here is my +1.
 
 
  Thanks,
  Samisa...
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 


 --
 http://blog.kaushalye.org/
 http://wso2.org/


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

Re: [Vote] [Axis2] Damitha as Release Manager for Apache Axis2/C 1.2.0 Release

2007-11-14 Thread Sanjaya Ratnaweera


+1

   ~sanjaya

Dimuthu Gamage wrote:

+1

Dimuthu

On Nov 15, 2007 10:18 AM, Kaushalye Kapuruge [EMAIL PROTECTED] 
mailto:[EMAIL PROTECTED] wrote:



+1
-Kaushalye

Samisa Abeysinghe wrote:
 Hi All,
   I would like to propose Damitha as the release manager for Apache
 Axis2/C 1.2.0 release.
   Damitha, a WS PMC as well as an active committer for Apache
Axis2/C,
 has expressed his willingness to be the release manager for Apache
 Axis2/C 1.2.0 and I would like to welcome him for this role.

   Here is my +1.


 Thanks,
 Samisa...


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




--
http://blog.kaushalye.org/ http://blog.kaushalye.org/
http://wso2.org/


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

[jira] Created: (AXIS2C-766) Sample using specific error blocks

Sample using specific error blocks
--

 Key: AXIS2C-766
 URL: https://issues.apache.org/jira/browse/AXIS2C-766
 Project: Axis2-C
  Issue Type: Improvement
  Components: util
Affects Versions: 1.1.0
Reporter: Dinesh Premalal
Assignee: Dinesh Premalal
Priority: Minor
 Fix For: Current (Nightly)


Sample on How to use predefined error bocks. User can easily defined own error 
set.

-- 
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-766) Sample using specific error blocks


 [ 
https://issues.apache.org/jira/browse/AXIS2C-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dinesh Premalal updated AXIS2C-766:
---

Attachment: echo.tar.gz

Modfied echo service using , pre-defined error blocks.

 Sample using specific error blocks
 --

 Key: AXIS2C-766
 URL: https://issues.apache.org/jira/browse/AXIS2C-766
 Project: Axis2-C
  Issue Type: Improvement
  Components: util
Affects Versions: 1.1.0
Reporter: Dinesh Premalal
Assignee: Dinesh Premalal
Priority: Minor
 Fix For: Current (Nightly)

 Attachments: echo.tar.gz


 Sample on How to use predefined error bocks. User can easily defined own 
 error set.

-- 
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-700) The INSTALL file states about a conf folder which does not exist in the binary distribution


 [ 
https://issues.apache.org/jira/browse/AXIS2C-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera resolved AXIS2C-700.
---

Resolution: Fixed

Fixed in current SVN

 The INSTALL file states about a conf folder which does not exist in the 
 binary distribution
 ---

 Key: AXIS2C-700
 URL: https://issues.apache.org/jira/browse/AXIS2C-700
 Project: Axis2-C
  Issue Type: Bug
  Components: documentation
Affects Versions: 1.1.0
 Environment: Windows XP
Reporter: Evanthika Amarasiri
Assignee: Sanjaya Ratnaweera
Priority: Trivial
 Fix For: 1.2.0


 In the INSTALL file of the binary distribution, it mentions about a conf 
 folder which should be included in the axis2c folder structure.
 Such folder does not exist in the binary distribution, therefore the INSTALL 
 file should be updated

-- 
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-707) broken link in axis2/c manual


 [ 
https://issues.apache.org/jira/browse/AXIS2C-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjaya Ratnaweera resolved AXIS2C-707.
---

Resolution: Fixed

Fixed in current svn

 broken link in axis2/c manual
 -

 Key: AXIS2C-707
 URL: https://issues.apache.org/jira/browse/AXIS2C-707
 Project: Axis2-C
  Issue Type: Bug
  Components: documentation
 Environment: webpage
Reporter: Ryan Jarvis
Assignee: Sanjaya Ratnaweera
Priority: Minor
 Fix For: 1.2.0


 The link to the hello_svc.c file displayed in the 1.1 Hello Service section 
 is not valid.  Link should take user to appropriate file.

-- 
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-760) To build the samples section of the Apache Axis2/C Installation Guide should be modified to include correct configuration command.