[
https://issues.apache.org/jira/browse/AXIS2C-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Senaka Fernando updated AXIS2C-735:
---
Attachment: diff.txt
Hi Rajika,
I went through the proposed patch. But, I believe that the
Unreachable code found in http_reciever.c
-
Key: AXIS2C-738
URL: https://issues.apache.org/jira/browse/AXIS2C-738
Project: Axis2-C
Issue Type: Bug
Components: transport/http
[
https://issues.apache.org/jira/browse/AXIS2C-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Senaka Fernando updated AXIS2C-738:
---
Attachment: diff.txt
By modifying the code (as in diff.txt), this issue would be resolved.
As you see, axis2_bool_t, has two values, AXIS2_TRUE and AXIS2_FALSE that
corresponds to true and false respectively.
Now when such a type is compared in an 'if' or a 'while' as in,
if (..statement..) or while (..statement..) there are two mechanisms used.
That is,
lets assume myVar =
Function Definition does not match declaration in soap_builder.c
Key: AXIS2C-739
URL: https://issues.apache.org/jira/browse/AXIS2C-739
Project: Axis2-C
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AXIS2C-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Senaka Fernando updated AXIS2C-739:
---
Attachment: diff.txt
Proposed patch solves the bug (refer diff.txt).
Senaka
Function
Definition of type axis2_bool_t based on an enumeration
---
Key: AXIS2C-740
URL: https://issues.apache.org/jira/browse/AXIS2C-740
Project: Axis2-C
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/AXIS2C-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Senaka Fernando updated AXIS2C-740:
---
Attachment: diff.txt
Refer diff.txt for the patch that adds the desired improvement.
Please
axis2_any_content_type_add_value(...), in any_content_type.c always returns
AXIS2_SUCCESS.
--
Key: AXIS2C-741
URL: https://issues.apache.org/jira/browse/AXIS2C-741
[
https://issues.apache.org/jira/browse/AXIS2C-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Senaka Fernando updated AXIS2C-741:
---
Attachment: diff.txt
In the proposed patch, it is tested whether the hash is actually set,
[
https://issues.apache.org/jira/browse/AXIS2C-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538330
]
senakafdo edited comment on AXIS2C-741 at 10/28/07 11:38 AM:
---
In the proposed
Improper placement of code in data_handler.c leads to increased time overhead
and memory leaks.
---
Key: AXIS2C-742
URL: https://issues.apache.org/jira/browse/AXIS2C-742
some return paths in axiom_data_handler_read_from() does not call fclose() on
the open file stream, in data_handler.c
-
Key: AXIS2C-743
URL:
[
https://issues.apache.org/jira/browse/AXIS2C-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538411
]
Senaka Fernando commented on AXIS2C-728:
Hi Tsunoda,
SSLVerifyClient none is not the best option to adopt.
[
https://issues.apache.org/jira/browse/AXIS2C-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Senaka Fernando updated AXIS2C-728:
---
Attachment: diff.txt
SSL client authenticate failed
--
[
https://issues.apache.org/jira/browse/AXIS2C-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Premalal resolved AXIS2C-708.
Resolution: Fixed
Fix Version/s: Current (Nightly)
Assignee: Damitha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok I can see at least some one is really using commons-logging. I
understand and withdraw my proposal to remove the commons-logging.
And Oleg, well it might be the case that other jars also might have
dependencies on commons-logging, so we will have
On Sun, 2007-10-28 at 10:18 -0400, Eran Chinthaka wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok I can see at least some one is really using commons-logging. I
understand and withdraw my proposal to remove the commons-logging.
And Oleg, well it might be the case that other jars
the situation with dependencies may be improved by carefully
restructuring Axis2 code into a number of smaller jars
(kernel + options)
I think this idea can work so long as:
1. The kernel is small and contains what you need to get started. i.e. It
is possible to run Axis2 with just the
Lawrence Mandel wrote:
the situation with dependencies may be improved by carefully
restructuring Axis2 code into a number of smaller jars
(kernel + options)
I think this idea can work so long as:
1. The kernel is small and contains what you need to get started. i.e. It
is possible to run
Does anyone have any objections or comments regarding the proposed response?
Thanks.
On 10/23/07, Andrew Das [EMAIL PROTECTED] wrote:
The samples will not have any WebSphere specifics, so that should not be
of concern. The primary goal is to demonstrate interoperability with
WebSphere, using
Hi Oleg,
I like that idea from an end user perspective (and that I'm seeing some
suggestions from this perspective) but it will definitely take more work
than an optional downloads list with descriptions. Also, the development
of that kind of utility seems out of scope for the WS project and
Hi,
This is an issue in Rampart because it doesn't processes the security
header of fault messages.
https://issues.apache.org/jira/browse/RAMPART-90
This will be fixed in the next release of Apache Rampart.
Thanks,
Ruchith
On 10/12/07, Tim Munro (myDIALS) [EMAIL PROTECTED] wrote:
Hi All,
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Along with the discussion on various mail threads to restructure Axis2
distributables, I looked at the modules and this is what I came up with.
Axis2 gurus and experts please comment on the modules as you know better
than me.
Both Axis2 Server
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I looked at the modules we have in Axis2 and just wanted to know about
some modules.Please be kind enough to help me to answer following
questions on our modules.
1. Why do we have mex and mex-mar as two separate modules? Can't we put
them in
Hi Chinthaka,
On 10/29/07, Eran Chinthaka [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
1. Why do we have mex and mex-mar as two separate modules? Can't we put
them in one module and do maven magic to create two separate
distributables, if needed?
I was
Hi,
4. Why do we have ping module? Isn't that something that should go
inside samples?
The objective of the Ping module is to serve as a base for web service
monitoring.. I'm not sure whether anybody is using it yet or whether
anybody is planning on doing any improvements to it..
IMHO samples
NPE throws when starting axis2server if NIO https transport is enabled in
axis2.xml
---
Key: AXIS2-3309
URL: https://issues.apache.org/jira/browse/AXIS2-3309
Project:
hi,
As I understood we are going to shift the Axis2 as five sperate artifacts.
1. Kernal
2. Axis2 Server
3. Axis2 Client
4. Tools
5. Optional
what are the things we going to shift on each module? to which modules we
are going to put other jars?
(i.e axiom, neethi, common jars)
Does Axis2
29 matches
Mail list logo
