[jira] Assigned: (AXIS2C-1183) TCPMon tool segfaults if the listen port or the target port is not specified

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake reassigned AXIS2C-1183:
--

Assignee: Lahiru Gunathilake

> TCPMon tool segfaults if the listen port or the target port is not specified
> 
>
> Key: AXIS2C-1183
> URL: https://issues.apache.org/jira/browse/AXIS2C-1183
> Project: Axis2-C
>  Issue Type: Bug
>  Components: tcpmon
>Affects Versions: Current (Nightly)
> Environment: Windows XP
>Reporter: S.Uthaiyashankar
>Assignee: Lahiru Gunathilake
>
> 1. Tried to start the TCPMon tool without specifying the target port or the 
> listen port as below
> E.g.:- 
> a) tcpmon.exe -tp 9091 -lp
> b) tcpmon.exe -tp
> 2. A segfault was occurred

-- 
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-1126) Build Breaks when Libxml2-dev isn't install

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-1126.
--

Resolution: Fixed

> Build Breaks when Libxml2-dev isn't install
> ---
>
> Key: AXIS2C-1126
> URL: https://issues.apache.org/jira/browse/AXIS2C-1126
> Project: Axis2-C
>  Issue Type: Bug
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 8.04
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
>
> I tried to build Axis2C by running build.sh and I haven't install libxml2-dev 
> in my machine since I tried to work with guththila.
> But in neethi/test build breaks by telling a problem with -lxml2. After 
> installing libxml2-dev Axis2C build breaks.
> I think this should be changed since guththila parser is the default parser. 
> 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] Commented: (AXIS2C-1126) Build Breaks when Libxml2-dev isn't install

[Lahiru Gunathilake (JIRA)]

[ 
https://issues.apache.org/jira/browse/AXIS2C-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593742#action_12593742
 ] 

Lahiru Gunathilake commented on AXIS2C-1126:


I removed the libxml2 and try to build. Still breaks in neethi/test.

/usr/bin/ld: cannot find -lxml2
collect2: ld returned 1 exit status
make[2]: *** [test] Error 1
make[2]: Leaving directory `/home/lahiru/axis2c/neethi/test'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/lahiru/axis2c/neethi'
make: *** [all] Error 2

lahiru

> Build Breaks when Libxml2-dev isn't install
> ---
>
> Key: AXIS2C-1126
> URL: https://issues.apache.org/jira/browse/AXIS2C-1126
> Project: Axis2-C
>  Issue Type: Bug
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 8.04
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
>
> I tried to build Axis2C by running build.sh and I haven't install libxml2-dev 
> in my machine since I tried to work with guththila.
> But in neethi/test build breaks by telling a problem with -lxml2. After 
> installing libxml2-dev Axis2C build breaks.
> I think this should be changed since guththila parser is the default parser. 
> 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] Created: (AXIS2C-1126) Build Breaks when Libxml2-dev isn't install

[Lahiru Gunathilake (JIRA)]

Build Breaks when Libxml2-dev isn't install
---

 Key: AXIS2C-1126
 URL: https://issues.apache.org/jira/browse/AXIS2C-1126
 Project: Axis2-C
  Issue Type: Bug
Affects Versions: Current (Nightly)
 Environment: Ubuntu 8.04
Reporter: Lahiru Gunathilake
 Fix For: Current (Nightly)



I tried to build Axis2C by running build.sh and I haven't install libxml2-dev 
in my machine since I tried to work with guththila.
But in neethi/test build breaks by telling a problem with -lxml2. After 
installing libxml2-dev Axis2C build breaks.

I think this should be changed since guththila parser is the default parser. 

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] Resolved: (AXIS2C-1089) Hello Client in manual Broken

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake resolved AXIS2C-1089.


Resolution: Fixed

> Hello Client in manual Broken
> -
>
> Key: AXIS2C-1089
> URL: https://issues.apache.org/jira/browse/AXIS2C-1089
> Project: Axis2-C
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.3.0
>Reporter: Dinesh Premalal
>Assignee: Lahiru Gunathilake
>
> hello_client.c is broken, please follow this link for more info
> http://marc.info/?l=axis-c-dev&m=120658792802310&w=2

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


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

[jira] Issue Comment Edited: (AXIS2C-1089) Hello Client in manual Broken

[Lahiru Gunathilake (JIRA)]

[ 
https://issues.apache.org/jira/browse/AXIS2C-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586737#action_12586737
 ] 

lahiru edited comment on AXIS2C-1089 at 4/8/08 3:47 AM:


have to change the manual.

regs
lahiru

  was (Author: lahiru):
hello client and service works fine in my machine.

Regs
lahiru
  
> Hello Client in manual Broken
> -
>
> Key: AXIS2C-1089
> URL: https://issues.apache.org/jira/browse/AXIS2C-1089
> Project: Axis2-C
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.3.0
>Reporter: Dinesh Premalal
>Assignee: Lahiru Gunathilake
>
> hello_client.c is broken, please follow this link for more info
> http://marc.info/?l=axis-c-dev&m=120658792802310&w=2

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


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

[jira] Commented: (AXIS2C-1089) Hello Client in manual Broken

[Lahiru Gunathilake (JIRA)]

[ 
https://issues.apache.org/jira/browse/AXIS2C-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586737#action_12586737
 ] 

Lahiru Gunathilake commented on AXIS2C-1089:


hello client and service works fine in my machine.

Regs
lahiru

> Hello Client in manual Broken
> -
>
> Key: AXIS2C-1089
> URL: https://issues.apache.org/jira/browse/AXIS2C-1089
> Project: Axis2-C
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.3.0
>Reporter: Dinesh Premalal
>Assignee: Lahiru Gunathilake
>
> hello_client.c is broken, please follow this link for more info
> http://marc.info/?l=axis-c-dev&m=120658792802310&w=2

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


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

[jira] Assigned: (AXIS2C-1089) Hello Client in manual Broken

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake reassigned AXIS2C-1089:
--

Assignee: Lahiru Gunathilake

> Hello Client in manual Broken
> -
>
> Key: AXIS2C-1089
> URL: https://issues.apache.org/jira/browse/AXIS2C-1089
> Project: Axis2-C
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.3.0
>Reporter: Dinesh Premalal
>Assignee: Lahiru Gunathilake
>
> hello_client.c is broken, please follow this link for more info
> http://marc.info/?l=axis-c-dev&m=120658792802310&w=2

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


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

[jira] Resolved: (AXIS2C-1003) Memory leak in WSDL2C client code

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake resolved AXIS2C-1003.


Resolution: Fixed

> Memory leak in WSDL2C client code
> -
>
> Key: AXIS2C-1003
> URL: https://issues.apache.org/jira/browse/AXIS2C-1003
> Project: Axis2-C
>  Issue Type: Bug
>  Components: code generation
>Affects Versions: 1.2.0
> Environment: linux redhat as 4.0
> axis2c 1.2.0
> axis2java nigthly build
>Reporter: Simone Bordin
>Assignee: Lahiru Gunathilake
> Attachments: adb_ParSmStateRequest.c, adb_ParSmStateRequestType.c, 
> axis2_stub_AppSmsService.c, valgrind.txt
>
>
> With valgrind i have found some memory leak in client generated with WSDL2C 
> tool.
> In stub source code, some data pointed by "svc_name", "soap_act", "op_qname" 
> are allocated but they are never free.
> Also in some adb data type, there's the same problem with variable 
> "start_input_str" and "end_input_str" , "data_source".
> (in attachement files:
>  axis2_stub_AppSmsService.c: line 75, 180, 188
>  adb_ParSmStateRequest.c: line 249, 354, 324
>  adb_ParSmStateRequestType.c: line 667, 672, 739, 744, 810, 815
> Some leaks are singalled in the the axis2c-1.2 library too.
> Attached file "valgrind.txt" is the valgrind trace after i have resolved 
> leaks in generated code (except "data_source").

-- 
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-1052) Bad code from anonymous empty clompex types

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake resolved AXIS2C-1052.


Resolution: Fixed

>From 2008 12th Nightly build this issue is resolved.

Regs
lahiru

> Bad code from anonymous empty clompex types
> ---
>
> Key: AXIS2C-1052
> URL: https://issues.apache.org/jira/browse/AXIS2C-1052
> Project: Axis2-C
>  Issue Type: Bug
>  Components: code generation
>Affects Versions: 1.3.0
>Reporter: Sam Meder
>Assignee: Lahiru Gunathilake
> Attachments: adb_AddInternetScsiSendTargetsResponse.c
>
>
> I tried generating stubs from the VMWare vim25 wsdls and ended up with a 
> bunch of compile errors. They all seem related to code generated from 
> anonymous and empty  declarations, e.g:
>  
> 
>  
> This seems to generate code with the following two statements (I'll attach 
> the generated code):
>  AXIS2_FREE(env->allocator,start_input_str);
>  AXIS2_FREE(env->allocator,end_input_str);
> The issue is that neither start_input_str nor end_input_str are ever 
> declared/assigned, so compilation fails.

-- 
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-1052) Bad code from anonymous empty clompex types

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake reassigned AXIS2C-1052:
--

Assignee: Lahiru Gunathilake

> Bad code from anonymous empty clompex types
> ---
>
> Key: AXIS2C-1052
> URL: https://issues.apache.org/jira/browse/AXIS2C-1052
> Project: Axis2-C
>  Issue Type: Bug
>  Components: code generation
>Affects Versions: 1.3.0
>Reporter: Sam Meder
>Assignee: Lahiru Gunathilake
> Attachments: adb_AddInternetScsiSendTargetsResponse.c
>
>
> I tried generating stubs from the VMWare vim25 wsdls and ended up with a 
> bunch of compile errors. They all seem related to code generated from 
> anonymous and empty  declarations, e.g:
>  
> 
>  
> This seems to generate code with the following two statements (I'll attach 
> the generated code):
>  AXIS2_FREE(env->allocator,start_input_str);
>  AXIS2_FREE(env->allocator,end_input_str);
> The issue is that neither start_input_str nor end_input_str are ever 
> declared/assigned, so compilation fails.

-- 
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-978) Wrong logic in codegeneration with the XSD_NOTATION.wsdl

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake resolved AXIS2C-978.
---

Resolution: Fixed

> Wrong logic in codegeneration with the XSD_NOTATION.wsdl
> 
>
> Key: AXIS2C-978
> URL: https://issues.apache.org/jira/browse/AXIS2C-978
> Project: Axis2-C
>  Issue Type: Bug
>  Components: code generation
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Lahiru Gunathilake
>Assignee: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
> Attachments: diff.txt
>
>
> When i'm checking all the wsdl's in test/resources/wsdl folder in Axis2c i 
> found that with XSD_NOTATION.wsdl is not working.

-- 
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-1003) Memory leak in WSDL2C client code

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake reassigned AXIS2C-1003:
--

Assignee: Lahiru Gunathilake

> Memory leak in WSDL2C client code
> -
>
> Key: AXIS2C-1003
> URL: https://issues.apache.org/jira/browse/AXIS2C-1003
> Project: Axis2-C
>  Issue Type: Bug
>  Components: code generation
>Affects Versions: 1.2.0
> Environment: linux redhat as 4.0
> axis2c 1.2.0
> axis2java nigthly build
>Reporter: Simone Bordin
>Assignee: Lahiru Gunathilake
> Attachments: adb_ParSmStateRequest.c, adb_ParSmStateRequestType.c, 
> axis2_stub_AppSmsService.c, valgrind.txt
>
>
> With valgrind i have found some memory leak in client generated with WSDL2C 
> tool.
> In stub source code, some data pointed by "svc_name", "soap_act", "op_qname" 
> are allocated but they are never free.
> Also in some adb data type, there's the same problem with variable 
> "start_input_str" and "end_input_str" , "data_source".
> (in attachement files:
>  axis2_stub_AppSmsService.c: line 75, 180, 188
>  adb_ParSmStateRequest.c: line 249, 354, 324
>  adb_ParSmStateRequestType.c: line 667, 672, 739, 744, 810, 815
> Some leaks are singalled in the the axis2c-1.2 library too.
> Attached file "valgrind.txt" is the valgrind trace after i have resolved 
> leaks in generated code (except "data_source").

-- 
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-977) Service and client segfaults with the following wsdl

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-977.
-


> Service and client segfaults with the following wsdl
> 
>
> Key: AXIS2C-977
> URL: https://issues.apache.org/jira/browse/AXIS2C-977
> Project: Axis2-C
>  Issue Type: Bug
>  Components: wsdl2c tool
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Lahiru Gunathilake
>Assignee: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
> Attachments: diff.txt
>
>
> while i'm checking with the wsdl's in the test/resources/wsdl/ i found that 
> when we codegen with  SimpleArrays.wsdl file it seg faults the client and the 
> server.

-- 
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-977) Service and client segfaults with the following wsdl

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake resolved AXIS2C-977.
---

Resolution: Fixed

patch applied.

> Service and client segfaults with the following wsdl
> 
>
> Key: AXIS2C-977
> URL: https://issues.apache.org/jira/browse/AXIS2C-977
> Project: Axis2-C
>  Issue Type: Bug
>  Components: wsdl2c tool
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Lahiru Gunathilake
>Assignee: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
> Attachments: diff.txt
>
>
> while i'm checking with the wsdl's in the test/resources/wsdl/ i found that 
> when we codegen with  SimpleArrays.wsdl file it seg faults the client and the 
> server.

-- 
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-985) There's a leak due to wrong token create

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-985:
--

Attachment: diff_leak_fix.txt

> There's a leak due to wrong token create 
> -
>
> Key: AXIS2C-985
> URL: https://issues.apache.org/jira/browse/AXIS2C-985
> Project: Axis2-C
>  Issue Type: Bug
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Lahiru Gunathilake
>Assignee: Dinesh Premalal
> Fix For: Current (Nightly)
>
> Attachments: diff_leak_fix.txt
>
>
> There's  a wrong token creation in guththila_init method and it cause a 
> memory leak.

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


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

[jira] Created: (AXIS2C-985) There's a leak due to wrong token create

[Lahiru Gunathilake (JIRA)]

There's a leak due to wrong token create 
-

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


There's  a wrong token creation in guththila_init method and it cause a memory 
leak.


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


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

[jira] Assigned: (AXIS2C-978) Wrong logic in codegeneration with the XSD_NOTATION.wsdl

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake reassigned AXIS2C-978:
-

Assignee: Lahiru Gunathilake

> Wrong logic in codegeneration with the XSD_NOTATION.wsdl
> 
>
> Key: AXIS2C-978
> URL: https://issues.apache.org/jira/browse/AXIS2C-978
> Project: Axis2-C
>  Issue Type: Bug
>  Components: code generation
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Lahiru Gunathilake
>Assignee: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
> Attachments: diff.txt
>
>
> When i'm checking all the wsdl's in test/resources/wsdl folder in Axis2c i 
> found that with XSD_NOTATION.wsdl is not working.

-- 
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-977) Service and client segfaults with the following wsdl

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake reassigned AXIS2C-977:
-

Assignee: Lahiru Gunathilake

> Service and client segfaults with the following wsdl
> 
>
> Key: AXIS2C-977
> URL: https://issues.apache.org/jira/browse/AXIS2C-977
> Project: Axis2-C
>  Issue Type: Bug
>  Components: wsdl2c tool
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Lahiru Gunathilake
>Assignee: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
> Attachments: diff.txt
>
>
> while i'm checking with the wsdl's in the test/resources/wsdl/ i found that 
> when we codegen with  SimpleArrays.wsdl file it seg faults the client and the 
> server.

-- 
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-983) Following wsdl's are not working with wsdl2java tool and wsdl2c tool

[Lahiru Gunathilake (JIRA)]

[ 
https://issues.apache.org/jira/browse/AXIS2C-983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568426#action_12568426
 ] 

Lahiru Gunathilake commented on AXIS2C-983:
---

This jira should go in to Axis2java so i'm closing the jira here and raise one 
in Axis2java.

> Following wsdl's are not working with wsdl2java  tool and wsdl2c tool
> -
>
> Key: AXIS2C-983
> URL: https://issues.apache.org/jira/browse/AXIS2C-983
> Project: Axis2-C
>  Issue Type: Bug
>  Components: code generation
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
> Attachments: ExceptionTest.wsdl, FaultMapping.wsdl, inquire_v2.wsdl, 
> nillableComplexType.wsdl, nillableComplexType.xsd
>
>
> I'm checking wsdl's in axis2c source.I found some wsdl's which are not 
> working with wsdl2java and wsdl2c tools.I'm attaching those wsdl's with the 
> jira and please check this.

-- 
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-983) Following wsdl's are not working with wsdl2java tool and wsdl2c tool

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-983.
-

Resolution: Fixed

This jira is not related to axis2c and raised in axis2java.

> Following wsdl's are not working with wsdl2java  tool and wsdl2c tool
> -
>
> Key: AXIS2C-983
> URL: https://issues.apache.org/jira/browse/AXIS2C-983
> Project: Axis2-C
>  Issue Type: Bug
>  Components: code generation
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
> Attachments: ExceptionTest.wsdl, FaultMapping.wsdl, inquire_v2.wsdl, 
> nillableComplexType.wsdl, nillableComplexType.xsd
>
>
> I'm checking wsdl's in axis2c source.I found some wsdl's which are not 
> working with wsdl2java and wsdl2c tools.I'm attaching those wsdl's with the 
> jira and please check this.

-- 
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-983) Following wsdl's are not working with wsdl2java tool and wsdl2c tool

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-983:
--

Attachment: inquire_v2.wsdl
nillableComplexType.xsd

> Following wsdl's are not working with wsdl2java  tool and wsdl2c tool
> -
>
> Key: AXIS2C-983
> URL: https://issues.apache.org/jira/browse/AXIS2C-983
> Project: Axis2-C
>  Issue Type: Bug
>  Components: code generation
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
> Attachments: ExceptionTest.wsdl, FaultMapping.wsdl, inquire_v2.wsdl, 
> nillableComplexType.wsdl, nillableComplexType.xsd
>
>
> I'm checking wsdl's in axis2c source.I found some wsdl's which are not 
> working with wsdl2java and wsdl2c tools.I'm attaching those wsdl's with the 
> jira and please check this.

-- 
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-983) Following wsdl's are not working with wsdl2java tool and wsdl2c tool

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-983:
--

Attachment: nillableComplexType.wsdl
FaultMapping.wsdl
ExceptionTest.wsdl

Here are those wsdl's

> Following wsdl's are not working with wsdl2java  tool and wsdl2c tool
> -
>
> Key: AXIS2C-983
> URL: https://issues.apache.org/jira/browse/AXIS2C-983
> Project: Axis2-C
>  Issue Type: Bug
>  Components: code generation
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
> Attachments: ExceptionTest.wsdl, FaultMapping.wsdl, 
> nillableComplexType.wsdl
>
>
> I'm checking wsdl's in axis2c source.I found some wsdl's which are not 
> working with wsdl2java and wsdl2c tools.I'm attaching those wsdl's with the 
> jira and please check this.

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


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

[jira] Created: (AXIS2C-983) Following wsdl's are not working with wsdl2java tool and wsdl2c tool

[Lahiru Gunathilake (JIRA)]

Following wsdl's are not working with wsdl2java  tool and wsdl2c tool
-

 Key: AXIS2C-983
 URL: https://issues.apache.org/jira/browse/AXIS2C-983
 Project: Axis2-C
  Issue Type: Bug
  Components: code generation
Affects Versions: Current (Nightly)
 Environment: Ubuntu 7.10
Reporter: Lahiru Gunathilake
 Fix For: Current (Nightly)


I'm checking wsdl's in axis2c source.I found some wsdl's which are not working 
with wsdl2java and wsdl2c tools.I'm attaching those wsdl's with the jira and 
please check this.

-- 
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-980) Same code block repeat in guththila_free method

[Lahiru Gunathilake (JIRA)]

[ 
https://issues.apache.org/jira/browse/AXIS2C-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568002#action_12568002
 ] 

Lahiru Gunathilake commented on AXIS2C-980:
---

sorry! this doesn't reduce a memory leak it's a small mistake i've made without 
restarting the server.However that code is not useful.

Regards
lahiru

> Same code block repeat in guththila_free method
> ---
>
> Key: AXIS2C-980
> URL: https://issues.apache.org/jira/browse/AXIS2C-980
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
> Attachments: diff.txt
>
>
> Same code block is repeating in guththila_free method and this cause a memory 
> leak when i check with valgrind.

-- 
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-980) Same code block repeat in guththila_free method

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-980:
--

Attachment: diff.txt

Remove the code block and this fix a leak.

Regards
lahiru

> Same code block repeat in guththila_free method
> ---
>
> Key: AXIS2C-980
> URL: https://issues.apache.org/jira/browse/AXIS2C-980
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
> Attachments: diff.txt
>
>
> Same code block is repeating in guththila_free method and this cause a memory 
> leak when i check with valgrind.

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


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

[jira] Created: (AXIS2C-980) Same code block repeat in guththila_free method

[Lahiru Gunathilake (JIRA)]

Same code block repeat in guththila_free method
---

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


Same code block is repeating in guththila_free method and this cause a memory 
leak when i check with valgrind.


-- 
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-978) Wrong logic in codegeneration with the XSD_NOTATION.wsdl

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-978:
--

Attachment: diff.txt

I change the logic now the XSD_NOTATION.wsdl is working properly.

> Wrong logic in codegeneration with the XSD_NOTATION.wsdl
> 
>
> Key: AXIS2C-978
> URL: https://issues.apache.org/jira/browse/AXIS2C-978
> Project: Axis2-C
>  Issue Type: Bug
>  Components: code generation
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
> Attachments: diff.txt
>
>
> When i'm checking all the wsdl's in test/resources/wsdl folder in Axis2c i 
> found that with XSD_NOTATION.wsdl is not working.

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


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

[jira] Created: (AXIS2C-978) Wrong logic in codegeneration with the XSD_NOTATION.wsdl

[Lahiru Gunathilake (JIRA)]

Wrong logic in codegeneration with the XSD_NOTATION.wsdl


 Key: AXIS2C-978
 URL: https://issues.apache.org/jira/browse/AXIS2C-978
 Project: Axis2-C
  Issue Type: Bug
  Components: code generation
Affects Versions: Current (Nightly)
 Environment: Ubuntu 7.10
Reporter: Lahiru Gunathilake
 Fix For: Current (Nightly)
 Attachments: diff.txt

When i'm checking all the wsdl's in test/resources/wsdl folder in Axis2c i 
found that with XSD_NOTATION.wsdl is not working.

-- 
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-977) Service and client segfaults with the following wsdl

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-977:
--

Attachment: diff.txt

> Service and client segfaults with the following wsdl
> 
>
> Key: AXIS2C-977
> URL: https://issues.apache.org/jira/browse/AXIS2C-977
> Project: Axis2-C
>  Issue Type: Bug
>  Components: wsdl2c tool
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
> Attachments: diff.txt
>
>
> while i'm checking with the wsdl's in the test/resources/wsdl/ i found that 
> when we codegen with  SimpleArrays.wsdl file it seg faults the client and the 
> server.

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


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

[jira] Created: (AXIS2C-977) Service and client segfaults with the following wsdl

[Lahiru Gunathilake (JIRA)]

Service and client segfaults with the following wsdl


 Key: AXIS2C-977
 URL: https://issues.apache.org/jira/browse/AXIS2C-977
 Project: Axis2-C
  Issue Type: Bug
  Components: wsdl2c tool
Affects Versions: Current (Nightly)
 Environment: Ubuntu 7.10
Reporter: Lahiru Gunathilake
 Fix For: Current (Nightly)


while i'm checking with the wsdl's in the test/resources/wsdl/ i found that 
when we codegen with  SimpleArrays.wsdl file it seg faults the client and the 
server.

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


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

[jira] Updated: (AXIS2C-859) guththila parser fails to handle escape sequences for ampersand, less than, greater than

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-859:
--

Attachment: diff_1.txt

Hi Bill,
I've implement this patch according to your fourth and fifth suggestions.I 
doubt on how to implement support escape characters in attribute values.We can 
simply use the we use with text value.As you told it's not pretty.But i'm 
confuse on how to implement it in lower level.
And the next thing is the performance hit.With this patch i did a benchmark and 
there's no performance hit with this patch.Any ideas

regs
lahiru

> guththila parser fails to handle escape sequences for ampersand, less than, 
> greater than
> 
>
> Key: AXIS2C-859
> URL: https://issues.apache.org/jira/browse/AXIS2C-859
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila
>Affects Versions: Current (Nightly)
> Environment: Windows XP, Visual Studio 2005, guththila parser, libcurl
>Reporter: Bill Mitchell
> Attachments: diff.txt, diff_1.txt
>
>
> When an incoming message contains within text the escaped ampersand sequence, 
> "&", this sequence is being passed to the client as raw text without 
> being converted to the single ampersand character.  Clearly, this action must 
> take place at the level of the parser, as only the parser knows whether it is 
> seeing simple text, and conversion is required, or text embedded in a CDATA 
> section, where conversion is not allowed.  I have tested the build with the 
> libxml parser, and of course the libxml parser behaves correctly: the text 
> passed to the client contains only the single ampersand character, not the 
> escaped sequence.  (See section 2.4 of XML 1.0 spec.)
> Looking at the code, I expect the same problem occurs with all escaped 
> sequences, less than and greater than as well as ampersand, on both input and 
> output.  I also don't see where CDATA sections are handled, but as I am not 
> seeing CDATA in the messages from the service I am hitting, I have not tested 
> this case.  

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


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

[jira] Updated: (AXIS2C-857) guththila parser drops xml:id attributes from incoming elements

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-857:
--

Attachment: diff_mod.txt

There's small mistake with the patch file.Same block of code repeated again in 
the patch.

Thanks
Lahiru

> guththila parser drops xml:id attributes from incoming elements
> ---
>
> Key: AXIS2C-857
> URL: https://issues.apache.org/jira/browse/AXIS2C-857
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila
>Affects Versions: Current (Nightly)
> Environment: Windows XP, Visual Studio 2005, guththila parser, libcurl
>Reporter: Bill Mitchell
>Assignee: Dinesh Premalal
>Priority: Minor
> Fix For: 1.2.1
>
> Attachments: diff.txt, diff2.txt, diff_mod.txt
>
>
> The XML specification allows an element to carry an xml:id attribute without 
> the xml namespace being declared explicitly.  In fact, if the xml namespace 
> is declared, it must match http://www.w3.org/XML/1998/namespace.  When the 
> namespace is not declared explicitly, it appears that the guththila parser 
> discards the incoming xml:id attributes without including them in the om.  
> For example, I receive a response message from a service that begins:
> http://www.w3.org/2001/XMLSchema"; 
> xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"; 
> xmlns:fw="http://frameware.xcentrisity.com/services/";>
> 
>  name="customer" supportedMethods="browse browseNext browsePrevious create 
> update delete retrieve">
> 
> 
> 
> 
> ...
> When linked with libxml, the client code sees two attributes, a type 
> attribute and an xml:id attribute, attached to the element nodes.  When 
> linked with the guththila parser, only the type attribute is present.  

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


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

[jira] Updated: (AXIS2C-856) axiom_element_get_children() code behavior does not match header description

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-856:
--

Attachment: diff.txt

> axiom_element_get_children() code behavior does not match header description
> 
>
> Key: AXIS2C-856
> URL: https://issues.apache.org/jira/browse/AXIS2C-856
> Project: Axis2-C
>  Issue Type: Bug
>  Components: xml/om
>Affects Versions: 1.1.0
> Environment: Windows XP, Visual Studio 2005, guththila parser, libcurl
>Reporter: Bill Mitchell
>Priority: Minor
> Attachments: diff.txt
>
>
> The comments in axiom_element.h describing the behavior of 
> axiom_element_get_children indicate that the returned interator is owned by 
> the user and must be freed by the user.  In fact, the code implements this 
> function like axiom_element_get_children_with_qname, where the iterator is 
> owned by the element and is freed when the om is freed.
> Obviously if the user follows the instructions in the .h file and frees the 
> iterator, the memory may be reused before the om structure is freed, at which 
> time things go rapidly downhill.  
> Here are the current comments:
> /**
>  *   returns a list of children iterator
>  *   iterators free function must be called by user
>  */
> AXIS2_EXTERN axiom_children_iterator_t *AXIS2_CALL
> axiom_element_get_children(
> axiom_element_t * om_element,
> const axutil_env_t * env,
> axiom_node_t * element_node);
> I suggest this should read:
> /**
>  *   returns a list of children iterator
>  *   returned iterator is freed when om element struct
>  *  is freed 
>  *   iterators reset function must be called by user
>  */
> AXIS2_EXTERN axiom_children_iterator_t *AXIS2_CALL
> axiom_element_get_children(
> ...

-- 
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-857) guththila parser drops xml:id attributes from incoming elements

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-857:
--

Attachment: (was: diff.txt)

> guththila parser drops xml:id attributes from incoming elements
> ---
>
> Key: AXIS2C-857
> URL: https://issues.apache.org/jira/browse/AXIS2C-857
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila
>Affects Versions: Current (Nightly)
> Environment: Windows XP, Visual Studio 2005, guththila parser, libcurl
>Reporter: Bill Mitchell
>Priority: Minor
> Attachments: diff.txt, diff2.txt
>
>
> The XML specification allows an element to carry an xml:id attribute without 
> the xml namespace being declared explicitly.  In fact, if the xml namespace 
> is declared, it must match http://www.w3.org/XML/1998/namespace.  When the 
> namespace is not declared explicitly, it appears that the guththila parser 
> discards the incoming xml:id attributes without including them in the om.  
> For example, I receive a response message from a service that begins:
> http://www.w3.org/2001/XMLSchema"; 
> xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"; 
> xmlns:fw="http://frameware.xcentrisity.com/services/";>
> 
>  name="customer" supportedMethods="browse browseNext browsePrevious create 
> update delete retrieve">
> 
> 
> 
> 
> ...
> When linked with libxml, the client code sees two attributes, a type 
> attribute and an xml:id attribute, attached to the element nodes.  When 
> linked with the guththila parser, only the type attribute is present.  

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


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

[jira] Updated: (AXIS2C-857) guththila parser drops xml:id attributes from incoming elements

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-857:
--

Attachment: diff.txt

> guththila parser drops xml:id attributes from incoming elements
> ---
>
> Key: AXIS2C-857
> URL: https://issues.apache.org/jira/browse/AXIS2C-857
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila
>Affects Versions: Current (Nightly)
> Environment: Windows XP, Visual Studio 2005, guththila parser, libcurl
>Reporter: Bill Mitchell
>Priority: Minor
> Attachments: diff.txt, diff2.txt
>
>
> The XML specification allows an element to carry an xml:id attribute without 
> the xml namespace being declared explicitly.  In fact, if the xml namespace 
> is declared, it must match http://www.w3.org/XML/1998/namespace.  When the 
> namespace is not declared explicitly, it appears that the guththila parser 
> discards the incoming xml:id attributes without including them in the om.  
> For example, I receive a response message from a service that begins:
> http://www.w3.org/2001/XMLSchema"; 
> xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"; 
> xmlns:fw="http://frameware.xcentrisity.com/services/";>
> 
>  name="customer" supportedMethods="browse browseNext browsePrevious create 
> update delete retrieve">
> 
> 
> 
> 
> ...
> When linked with libxml, the client code sees two attributes, a type 
> attribute and an xml:id attribute, attached to the element nodes.  When 
> linked with the guththila parser, only the type attribute is present.  

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


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

[jira] Updated: (AXIS2C-857) guththila parser drops xml:id attributes from incoming elements

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-857:
--

Attachment: diff.txt

> guththila parser drops xml:id attributes from incoming elements
> ---
>
> Key: AXIS2C-857
> URL: https://issues.apache.org/jira/browse/AXIS2C-857
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila
>Affects Versions: Current (Nightly)
> Environment: Windows XP, Visual Studio 2005, guththila parser, libcurl
>Reporter: Bill Mitchell
>Priority: Minor
> Attachments: diff.txt, diff2.txt
>
>
> The XML specification allows an element to carry an xml:id attribute without 
> the xml namespace being declared explicitly.  In fact, if the xml namespace 
> is declared, it must match http://www.w3.org/XML/1998/namespace.  When the 
> namespace is not declared explicitly, it appears that the guththila parser 
> discards the incoming xml:id attributes without including them in the om.  
> For example, I receive a response message from a service that begins:
> http://www.w3.org/2001/XMLSchema"; 
> xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"; 
> xmlns:fw="http://frameware.xcentrisity.com/services/";>
> 
>  name="customer" supportedMethods="browse browseNext browsePrevious create 
> update delete retrieve">
> 
> 
> 
> 
> ...
> When linked with libxml, the client code sees two attributes, a type 
> attribute and an xml:id attribute, attached to the element nodes.  When 
> linked with the guththila parser, only the type attribute is present.  

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


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

[jira] Updated: (AXIS2C-857) guththila parser drops xml:id attributes from incoming elements

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-857:
--

Attachment: (was: diff.txt)

> guththila parser drops xml:id attributes from incoming elements
> ---
>
> Key: AXIS2C-857
> URL: https://issues.apache.org/jira/browse/AXIS2C-857
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila
>Affects Versions: Current (Nightly)
> Environment: Windows XP, Visual Studio 2005, guththila parser, libcurl
>Reporter: Bill Mitchell
>Priority: Minor
> Attachments: diff.txt, diff2.txt
>
>
> The XML specification allows an element to carry an xml:id attribute without 
> the xml namespace being declared explicitly.  In fact, if the xml namespace 
> is declared, it must match http://www.w3.org/XML/1998/namespace.  When the 
> namespace is not declared explicitly, it appears that the guththila parser 
> discards the incoming xml:id attributes without including them in the om.  
> For example, I receive a response message from a service that begins:
> http://www.w3.org/2001/XMLSchema"; 
> xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"; 
> xmlns:fw="http://frameware.xcentrisity.com/services/";>
> 
>  name="customer" supportedMethods="browse browseNext browsePrevious create 
> update delete retrieve">
> 
> 
> 
> 
> ...
> When linked with libxml, the client code sees two attributes, a type 
> attribute and an xml:id attribute, attached to the element nodes.  When 
> linked with the guththila parser, only the type attribute is present.  

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


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

[jira] Commented: (AXIS2C-859) guththila parser fails to handle escape sequences for ampersand, less than, greater than

[Lahiru Gunathilake (JIRA)]

[ 
https://issues.apache.org/jira/browse/AXIS2C-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563814#action_12563814
 ] 

Lahiru Gunathilake commented on AXIS2C-859:
---

Thanks Bill for the comment.Here's my idea on your comment,

First:This is very similar thing what i have done and only difference is 
there's no memory allocation in this method.However if it's better to avoid 
another memory allocation i will do it in that way.

Second : This is not much clear for me.If you can explain some more that'll be 
great.

Third Forth Fifth: +1for all three ideas. I'll implement these in that way.

Regards
Lahiru


> guththila parser fails to handle escape sequences for ampersand, less than, 
> greater than
> 
>
> Key: AXIS2C-859
> URL: https://issues.apache.org/jira/browse/AXIS2C-859
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila
>Affects Versions: Current (Nightly)
> Environment: Windows XP, Visual Studio 2005, guththila parser, libcurl
>Reporter: Bill Mitchell
> Attachments: diff.txt
>
>
> When an incoming message contains within text the escaped ampersand sequence, 
> "&", this sequence is being passed to the client as raw text without 
> being converted to the single ampersand character.  Clearly, this action must 
> take place at the level of the parser, as only the parser knows whether it is 
> seeing simple text, and conversion is required, or text embedded in a CDATA 
> section, where conversion is not allowed.  I have tested the build with the 
> libxml parser, and of course the libxml parser behaves correctly: the text 
> passed to the client contains only the single ampersand character, not the 
> escaped sequence.  (See section 2.4 of XML 1.0 spec.)
> Looking at the code, I expect the same problem occurs with all escaped 
> sequences, less than and greater than as well as ampersand, on both input and 
> output.  I also don't see where CDATA sections are handled, but as I am not 
> seeing CDATA in the messages from the service I am hitting, I have not tested 
> this case.  

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


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

[jira] Updated: (AXIS2C-859) guththila parser fails to handle escape sequences for ampersand, less than, greater than

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-859:
--

Attachment: diff.txt

Now guththila parses escape charactor.Please go through the patch file and 
apply this since this may reduce the performance of Guththila parser. 

> guththila parser fails to handle escape sequences for ampersand, less than, 
> greater than
> 
>
> Key: AXIS2C-859
> URL: https://issues.apache.org/jira/browse/AXIS2C-859
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila
>Affects Versions: Current (Nightly)
> Environment: Windows XP, Visual Studio 2005, guththila parser, libcurl
>Reporter: Bill Mitchell
> Attachments: diff.txt
>
>
> When an incoming message contains within text the escaped ampersand sequence, 
> "&", this sequence is being passed to the client as raw text without 
> being converted to the single ampersand character.  Clearly, this action must 
> take place at the level of the parser, as only the parser knows whether it is 
> seeing simple text, and conversion is required, or text embedded in a CDATA 
> section, where conversion is not allowed.  I have tested the build with the 
> libxml parser, and of course the libxml parser behaves correctly: the text 
> passed to the client contains only the single ampersand character, not the 
> escaped sequence.  (See section 2.4 of XML 1.0 spec.)
> Looking at the code, I expect the same problem occurs with all escaped 
> sequences, less than and greater than as well as ampersand, on both input and 
> output.  I also don't see where CDATA sections are handled, but as I am not 
> seeing CDATA in the messages from the service I am hitting, I have not tested 
> this case.  

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


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

[jira] Commented: (AXIS2C-834) guththila_xml_writer has problems with default namespace

[Lahiru Gunathilake (JIRA)]

[ 
https://issues.apache.org/jira/browse/AXIS2C-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561335#action_12561335
 ] 

Lahiru Gunathilake commented on AXIS2C-834:
---

Yes,thanks alot for pointing out it.

Regs
lahiru

> guththila_xml_writer has problems with default namespace
> 
>
> Key: AXIS2C-834
> URL: https://issues.apache.org/jira/browse/AXIS2C-834
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila, xml/parser
>Affects Versions: Current (Nightly)
> Environment: Windows XP, Visual Studio 2005, guththila parser, 
> libcurl transport
>Reporter: Bill Mitchell
> Attachments: guththila_xml_writer_diff, 
> guththila_xml_writer_wrapper_diff
>
>
> The guththila xml writer appears to have several problems related to the 
> default namespace.  These appear when attempting to use the ADB stubs for the 
> elements in the SOAP request messages, as the Axis data bindings fill in the 
> default namespace from the WSDL.  
> (1) In guththila_xml_writer_wrapper, guththila_xml_writer_wrap_namespace() 
> has a comment indicating that the prefix is null on the default namespace.  
> Yet it goes ahead and calls guththila_write_namespace() which requires both a 
> prefix and a namespace URI.  
> (2) In guththila_xml_wrapper.c, the routine 
> guththila_write_start_element_with_namespace() does not understand the 
> default namespace.  It searches the table of namespaces to determine the 
> prefix that goes with this namespace.  If the namespace is not found, no XML 
> is generated, so no element is started although the outer code assumes it is. 
>  This results in malformed XML as below:
> http://schemas.xmlsoap.org/soap/envelope/";>
> 
>  xmlns="http://frameware.xcentrisity.com/services/";>
>  Yes, the trailing  elements in the stack without having started one of the elements, this is the 
> outcome.  
> (3) After fixing the above problems, I discovered that the generated XML for 
> the element inside the SOAP Body incorrectly had the URI of the namespace as 
> the name of the element, rather than the name itself.  I.e., the message 
> contained a structure like:
> http://schemas.xmlsoap.org/soap/envelope/";>
> 
> 
>  exemplarHandle="master" 
> xmlns="http://frameware.xcentrisity.com/services/";>http://frameware.xcentrisity.com/services/>
> 
> 
> The problem is that 
> guththila_xml_writer_wrapper_start_element_with_namespace() is not flipping 
> the order of the parameters as is correctly done in 
> guththila_xml_writer_wrapper_start_element_with_namespace_prefix().  

-- 
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-857) guththila parser drops xml:id attributes from incoming elements

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-857:
--

Attachment: diff.txt

This patch will fix the bug.Now guththila parser keeps a namespace with the 
prefix of xml for all the xml's.Then it is no longer drop the attributes with 
prefix xml.


> guththila parser drops xml:id attributes from incoming elements
> ---
>
> Key: AXIS2C-857
> URL: https://issues.apache.org/jira/browse/AXIS2C-857
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila
>Affects Versions: Current (Nightly)
> Environment: Windows XP, Visual Studio 2005, guththila parser, libcurl
>Reporter: Bill Mitchell
>Priority: Minor
> Attachments: diff.txt
>
>
> The XML specification allows an element to carry an xml:id attribute without 
> the xml namespace being declared explicitly.  In fact, if the xml namespace 
> is declared, it must match http://www.w3.org/XML/1998/namespace.  When the 
> namespace is not declared explicitly, it appears that the guththila parser 
> discards the incoming xml:id attributes without including them in the om.  
> For example, I receive a response message from a service that begins:
> http://www.w3.org/2001/XMLSchema"; 
> xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"; 
> xmlns:fw="http://frameware.xcentrisity.com/services/";>
> 
>  name="customer" supportedMethods="browse browseNext browsePrevious create 
> update delete retrieve">
> 
> 
> 
> 
> ...
> When linked with libxml, the client code sees two attributes, a type 
> attribute and an xml:id attribute, attached to the element nodes.  When 
> linked with the guththila parser, only the type attribute is present.  

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


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

[jira] Updated: (AXIS2C-914) Simple axis server segfault in side the guththila when we send a wrong xml

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-914:
--

Attachment: diff.txt

> Simple axis server segfault in side the guththila when we send a wrong xml
> --
>
> Key: AXIS2C-914
> URL: https://issues.apache.org/jira/browse/AXIS2C-914
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila
>Affects Versions: Current (Nightly)
> Environment: Ubuntu7.10
>Reporter: Lahiru Gunathilake
>Assignee: Sanjaya Ratnaweera
> Fix For: Current (Nightly)
>
> Attachments: diff.txt
>
>
> When i'm testing Rampart Samples guththila writes a wrong xml file and send 
> it to simple axis server.Then simple axis server segfault inside a guththila 
> method.This cause due to deletion without checking.

-- 
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-914) Simple axis server segfault in side the guththila when we send a wrong xml

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-914:
--

Attachment: (was: diff.txt)

> Simple axis server segfault in side the guththila when we send a wrong xml
> --
>
> Key: AXIS2C-914
> URL: https://issues.apache.org/jira/browse/AXIS2C-914
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila
>Affects Versions: Current (Nightly)
> Environment: Ubuntu7.10
>Reporter: Lahiru Gunathilake
>Assignee: Sanjaya Ratnaweera
> Fix For: Current (Nightly)
>
>
> When i'm testing Rampart Samples guththila writes a wrong xml file and send 
> it to simple axis server.Then simple axis server segfault inside a guththila 
> method.This cause due to deletion without checking.

-- 
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-907) In test_om it doensn't serialize attributes

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-907:
--

Attachment: diff.txt

> In test_om it doensn't serialize attributes
> ---
>
> Key: AXIS2C-907
> URL: https://issues.apache.org/jira/browse/AXIS2C-907
> Project: Axis2-C
>  Issue Type: Improvement
>  Components: xml/om
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Lahiru Gunathilake
>Priority: Minor
> Fix For: Current (Nightly)
>
> Attachments: diff.txt
>
>
> In test_om it is not serialize the attributes and we can't see what are the 
> attributes of particular element.This will be very important when we want to 
> see the full serialization of a xml.

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


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

[jira] Updated: (AXIS2C-907) In test_om it doensn't serialize attributes

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-907:
--

Attachment: (was: diff.txt)

> In test_om it doensn't serialize attributes
> ---
>
> Key: AXIS2C-907
> URL: https://issues.apache.org/jira/browse/AXIS2C-907
> Project: Axis2-C
>  Issue Type: Improvement
>  Components: xml/om
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Lahiru Gunathilake
>Priority: Minor
> Fix For: Current (Nightly)
>
>
> In test_om it is not serialize the attributes and we can't see what are the 
> attributes of particular element.This will be very important when we want to 
> see the full serialization of a xml.

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


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

[jira] Commented: (AXIS2C-834) guththila_xml_writer has problems with default namespace

[Lahiru Gunathilake (JIRA)]

[ 
https://issues.apache.org/jira/browse/AXIS2C-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560930#action_12560930
 ] 

Lahiru Gunathilake commented on AXIS2C-834:
---

This issue is resloved by the jira 891.Now guththila parser works with default 
namespaces.

Regs
lahiru

> guththila_xml_writer has problems with default namespace
> 
>
> Key: AXIS2C-834
> URL: https://issues.apache.org/jira/browse/AXIS2C-834
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila, xml/parser
>Affects Versions: Current (Nightly)
> Environment: Windows XP, Visual Studio 2005, guththila parser, 
> libcurl transport
>Reporter: Bill Mitchell
> Attachments: guththila_xml_writer_diff, 
> guththila_xml_writer_wrapper_diff
>
>
> The guththila xml writer appears to have several problems related to the 
> default namespace.  These appear when attempting to use the ADB stubs for the 
> elements in the SOAP request messages, as the Axis data bindings fill in the 
> default namespace from the WSDL.  
> (1) In guththila_xml_writer_wrapper, guththila_xml_writer_wrap_namespace() 
> has a comment indicating that the prefix is null on the default namespace.  
> Yet it goes ahead and calls guththila_write_namespace() which requires both a 
> prefix and a namespace URI.  
> (2) In guththila_xml_wrapper.c, the routine 
> guththila_write_start_element_with_namespace() does not understand the 
> default namespace.  It searches the table of namespaces to determine the 
> prefix that goes with this namespace.  If the namespace is not found, no XML 
> is generated, so no element is started although the outer code assumes it is. 
>  This results in malformed XML as below:
> http://schemas.xmlsoap.org/soap/envelope/";>
> 
>  xmlns="http://frameware.xcentrisity.com/services/";>
>  Yes, the trailing  elements in the stack without having started one of the elements, this is the 
> outcome.  
> (3) After fixing the above problems, I discovered that the generated XML for 
> the element inside the SOAP Body incorrectly had the URI of the namespace as 
> the name of the element, rather than the name itself.  I.e., the message 
> contained a structure like:
> http://schemas.xmlsoap.org/soap/envelope/";>
> 
> 
>  exemplarHandle="master" 
> xmlns="http://frameware.xcentrisity.com/services/";>http://frameware.xcentrisity.com/services/>
> 
> 
> The problem is that 
> guththila_xml_writer_wrapper_start_element_with_namespace() is not flipping 
> the order of the parameters as is correctly done in 
> guththila_xml_writer_wrapper_start_element_with_namespace_prefix().  

-- 
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-907) In test_om it doensn't serialize attributes

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-907:
--

Attachment: diff.txt

> In test_om it doensn't serialize attributes
> ---
>
> Key: AXIS2C-907
> URL: https://issues.apache.org/jira/browse/AXIS2C-907
> Project: Axis2-C
>  Issue Type: Improvement
>  Components: xml/om
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Lahiru Gunathilake
>Priority: Minor
> Fix For: Current (Nightly)
>
> Attachments: diff.txt
>
>
> In test_om it is not serialize the attributes and we can't see what are the 
> attributes of particular element.This will be very important when we want to 
> see the full serialization of a xml.

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


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

[jira] Updated: (AXIS2C-907) In test_om it doensn't serialize attributes

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-907:
--

Attachment: (was: diff.txt)

> In test_om it doensn't serialize attributes
> ---
>
> Key: AXIS2C-907
> URL: https://issues.apache.org/jira/browse/AXIS2C-907
> Project: Axis2-C
>  Issue Type: Improvement
>  Components: xml/om
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Lahiru Gunathilake
>Priority: Minor
> Fix For: Current (Nightly)
>
>
> In test_om it is not serialize the attributes and we can't see what are the 
> attributes of particular element.This will be very important when we want to 
> see the full serialization of a xml.

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


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

[jira] Closed: (AXIS2C-908) Guththila doesn't parse attributes which contais prefix

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-908.
-

Resolution: Fixed

> Guththila doesn't parse attributes which contais prefix
> ---
>
> Key: AXIS2C-908
> URL: https://issues.apache.org/jira/browse/AXIS2C-908
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila
>Affects Versions: Current (Nightly)
> Environment: Ubuntu7.10
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
>
> I try to pass an xml which contains attributes with prefix and tried to print 
> the attributes of all the elements.But it is not printing attributes which 
> contains prefix with that.

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


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

[jira] Updated: (AXIS2C-913) Rampart/C scenario4 onwards are not working with Guththila

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-913:
--

Summary: Rampart/C scenario4 onwards are not working with Guththila  (was: 
Rampart/C scenario4 onwards are  are now working with Guththila)

Summary changed.

regs
lahiru

> Rampart/C scenario4 onwards are not working with Guththila
> --
>
> Key: AXIS2C-913
> URL: https://issues.apache.org/jira/browse/AXIS2C-913
> Project: Axis2-C
>  Issue Type: Bug
>  Components: build system (Unix/Linux)
>Affects Versions: Current (Nightly)
> Environment: ubuntu7.10
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
> Attachments: diff.txt
>
>
> when Axis2c build with guththila and run rampart samples it works up to 
> scenario4.But from scenario4 including itself is not working with Guththila.

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


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

[jira] Created: (AXIS2C-914) Simple axis server segfault in side the guththila when we send a wrong xml

[Lahiru Gunathilake (JIRA)]

Simple axis server segfault in side the guththila when we send a wrong xml
--

 Key: AXIS2C-914
 URL: https://issues.apache.org/jira/browse/AXIS2C-914
 Project: Axis2-C
  Issue Type: Bug
  Components: guththila
Affects Versions: Current (Nightly)
 Environment: Ubuntu7.10
Reporter: Lahiru Gunathilake
 Fix For: Current (Nightly)
 Attachments: diff.txt

When i'm testing Rampart Samples guththila writes a wrong xml file and send it 
to simple axis server.Then simple axis server segfault inside a guththila 
method.This cause due to deletion without checking.


-- 
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-914) Simple axis server segfault in side the guththila when we send a wrong xml

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-914:
--

Attachment: diff.txt

Checks the namespace struct before deleting that inside guththia_un_init method.


> Simple axis server segfault in side the guththila when we send a wrong xml
> --
>
> Key: AXIS2C-914
> URL: https://issues.apache.org/jira/browse/AXIS2C-914
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila
>Affects Versions: Current (Nightly)
> Environment: Ubuntu7.10
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
> Attachments: diff.txt
>
>
> When i'm testing Rampart Samples guththila writes a wrong xml file and send 
> it to simple axis server.Then simple axis server segfault inside a guththila 
> method.This cause due to deletion without checking.

-- 
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-913) Rampart/C scenario4 onwards are are now working with Guththila

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-913:
--

Attachment: diff.txt

There was a problem with guththila_xml_writer.c and guththila_buffer.h.Now with 
Guththila all the samples are working.

> Rampart/C scenario4 onwards are  are now working with Guththila
> ---
>
> Key: AXIS2C-913
> URL: https://issues.apache.org/jira/browse/AXIS2C-913
> Project: Axis2-C
>  Issue Type: Bug
>  Components: build system (Unix/Linux)
>Affects Versions: Current (Nightly)
> Environment: ubuntu7.10
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
> Attachments: diff.txt
>
>
> when Axis2c build with guththila and run rampart samples it works up to 
> scenario4.But from scenario4 including itself is not working with Guththila.

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


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

[jira] Created: (AXIS2C-913) Rampart/C scenario4 onwards are are now working with Guththila

[Lahiru Gunathilake (JIRA)]

Rampart/C scenario4 onwards are  are now working with Guththila
---

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


when Axis2c build with guththila and run rampart samples it works up to 
scenario4.But from scenario4 including itself is not working with Guththila.

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


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

[jira] Created: (AXIS2C-908) Guththila doesn't parse attributes which contais prefix

[Lahiru Gunathilake (JIRA)]

Guththila doesn't parse attributes which contais prefix
---

 Key: AXIS2C-908
 URL: https://issues.apache.org/jira/browse/AXIS2C-908
 Project: Axis2-C
  Issue Type: Bug
  Components: guththila
Affects Versions: Current (Nightly)
 Environment: Ubuntu7.10
Reporter: Lahiru Gunathilake
 Fix For: Current (Nightly)


I try to pass an xml which contains attributes with prefix and tried to print 
the attributes of all the elements.But it is not printing attributes which 
contains prefix with that.

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


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

[jira] Created: (AXIS2C-907) In test_om it doensn't serialize attributes

[Lahiru Gunathilake (JIRA)]

In test_om it doensn't serialize attributes
---

 Key: AXIS2C-907
 URL: https://issues.apache.org/jira/browse/AXIS2C-907
 Project: Axis2-C
  Issue Type: Improvement
  Components: xml/om
Affects Versions: Current (Nightly)
 Environment: Ubuntu 7.10
Reporter: Lahiru Gunathilake
Priority: Minor
 Fix For: Current (Nightly)
 Attachments: diff.txt

In test_om it is not serialize the attributes and we can't see what are the 
attributes of particular element.This will be very important when we want to 
see the full serialization of a xml.

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


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

[jira] Updated: (AXIS2C-907) In test_om it doensn't serialize attributes

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-907:
--

Attachment: diff.txt

I've change the code of test_om and now it prints all the element clearly with 
it's attributes and attribute values.


> In test_om it doensn't serialize attributes
> ---
>
> Key: AXIS2C-907
> URL: https://issues.apache.org/jira/browse/AXIS2C-907
> Project: Axis2-C
>  Issue Type: Improvement
>  Components: xml/om
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.10
>Reporter: Lahiru Gunathilake
>Priority: Minor
> Fix For: Current (Nightly)
>
> Attachments: diff.txt
>
>
> In test_om it is not serialize the attributes and we can't see what are the 
> attributes of particular element.This will be very important when we want to 
> see the full serialization of a xml.

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


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

[jira] Updated: (AXIS2C-897) Have to chage the API method according to default namespace scenario

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-897:
--

Attachment: diff.txt

change the API methods.

> Have to chage the API method according to default namespace scenario
> 
>
> Key: AXIS2C-897
> URL: https://issues.apache.org/jira/browse/AXIS2C-897
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.04
>Reporter: Lahiru Gunathilake
>Priority: Minor
> Fix For: Current (Nightly)
>
> Attachments: diff.txt
>
>
> Since in default namespace there's no prefix and prefix is NULL.So we have to 
> change the Guththila API method.
> 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] Created: (AXIS2C-897) Have to chage the API method according to default namespace scenario

[Lahiru Gunathilake (JIRA)]

Have to chage the API method according to default namespace scenario


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


Since in default namespace there's no prefix and prefix is NULL.So we have to 
change the Guththila API method.

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] Updated: (AXIS2C-886) Unused Variable in guththila_xml_parser.c

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-886:
--

Attachment: (was: diff.txt)

> Unused Variable in guththila_xml_parser.c
> -
>
> Key: AXIS2C-886
> URL: https://issues.apache.org/jira/browse/AXIS2C-886
> Project: Axis2-C
>  Issue Type: Bug
> Environment: Ubuntu 7.04
>Reporter: Lahiru Gunathilake
> Attachments: diff_2.txt
>
>
> There are Warnings in Axis2c when it build with guththila parser.

-- 
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-886) Unused Variable in guththila_xml_parser.c

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-886:
--

Attachment: diff_2.txt

> Unused Variable in guththila_xml_parser.c
> -
>
> Key: AXIS2C-886
> URL: https://issues.apache.org/jira/browse/AXIS2C-886
> Project: Axis2-C
>  Issue Type: Bug
> Environment: Ubuntu 7.04
>Reporter: Lahiru Gunathilake
> Attachments: diff_2.txt
>
>
> There are Warnings in Axis2c when it build with guththila parser.

-- 
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-891) Guththila doesn't parse xml elements with default namespace correctly

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-891:
--

Attachment: diff.txt

Previously Guththila doesn't work with default namespaces.I've change the 
guththila_token_close method and now it parses xml's which contains default 
namespaces.

Regs
lahiru

> Guththila doesn't parse xml elements with default namespace correctly
> -
>
> Key: AXIS2C-891
> URL: https://issues.apache.org/jira/browse/AXIS2C-891
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila
> Environment: Linux  (Ubuntu 7.10)
>Reporter: Dimuthu Gamage
> Attachments: diff.txt
>
>
> For an example consider the following XML.
> http://ws.apache.org/axis2/xsd";>
>
> 
> Whenever I checked the qname of param0 and rows0, it returns the namespace 
> uri with NULL values. But they actually should belong to the 
> "http://ws.apache.org/axis2/xsd";.
> This leads to fail code-generation tests with Guththila.

-- 
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-883) Apache segfaults when running mtom sample with big files

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-883.
-


> Apache segfaults when running mtom sample with big files
> 
>
> Key: AXIS2C-883
> URL: https://issues.apache.org/jira/browse/AXIS2C-883
> Project: Axis2-C
>  Issue Type: Bug
> Environment: Ubuntu 7.04
>Reporter: Lahiru Gunathilake
>Assignee: Sanjaya Ratnaweera
> Fix For: Current (Nightly)
>
> Attachments: diff.txt
>
>
> I ran apache in - X mode and ran mtom sample with an attachment of 100MB 
> file.Then the thread which handle that request segfaults.

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


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

[jira] Closed: (AXIS2C-841) Axis2 Manual have to up date

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-841.
-


> Axis2 Manual have to up date 
> -
>
> Key: AXIS2C-841
> URL: https://issues.apache.org/jira/browse/AXIS2C-841
> Project: Axis2-C
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: Current (Nightly)
> Environment: Ubuntu
>Reporter: Lahiru Gunathilake
>Assignee: Sanjaya Ratnaweera
> Fix For: 1.2.0
>
> Attachments: doc_diff.txt
>
>
> Axis2 manual is not updated with the new changes occure in log file scenario 
> and Global Pool scenario

-- 
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-839) When MaxLogFileSize is not given Apache Segfaults.

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-839.
-


> When MaxLogFileSize is not given Apache Segfaults.
> --
>
> Key: AXIS2C-839
> URL: https://issues.apache.org/jira/browse/AXIS2C-839
> Project: Axis2-C
>  Issue Type: Bug
> Environment: Ubuntu
>Reporter: Lahiru Gunathilake
>Assignee: Sanjaya Ratnaweera
> Fix For: 1.2.0
>
> Attachments: diff.txt
>
>
> When MaxLogFileSize is not given Apache Segfaults.

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


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

[jira] Closed: (AXIS2C-825) Still mod_axis2.so create Shared Global Pool when uncomment Axis2SharedGlobalPoolSize in httpd.conf

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-825.
-


> Still mod_axis2.so create Shared Global Pool when uncomment 
> Axis2SharedGlobalPoolSize in httpd.conf
> ---
>
> Key: AXIS2C-825
> URL: https://issues.apache.org/jira/browse/AXIS2C-825
> Project: Axis2-C
>  Issue Type: Bug
>  Components: core/transport
>Affects Versions: Current (Nightly)
> Environment: Ubuntu
>Reporter: Lahiru Gunathilake
>Assignee: Sanjaya Ratnaweera
> Fix For: 1.2.0
>
> Attachments: diff_mod_axis
>
>
> I've build Axis2c with Apache and comment SharedGlobalPoolSize and test the 
> Performance.But still it share the Global pool when that entry is 
> uncomment.Then the performance gone down.
> 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] Closed: (AXIS2C-835) Wrong error message in simple axis server

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-835.
-


> Wrong error message in simple axis server
> -
>
> Key: AXIS2C-835
> URL: https://issues.apache.org/jira/browse/AXIS2C-835
> Project: Axis2-C
>  Issue Type: Bug
>  Components: core/transport
>Affects Versions: Current (Nightly)
> Environment: Ubuntu
>Reporter: Lahiru Gunathilake
>Assignee: Sanjaya Ratnaweera
>Priority: Minor
> Fix For: Current (Nightly)
>
> Attachments: diff
>
>
> In an error message there's a spelling mistake.
> 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] Closed: (AXIS2C-810) test_om segfaults with Guththila when serialize a signed message with rampart

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-810.
-


> test_om segfaults with Guththila when serialize a signed message with rampart
> -
>
> Key: AXIS2C-810
> URL: https://issues.apache.org/jira/browse/AXIS2C-810
> Project: Axis2-C
>  Issue Type: Bug
>  Components: xml/om
>Affects Versions: Current (Nightly)
> Environment: Ubuntu
>Reporter: Lahiru Gunathilake
>Assignee: Sanjaya Ratnaweera
>Priority: Minor
> Fix For: 1.2.0
>
> Attachments: diff
>
>
> When i tried to parse a soap which generate when rampart signed sample runs 
> it cause an segfault with Guththila.
> 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] Closed: (AXIS2C-807) Apache segfault when build with apache enable

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-807.
-


>  Apache segfault when build with apache enable
> --
>
> Key: AXIS2C-807
> URL: https://issues.apache.org/jira/browse/AXIS2C-807
> Project: Axis2-C
>  Issue Type: Bug
>  Components: xml/om
>Affects Versions: Current (Nightly)
> Environment: Ubuntu
>Reporter: Lahiru Gunathilake
>Assignee: Sanjaya Ratnaweera
> Fix For: 1.2.0
>
> Attachments: temp_patch
>
>
> Apache server segfault when apache build with Apache. 
> 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] Closed: (AXIS2C-808) Incompatible between Guththila and Libxml

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-808.
-


> Incompatible between Guththila and Libxml
> -
>
> Key: AXIS2C-808
> URL: https://issues.apache.org/jira/browse/AXIS2C-808
> Project: Axis2-C
>  Issue Type: Bug
>  Components: xml/om
>Affects Versions: Current (Nightly)
> Environment: Ubuntu
>Reporter: Lahiru Gunathilake
>Assignee: Sanjaya Ratnaweera
> Fix For: 1.2.0
>
> Attachments: diff
>
>
> In om_stax_builder.c it calls parsers get_value and get_prefix like methods 
> to get the parts of the xml.But when it wants to free those axis2_char_t* it 
> simply calls the axiom_xml_reader_free method.But since Guththila and Libxml2 
> implementations are different , with Guththila it doesn't actually delete the 
> malloc char*.To resolve this we can't simply use AXIS2_FREE to delete with 
> both parsers because libxml2 gives those parts without doing malloc.Then we 
> have to use some macro definition and decide whether built with guththila or 
> not and use seperate methods to delete those char*.If we simply ignore this 
> it cause a big memory leak with Guththila.It's around 3000bytes for a simple 
> xml.
> 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] Closed: (AXIS2C-803) test_om serialization fails with Guththila Parser

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-803.
-


> test_om serialization fails with Guththila Parser
> -
>
> Key: AXIS2C-803
> URL: https://issues.apache.org/jira/browse/AXIS2C-803
> Project: Axis2-C
>  Issue Type: Bug
>  Components: xml/parser
>Affects Versions: Current (Nightly)
> Environment: Ubuntu
>Reporter: Lahiru Gunathilake
>Assignee: Sanjaya Ratnaweera
> Fix For: 1.2.0
>
> Attachments: diff_om_test
>
>
> When Axis2c build with Guththila test_om serialization fails for every xml i 
> test.There's a problem with guththila_xml_writer_wrapper.c.Then i can't parse 
> an xml to test with guththila parser using test_om.
> 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] Closed: (AXIS2C-800) There's a memory leak in om_stax_builder.c

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-800.
-


> There's a memory leak in om_stax_builder.c
> --
>
> Key: AXIS2C-800
> URL: https://issues.apache.org/jira/browse/AXIS2C-800
> Project: Axis2-C
>  Issue Type: Bug
>  Components: xml/om
>Affects Versions: Current (Nightly)
> Environment: Ubuntu
>Reporter: Lahiru Gunathilake
>Assignee: Sanjaya Ratnaweera
>Priority: Minor
> Fix For: Current (Nightly)
>
> Attachments: om_patch
>
>
> om_stax_builder.c does'nt delete some axis2_char_t* then this cause some 
> memory leaks.

-- 
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-804) Installation guide should be modify according to Shared Global Pool

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-804.
-


> Installation guide should be modify according to Shared Global Pool
> ---
>
> Key: AXIS2C-804
> URL: https://issues.apache.org/jira/browse/AXIS2C-804
> Project: Axis2-C
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: Current (Nightly)
> Environment: Ubuntu
>Reporter: Lahiru Gunathilake
>Assignee: Sanjaya Ratnaweera
> Fix For: 1.2.0
>
> Attachments: diff_INSTALL
>
>
> According to Shared Global Pool in Axis2c apache module We have to give some 
> more entries to httpd.conf file but those things are not in the INSTALL 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] Closed: (AXIS2C-789) Memory leak in om_stax_builder

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-789.
-


> Memory leak in om_stax_builder
> --
>
> Key: AXIS2C-789
> URL: https://issues.apache.org/jira/browse/AXIS2C-789
> Project: Axis2-C
>  Issue Type: Bug
>  Components: xml/om
> Environment: Ubuntu
>Reporter: Lahiru Gunathilake
>Assignee: Sanjaya Ratnaweera
> Fix For: 1.2.0
>
> Attachments: diff_om, diff_patch2
>
>
> There was a big memory leak in om_stax_builder it's around 4000bytes for echo 
> sample.

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


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

[jira] Closed: (AXIS2C-799) Unnessasary malloc in Guththila Wrapper

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-799.
-


> Unnessasary malloc in Guththila Wrapper
> ---
>
> Key: AXIS2C-799
> URL: https://issues.apache.org/jira/browse/AXIS2C-799
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila
>Affects Versions: Current (Nightly)
> Environment: Ubuntu
>Reporter: Lahiru Gunathilake
>Assignee: Sanjaya Ratnaweera
> Fix For: 1.2.0
>
> Attachments: diff_file1
>
>
> There's an unnessary malloc in the guththila_xml_writer_wrapper.c.Due to this 
> there's a 800 bytes of a memory leak.

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


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

[jira] Closed: (AXIS2C-785) Fixed some memory leaks

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-785.
-


> Fixed some memory leaks
> ---
>
> Key: AXIS2C-785
> URL: https://issues.apache.org/jira/browse/AXIS2C-785
> Project: Axis2-C
>  Issue Type: Bug
>  Components: guththila
>Affects Versions: Current (Nightly)
> Environment: Ubutu
>Reporter: Lahiru Gunathilake
>Assignee: Sanjaya Ratnaweera
> Fix For: 1.2.0
>
> Attachments: diff_parser, memory_patch, memory_patch2
>
>
> There are few memory leaks when axis2c runs with Guththila xml parser.When i 
> run simple_axis_server with valgrind i found serveral memory leaks.
> 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] Closed: (AXIS2C-764) Wrong xml write in guththila parser

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-764.
-


> 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: Sanjaya Ratnaweera
>Priority: Minor
> Fix For: 1.2.0
>
> Attachments: patch_raw_xml
>
>
> 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  xmlns:ns1="http://www.extreme.indiana.edu/wsdl/Benchmark1";
> 
> Input xml
> 
> 
>http://www.w3.org/2003/05/soap-envelope";>
>   
>   
>   xmlns:ns1="http://www.extreme.indiana.edu/wsdl/Benchmark1";>
> 0.0
>  
>   
>
> -
> 
> output xml with guththila parser
> 
> http://www.w3.org/2003/05/soap-envelope";>
>
>http://www.w3.org/2003/05/soap-envelope";>
>xmlns:ns1="http://www.extreme.indiana.edu/wsdl/Benchmark1";
>  0.00>
>   
>
> --
> output xml with libxml2
> ---
> http://www.w3.org/2003/05/soap-envelope";>
>
>
>xmlns:ns1="http://www.extreme.indiana.edu/wsdl/Benchmark1";>
>  0.00
>   
>
> 

-- 
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-772) Guththila Parser write extra namespace

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-772.
-


> Guththila Parser write extra namespace
> --
>
> Key: AXIS2C-772
> URL: https://issues.apache.org/jira/browse/AXIS2C-772
> Project: Axis2-C
>  Issue Type: Bug
>  Components: build system (Unix/Linux)
>Affects Versions: Current (Nightly)
> Environment: Ubuntu
>Reporter: Lahiru Gunathilake
>Assignee: Sanjaya Ratnaweera
> Fix For: 1.2.0
>
> Attachments: patch_file, patch_file_improved
>
>
> 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 
> ---
>  xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>  xmlns:soapenv = "http://www.w3.org/2003/05/soap-envelope";> xmlns:ns1 = 
> "http://axis2/test/namespace1";>18
> ---
> --with Libxml2 
> Parser--
>  xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>  
> xmlns:ns1="http://axis2/test/namespace1";>18
> -
> 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] Closed: (AXIS2C-755) Codegen segmentation fault when null value is passed

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-755.
-


> 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] Closed: (AXIS2C-727) Performace Testing with Guththila Parser

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-727.
-


> 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 
> 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] Closed: (AXIS2C-726) Issue In Guththila Parser

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake closed AXIS2C-726.
-


> 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 
> ---
>  "http://www.w3.org/2003/05/soap-envelope";>  xmlns:soapenv = "http://www.w3.org/2003/05/soap-envelope";> xmlns:ns1 = 
> "http://axis2/test/namespace1";>18
> ---
> --with Libxml2 
> Parser--
>  xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>  
> xmlns:ns1="http://axis2/test/namespace1";>18
> -
> 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] Created: (AXIS2C-886) Unused Variable in guththila_xml_parser.c

[Lahiru Gunathilake (JIRA)]

Unused Variable in guththila_xml_parser.c
-

 Key: AXIS2C-886
 URL: https://issues.apache.org/jira/browse/AXIS2C-886
 Project: Axis2-C
  Issue Type: Bug
 Environment: Ubuntu 7.04
Reporter: Lahiru Gunathilake
 Attachments: diff.txt

There are Warnings in Axis2c when it build with guththila parser.

-- 
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-886) Unused Variable in guththila_xml_parser.c

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-886:
--

Attachment: diff.txt

commented those lines.

> Unused Variable in guththila_xml_parser.c
> -
>
> Key: AXIS2C-886
> URL: https://issues.apache.org/jira/browse/AXIS2C-886
> Project: Axis2-C
>  Issue Type: Bug
> Environment: Ubuntu 7.04
>Reporter: Lahiru Gunathilake
> Attachments: diff.txt
>
>
> There are Warnings in Axis2c when it build with guththila parser.

-- 
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-877) Function axutil_env_create_all[Alastair FETTES]

[Lahiru Gunathilake (JIRA)]

[ 
https://issues.apache.org/jira/browse/AXIS2C-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556170#action_12556170
 ] 

Lahiru Gunathilake commented on AXIS2C-877:
---

Since  parameter log_file is a const it is not used by convention.

Regs
lahiru

> Function axutil_env_create_all[Alastair FETTES]
> ---
>
> Key: AXIS2C-877
> URL: https://issues.apache.org/jira/browse/AXIS2C-877
> Project: Axis2-C
>  Issue Type: Bug
>  Components: util
>Affects Versions: Current (Nightly)
> Environment: Ubuntu
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
>
> 
> AXIS2_EXTERN
> axutil_env_t* axutil_env_create_all(
>  const axis2_char_t* log_file,
>  const axutil_log_levels_t   log_level)
> 
> Problem: This function does not take responsibility for the memory allocated 
> by log_file.
> Solution: Document memory ownership for parameters and return value. 

-- 
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-876) Function axiom_element_add_attribute[Alastair FETTES]

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-876:
--

Attachment: diff1.txt

This resolves the issue.

> Function axiom_element_add_attribute[Alastair FETTES]
> -
>
> Key: AXIS2C-876
> URL: https://issues.apache.org/jira/browse/AXIS2C-876
> Project: Axis2-C
>  Issue Type: Bug
>  Components: xml/om
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.04
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
> Attachments: diff1.txt
>
>
> 
> AXIS2_EXTERN
> axis2_status_t axiom_element_add_attribute(
>  axiom_element_t*   om_element,
>  const axutil_env_t*env,
>  axiom_attribute_t* attribute,
>  axiom_node_t*  element_node)
> 
> Problem: The parameter om_element takes responsibility for the memory 
> allocated for the parameter attribute, thus a call to axiom_element_free will 
> de-allocated the data for attribute. The parameter om_element also takes 
> responsibility for the namespace associated with attribute.
> Solution: Document memory ownership for parameters and return value. 

-- 
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-875) Function axiom_attribute_create[Alastair FETTES]

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-875:
--

Attachment: diff.txt

This resolves the issue.

> Function axiom_attribute_create[Alastair FETTES]
> 
>
> Key: AXIS2C-875
> URL: https://issues.apache.org/jira/browse/AXIS2C-875
> Project: Axis2-C
>  Issue Type: Bug
>  Components: xml/om
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.04
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
> Attachments: diff.txt
>
>
> 
> AXIS2_EXTERN
> axiom_attribute_t* axiom_attribute_create(
>  const axutil_env_t* env,
>  const axis2_char_t* localname,
>  const axis2_char_t* value,
>  axiom_namespace_t*  ns)
> 
> Problem: This return value of type axiom_attribute_t* does not take 
> responsibility for the memory allocated for localname, value, ns, and env. 
> Although, if the return value is added to an axiom_node_t using 
> axiom_element_add_attribute, the responsibility of the namespace of the 
> attribute is given to the axiom_node_t. 
> Solution: Document memory ownership for parameters and return value.  
> Investigate the ownership of the namespace parameter.

-- 
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-883) Apache segfaults when running mtom sample with big files

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-883:
--

Attachment: diff.txt

> Apache segfaults when running mtom sample with big files
> 
>
> Key: AXIS2C-883
> URL: https://issues.apache.org/jira/browse/AXIS2C-883
> Project: Axis2-C
>  Issue Type: Bug
> Environment: Ubuntu 7.04
>Reporter: Lahiru Gunathilake
> Attachments: diff.txt
>
>
> I ran apache in - X mode and ran mtom sample with an attachment of 100MB 
> file.Then the thread which handle that request segfaults.

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


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

[jira] Created: (AXIS2C-883) Apache segfaults when running mtom sample with big files

[Lahiru Gunathilake (JIRA)]

Apache segfaults when running mtom sample with big files


 Key: AXIS2C-883
 URL: https://issues.apache.org/jira/browse/AXIS2C-883
 Project: Axis2-C
  Issue Type: Bug
 Environment: Ubuntu 7.04
Reporter: Lahiru Gunathilake


I ran apache in - X mode and ran mtom sample with an attachment of 100MB 
file.Then the thread which handle that request segfaults.

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


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

[jira] Updated: (AXIS2C-882) Problem with Apache module when running mtom

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-882:
--

Description: 
I run mtom sample with a big file and run with Apache then it fails to send it 
and in the log file it show an error like this in mtom.log.

[error] http_client.c(455) Response error, Server Shutdown

[Fri Jan  4 10:36:36 2008] [error] mtom_client.c(149) Stub invoke FAILED: Error 
code: 82 :: Input stream is NULL in message context


But mtom sample works fine with simple axis server for this particular 
file.With apache when increase the size of the file with mtom sample then,it 
cause a big performance degrading.But with simple axis server it works much 
faster than with Apache.

  was:
I run mtom sample with a big file and run with Apache then it fails to send it 
and in the log file it show an error like this in mtom.log.

[Fri Jan  4 10:22:20 2008] [error] http_sender.c(727) status_code < 0 

But mtom sample works fine with simple axis server for this particular 
file.With apache when increase the size of the file with mtom sample then,it 
cause a big performance degrading.But with simple axis server it works much 
faster than with Apache.


> Problem with Apache module when running mtom 
> -
>
> Key: AXIS2C-882
> URL: https://issues.apache.org/jira/browse/AXIS2C-882
> Project: Axis2-C
>  Issue Type: Bug
>  Components: transport/http
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.04
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
>
> I run mtom sample with a big file and run with Apache then it fails to send 
> it and in the log file it show an error like this in mtom.log.
> [error] http_client.c(455) Response error, Server Shutdown
> [Fri Jan  4 10:36:36 2008] [error] mtom_client.c(149) Stub invoke FAILED: 
> Error code: 82 :: Input stream is NULL in message context
> But mtom sample works fine with simple axis server for this particular 
> file.With apache when increase the size of the file with mtom sample then,it 
> cause a big performance degrading.But with simple axis server it works much 
> faster than with 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] Created: (AXIS2C-882) Problem with Apache module when running mtom

[Lahiru Gunathilake (JIRA)]

Problem with Apache module when running mtom 
-

 Key: AXIS2C-882
 URL: https://issues.apache.org/jira/browse/AXIS2C-882
 Project: Axis2-C
  Issue Type: Bug
  Components: transport/http
Affects Versions: Current (Nightly)
 Environment: Ubuntu 7.04
Reporter: Lahiru Gunathilake
 Fix For: Current (Nightly)


I run mtom sample with a big file and run with Apache then it fails to send it 
and in the log file it show an error like this in mtom.log.

[Fri Jan  4 10:22:20 2008] [error] http_sender.c(727) status_code < 0 

But mtom sample works fine with simple axis server for this particular 
file.With apache when increase the size of the file with mtom sample then,it 
cause a big performance degrading.But with simple axis server it works much 
faster than with 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-867) Function axis2_svc_client_remove_all_headers[Alastair FETTES]

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-867:
--

Summary: Function axis2_svc_client_remove_all_headers[Alastair FETTES]  
(was: Function axis2_svc_client_remove_all_headers)

> Function axis2_svc_client_remove_all_headers[Alastair FETTES]
> -
>
> Key: AXIS2C-867
> URL: https://issues.apache.org/jira/browse/AXIS2C-867
> Project: Axis2-C
>  Issue Type: Bug
>  Components: core/clientapi
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.04
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
> Attachments: diff.txt, diff2.txt
>
>
>  for (i = 0; i < size; i++)
> {
> /*axiom_node_t *node = NULL;  
>   
>  
>node = axutil_array_list_get(svc_client->headers, env, i); 
>   
>  
>   
>   
>  
>if (node)  
>   
>  
>{  
>   
>  
>axiom_node_free_tree(node, env);   
>   
>  
>node = NULL;   
>   
>  
>} */
> axutil_array_list_remove(svc_client->headers, env, i);
> }
> AXIS2_EXTERN void *AXIS2_CALL
>  axutil_array_list_remove(
>  struct axutil_array_list *array_list,
>  const axutil_env_t * env,
>  int index)
>  {
>  void *result = NULL;
>  int i = 0;
>  AXIS2_PARAM_CHECK (env->error, array_list, AXIS2_FAILURE);
>  if (axutil_array_list_check_bound_exclusive(array_list, env, index))
>  {
>  result = array_list->data[index];
>  for (i = index; i < array_list->size - 1; i++)
>  array_list->data[i] = array_list->data[i + 1];
> array_list->size--;
>  }
>  return result;
>  } There is a possible bug in "axis2_svc_client_remove_all_headers" function. 
>  The call to "axutil_array_list_remove" is where the problem stems from.  
> Since the for-loop  is incrementing, and the value of "array_list->size"  is 
> decrementing, eventually line 120 will fail, and some of the headers will not 
> be cleared out.

-- 
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-869) Function axiom_element_set_tex[Alastair FETTES]

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-869:
--

Summary: Function axiom_element_set_tex[Alastair FETTES]  (was: Function 
axiom_element_set_tex)

> Function axiom_element_set_tex[Alastair FETTES]
> ---
>
> Key: AXIS2C-869
> URL: https://issues.apache.org/jira/browse/AXIS2C-869
> Project: Axis2-C
>  Issue Type: Bug
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.04
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
>
> AXIS2_EXTERN
> axis2_status_t axiom_element_set_text(
>   axiom_element_t*   om_element,
>   const axutil_env_t*env,
>   const axis2_char_t*text,
>   axiom_node_t*  element_node) 
> Currently, the om_element has no use and is not used by the function 
> axiom_element_set_text therefore could probably be set NULL.  The function 
> does not take control of the string text within text. 
> Solution: Document memory ownership for parameters and return value.

-- 
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-868) Function axiom_element_create[Alastair FETTES]

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-868:
--

Summary: Function axiom_element_create[Alastair FETTES]  (was: Function 
axiom_element_create)

> Function axiom_element_create[Alastair FETTES]
> --
>
> Key: AXIS2C-868
> URL: https://issues.apache.org/jira/browse/AXIS2C-868
> Project: Axis2-C
>  Issue Type: Bug
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.04
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
>
> AXIS2_EXTERN
> axiom_element_t* axiom_element_create(
>   const axutil_env_t*   env,
>   axiom_node_t* parent,
>   const axis2_char_t*   localname,
>   axiom_namespace_t*ns,
>   axiom_node_t**node)
> The axiom_node_t instance node has responsibility for the returned 
> axion_element_t*.  Therefore, calls to axiom_node_free_tree will free this 
> returned element (in addition to all the child nodes of node).  The memory 
> allocated for the return value should not be de-allocated using 
> axiom_element_free in this scenario, since it is internally tied to the node.

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


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

[jira] Updated: (AXIS2C-870) Function axiom_xml_reader_create_for_memory[Alastair FETTES]

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-870:
--

Summary: Function axiom_xml_reader_create_for_memory[Alastair FETTES]  
(was: Function axiom_xml_reader_create_for_memory)

> Function axiom_xml_reader_create_for_memory[Alastair FETTES]
> 
>
> Key: AXIS2C-870
> URL: https://issues.apache.org/jira/browse/AXIS2C-870
> Project: Axis2-C
>  Issue Type: Bug
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.04
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
>
> AXIS2_EXTERN
> axiom_xml_reader_t* axiom_xml_reader_create_for_memory(
>   const axutil_env_t* env,
>   void*   container,
>   int size,
>   const axis2_char_t* encoding,
>   int type) 
> The return value of type axiom_xml_reader_t* takes control of the data 
> contained within container.

-- 
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-872) Function axiom_document_create[Alastair FETTES]

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-872:
--

Summary: Function axiom_document_create[Alastair FETTES]  (was: Function 
axiom_document_create)

> Function axiom_document_create[Alastair FETTES]
> ---
>
> Key: AXIS2C-872
> URL: https://issues.apache.org/jira/browse/AXIS2C-872
> Project: Axis2-C
>  Issue Type: Bug
> Environment: Ubuntu 7.04
>Reporter: Lahiru Gunathilake
>
> 
> AXIS2_EXTERN
> axiom_document_t* axiom_document_create(
> const axutil_env_t* env,
> axiom_node_t*   root,
> axiom_stax_builder_t*   builder)
> 
> Problem: The return value of type axiom_document_t* takes responsibility for 
> the memory allocated for root. Any child node that is added to root will be 
> free-ed when the function axiom_document_free is called. The return value of 
> type axiom_document_t* does not takes responsibility for the memory allocated 
> for builder (as of v1.1.0, this seems odd, since the internal structure 
> maintains a pointer to builder, but does not free builder. So this may create 
> a dangling pointer situation).
> Solution: Document memory ownership for parameters and return value.  
> Investigate use of pointers in internal structure.

-- 
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-871) Function axiom_stax_builder_create[Alastair FETTES]

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-871:
--

Summary: Function axiom_stax_builder_create[Alastair FETTES]  (was: 
Function axiom_stax_builder_create)

> Function axiom_stax_builder_create[Alastair FETTES]
> ---
>
> Key: AXIS2C-871
> URL: https://issues.apache.org/jira/browse/AXIS2C-871
> Project: Axis2-C
>  Issue Type: Bug
>  Components: xml/om
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.04
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
>
> 
> AXIS2_EXTERN
> axiom_stax_builder_t* axiom_stax_builder_create(
>   const axutil_env_t*   env,
>   axiom_xml_reader_t*   parser)
> 
> Problem: The return value of type axiom_stax_t* takes responsibility for the 
> memory allocated for parser.
> Solution: Document memory ownership for parameters and return value. 

-- 
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-873) Function axiom_document_build_all[Alastair FETTES]

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-873:
--

Summary: Function axiom_document_build_all[Alastair FETTES]  (was: Function 
axiom_document_build_all)

> Function axiom_document_build_all[Alastair FETTES]
> --
>
> Key: AXIS2C-873
> URL: https://issues.apache.org/jira/browse/AXIS2C-873
> Project: Axis2-C
>  Issue Type: Bug
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.04
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
>
> 
> AXIS2_EXTERN
> axiom_node_t* axiom_document_build_all(
>   struct axiom_document* document,
>   const axutil_env_t*env)
> 
> Problem: The caller of this function is not given responsibility for the 
> return value of type axiom_node_t*, since (as of v1.1.0) the return value is 
> free-ed by the function axiom_document_free. If the caller calls the function 
> axiom_document_free_self, the return value is NOT free-ed. So a memory leak 
> is possible here.
> Solution: Document memory ownership for parameters and return value.  
> Investigate the use of free functions and pointers in regards to possible 
> memory leak.

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


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

[jira] Updated: (AXIS2C-874) Function axiom_namespace_create[Alastair FETTES]

[Lahiru Gunathilake (JIRA)]

AXIS2_EXTERN
axiom_node_t*
 axiom_document_build_all(
  struct axiom_document* document,

  const axutil_env_t*env)

Function
 axiom_namespace_create
In-Reply-To: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Lahiru Gunathilake updated AXIS2C-874:
--

Summary: 
 Function axiom_namespace_create[Alastair FETTES]
AXIS2_EXTERN
axiom_node_t* axiom_document_build_all(
  struct axiom_document* document,
  const axutil_env_t*env)

Function axiom_namespace_create

  was:

AXIS2_EXTERN
axiom_node_t* axiom_document_build_all(
  struct axiom_document* document,
  const axutil_env_t*env)

Function axiom_namespace_create



>  Function axiom_namespace_create[Alastair FETTES]
AXIS2_EXTERN
axiom_node_t* axiom_document_build_all(
  struct axiom_document* document,
  const axutil_env_t*env)

Function axiom_namespace_create
> 
>
> Key: AXIS2C-874
> URL: https://issues.apache.org/jira/browse/AXIS2C-874
> Project: Axis2-C
>  Issue Type: Bug
>  Components: xml/om
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.04
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
>
> 
> AXIS2_EXTERN
> axiom_namespace_t* axiom_namespace_create(
>  const axutil_env_t* env,
>  const axis2_char_t* uri,
>  const axis2_char_t* prefix)
> 
> Problem: This function and return value of type axiom_namespace_t* does not 
> take responsibility for the memory allocated for the parameters uri, prefix, 
> and of course env.
> Solution: Document memory ownership for parameters and return value.

-- 
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-875) Function axiom_attribute_create[Alastair FETTES]

[Lahiru Gunathilake (JIRA)]

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

Lahiru Gunathilake updated AXIS2C-875:
--

Summary: Function axiom_attribute_create[Alastair FETTES]  (was: Function 
axiom_attribute_create)

> Function axiom_attribute_create[Alastair FETTES]
> 
>
> Key: AXIS2C-875
> URL: https://issues.apache.org/jira/browse/AXIS2C-875
> Project: Axis2-C
>  Issue Type: Bug
>  Components: xml/om
>Affects Versions: Current (Nightly)
> Environment: Ubuntu 7.04
>Reporter: Lahiru Gunathilake
> Fix For: Current (Nightly)
>
>
> 
> AXIS2_EXTERN
> axiom_attribute_t* axiom_attribute_create(
>  const axutil_env_t* env,
>  const axis2_char_t* localname,
>  const axis2_char_t* value,
>  axiom_namespace_t*  ns)
> 
> Problem: This return value of type axiom_attribute_t* does not take 
> responsibility for the memory allocated for localname, value, ns, and env. 
> Although, if the return value is added to an axiom_node_t using 
> axiom_element_add_attribute, the responsibility of the namespace of the 
> attribute is given to the axiom_node_t. 
> Solution: Document memory ownership for parameters and return value.  
> Investigate the ownership of the namespace parameter.

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