Re: soap action based dispatching with rampart

Thanks Manjula for this finding. Is this a bug or added purposely? Are there any problems if module defined phases get invoked before the default phases? If not definitely need to fix this phase ordering problem in Axis2/C. Cheers, Kaushalye Manjula Peiris wrote: Hi, I debug the code. What is

Re: soap action based dispatching with rampart

Uthaiyashankar wrote: Hi, Currently rampart in-handler is called in "PreDispatch" phase in inflow. Due to that, if a message is having only soap action (no operation is specified in url or no wsa:action is given, so only possible way of dispatching is based on soap action) and message is sec

[jira] Assigned: (AXIS2C-1129) Processing requests by modules, handlers

[ https://issues.apache.org/jira/browse/AXIS2C-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Malinda Kaushalye Kapuruge reassigned AXIS2C-1129: -- Assignee: Malinda Kaushalye Kapuruge > Processing requests

Re: [Rampart/C] [ANN] Apache Rampart/C 1.2.0 Released

This time with the correct subject ;-) -Kau Kaushalye Kapuruge wrote: Hi All, Apache Rampart/C team is pleased to announce the release of Apache Rampart/C 1.2.0 You may download the release from http://ws.apache.org/rampart/c/download.cgi Key features of the release

[Rampart/C] [ANN] Apache Rampart/C 1.1.0 Released

Hi All, Apache Rampart/C team is pleased to announce the release of Apache Rampart/C 1.2.0 You may download the release from http://ws.apache.org/rampart/c/download.cgi Key features of the release --- 1. Ability to send and verify UsernameTokens with -

Re: [Vote][Rampart-C] Vote for Apache Rampart/C 1.2.0 Release - Take 2

-to17104438.html Kaushalye Kapuruge wrote: Hi Devs, I have uploaded the Apache Rampart/C 1.2.0 release artifacts (Take 2) here http://people.apache.org/~kaushalye/release/rampart-c/1.2.0 The key to verify the release artifacts can be found at http://people.apache.org/~kaushalye/release/KEYS

Re: Caching support for MTOM

Manjula Peiris wrote: Hi devs, I have implemented a caching technique [1] for MTOM. I had to completely rewrite the current mime_parser logic. The implementation also has a new searching technique which efficiently uses memory. There are some bugs need to be fixed in the new implementation and i

[Vote][Rampart-C] Vote for Apache Rampart/C 1.2.0 Release - Take 2

Hi Devs, I have uploaded the Apache Rampart/C 1.2.0 release artifacts (Take 2) here http://people.apache.org/~kaushalye/release/rampart-c/1.2.0 The key to verify the release artifacts can be found at http://people.apache.org/~kaushalye/release/KEYS Please test and review with Apache Axis2/C 1.4

Re: [Vote][Rampart-C] Vote for Apache Rampart/C 1.2.0 Release - Take 1

Deepal jayasinghe wrote: Hi Kaushalye , Seems like docs/index.html has a problem it has a the release data as "*25th Apr 2008 - Apache Rampart/C Version 1.2.0 Released*". I think you need to update that, Thanks for pointing this out. But this is the date when we packed the RC2, which turned

[Vote][Rampart-C] Vote for Apache Rampart/C 1.2.0 Release - Take 1

Hi Devs, I have uploaded the Apache Rampart/C 1.2.0 release artifacts here http://people.apache.org/~kaushalye/release/rampart-c/1.2.0 The key to verify the release artifacts can be found at http://people.apache.org/~kaushalye/release/KEYS Please test and review with Apache Axis2/C 1.4.0 artifa

[jira] Commented: (AXIS2C-1129) Processing requests by modules, handlers

[ https://issues.apache.org/jira/browse/AXIS2C-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594512#action_12594512 ] Malinda Kaushalye Kapuruge commented on AXIS2C-1129: Hi, You can

Re: [VOTE][Axis2]Apache Axis2/C 1.4.0 Release - Take3

Tested on src + binary in Debian GNU. Worked fine. Also all the test cases were successful in Apache Rampart/C as well. Here's my +1. Cheers, Kaushalye Dinesh Premalal wrote: Hi Devs, I have packaged and uploaded the Apache Axis2/C 1.4.0 release artifacts at [1]. The key used to sign the rel

Re: More readable LOG Macros.

Chintana Wilamuna wrote: On Wed, Apr 30, 2008 at 5:01 PM, Kaushalye Kapuruge <[EMAIL PROTECTED]> wrote: +1. But when it comes to submodule prefix, could this be a problem? Say I need to use prefix [rampart][oxs] for OMXMLSecurity and [rampart][util] for Utility module etc. Would t

Re: More readable LOG Macros.

Dinesh Premalal wrote: Kaushalye Kapuruge <[EMAIL PROTECTED]> writes: +1. But when it comes to submodule prefix, could this be a problem? Say I need to use prefix [rampart][oxs] for OMXMLSecurity and [rampart][util] for Utility module etc. Would that be a big issue if we give the free

Re: More readable LOG Macros.

Chintana Wilamuna wrote: On Wed, Apr 30, 2008 at 10:51 AM, Ruwan Janapriya <[EMAIL PROTECTED]> wrote: AXIS2_DEBUG_MSG(env->log, "[Project XYZ] Debug Message Tik Tak Too"); also the above macro name AXIS2_DEBUG_MSG is open for better (short) name suggestions. Since the env->log part has the

Re: Axis2/c failed on Windows

Hi Kasun, Could you please attach the error log? Cheers, Kaushalye Kasun Indrasiri wrote: Hi, Axis2/C was successfully built on windows.. but when we start the axis2_http server.. it failed by giving an strange error.. Thanks, Kasun -- http://blog.kaushalye.org/ http://wso2.org/ --

Re: [VOTE][Axis2]Apache Axis2/C 1.3.1 Release Artifacts - Take 2

Hi, Tested on debian with Rampart/C. Worked fine. +1 Cheers, Kaushalye Uthaiyashankar wrote: Hi, I tested on windows. Tested with rampart as well and works fine. Here is my +1. Regards, Shankar. Manjula Peiris wrote: Hi, I have tested both the source and binary distributions on ubuntu 7.10

Re: [VOTE][Axis2]Apache Axis2/C 1.3.1 Release Artifacts

Hi devs, I found that google sample is giving sporadic segfault. Here is the stacktrace[1]. The valgrind trace too is attached. Cheers, Kaushalye [1] #0 0x0001 in ?? () #1 0xa7f86335 in axutil_stream_read (stream=0x80f2d30, env=0x804b400, buffer=0x80fd4ac, count=33283) at stream.c:709 #2

[Rampart-C] Apache Rampart/C 1.2.0 RC1

Hi All, I packed and uploaded Apache Rampart/C 1.2.0 RC1 here [1]. Please test it with Apache Axis2/C 1.3.1 RC1 here [2], and send your feedback. Cheers, Kaushalye [1]http://people.apache.org/~kaushalye/release/rampart-c/1.2.0-RC1/ [2]http://people.apache.org/~dinesh/release/Axis2C-1.3.1-RC1/

Re: re-distribute openSSL dlls with AXIS2/c and patent issue

Raymond Zhou wrote: Hi All, I am using AXIS2/c to develop a web service client component in a commercial application. The web service requires SSL support. It is my understanding that AXIS2/c can be built with openSSL to have SSL support. I have two questions: (1) In the distribution of my

Re: [Axis2][Vote]Dinesh as Release Manager

Damitha Kumarage wrote: Hi devs, I would like to propose Dinesh Premalal as the release manager for Apache Axis2/C 1.3.1 release. Since he has already volunteered to do so I would like to call a vote here to confirm his role as RM. Since we have identified few problems, it is worth to fix th

Re: Improvements to Axis2/C Neethi-GSoC project

>>>Stmnt: First by providing operation and message level policy support at client side. What do u mean by client side? Operations are specified in the service side. So I think this should be related to service implementation. Thus the policies are mapped to operations in the service end. C

SOAP version in message context

Hi Devs, What's the rationale behind having the member axis2_bool_t is_soap_11 in the struct axis2_msg_ctx? I'd rather suggest int soap_version. This is to support the future SOAP versions. May be we can introduce new functions to the API axis2_msg_ctx_set/get_soap_version() and deprecate the

Re: Google Summer of Code - Implementation of the XPath specification in Axis/C

Hi Kapoor, IMO its better to document your API in a wiki. Something like this[1] we added for Apache Rampart/C. In that way other devs can also participate in the discussion and nobody will be lost in a mail thread. I think the page should be under http://wiki.apache.org/ws/axiom. (Devs please

Re: GSoC: XPath support for Axiom

Varuna Jayasiri wrote: Hi, I am an engineering undergraduate from University of Moratuwa and I am interested in working on the XPath project. There are a couple of things not clear for me about this project. I read the previous thread on this topic and found it very useful. I would like t

Re: MTOM sample failed !

Dinesh Premalal wrote: Hi Devs, For me MTOM sample gives a failure I tried it too. Failed :( -Kau , I'm not sure it is due to changes in HTTP transport. I'm looking into that problem now. thanks, Dinesh -- http://blog.kaushalye.org/ http://wso2.org/ -

Re: Error logs for AXIS2_ERROR_SET

Senaka Fernando wrote: Senaka Fernando wrote: Hi all, How about AXIS2_ERROR_SET_AND_LOG(env->error, ...) a new macro which combines the AXIS2_ERROR_SET() and AXIS2_LOG_ERROR(). What if we wanted to do more with this macro in the future? e.g. AXIS2_ERROR_SET_AND_LOG_AND_FOO_AND_BAR

Error logs for AXIS2_ERROR_SET

Hi, When we do AXIS2_ERROR_SET, we have to log an error message as well. In "some" situations we can use the same error message we set to the env->error for logging. Like this AXIS2_ERROR_SET(env->error, AXIS2_ERROR_MULTIPLE_CODE_ELEMENTS_ENCOUNTERED,

Re: [jira] Created: (AXIS2C-1013) Error in month in date_time

Senaka Fernando wrote: A late fix in axutil_date_time, has created an issue in handling the month of the day due to gmtime treating January as zero. The fix has been applied partially leaving a bug when we call the function axutil_date_time_create_with_offset(). We won't be fixing this for 1.3.0

Re: Exposing Transport Headers to a Service

Senaka Fernando wrote: On Feb 12, 2008 5:29 PM, Kaushalye Kapuruge <[EMAIL PROTECTED]> wrote: Senaka Fernando wrote: Hi again, Also adding to this discussion, we must be fair to REST users too, Kaushalye and that makes sense. :)... :) Yes. But still I do not

Re: Exposing Transport Headers to a Service

Dumindu Pallewela wrote: On Feb 12, 2008 5:29 PM, Kaushalye Kapuruge <[EMAIL PROTECTED]> wrote: Senaka Fernando wrote: Hi again, Also adding to this discussion, we must be fair to REST users too, Kaushalye and that makes sense. :)... :) Yes. But still I do not

Re: Exposing Transport Headers to a Service

Senaka Fernando wrote: Hi again, Also adding to this discussion, we must be fair to REST users too, Kaushalye and that makes sense. :)... :) Yes. But still I do not accept exposing the password even for REST users. I mean this is transport level authentication. The call come to the servic

Re: Exposing Transport Headers to a Service

Hi Senaka, The basic authentication is always recommended to use with a cryptographically secured connection. If not, it's not a difficult task to crack the username and password pair, which is in the form of base64 encoded text. So if the client/server must agreed upon the kind of transport t

Re: [AXIS2C] HTTP Basic Authentication question

effort[1]. HTH, Kau [1]http://wso2.org/library/2702#ut Thanks, -Dave. -Original Message- From: Kaushalye Kapuruge [mailto:[EMAIL PROTECTED] Sent: Monday, February 11, 2008 9:42 PM To: Apache AXIS C Developers List Subject: Re: [AXIS2C] HTTP Basic Authentication question Hi Dave, Please

Re: [AXIS2C] HTTP Basic Authentication question

Hi Dave, Please refer the Aixs2/C manual here[1] for more information on basic authentication. Cheers, Kauhsalye [1]http://ws.apache.org/axis2/c/docs/axis2c_manual.html#http_auth Dave Meier wrote: Hi All, With my gsoap web services I can get at the userid and password that are passed in the

Re: [Axis2] [Vote] Dinesh as Release Manager for Apache Axis2/C 1.3.0 Release

+1 -Kau Dumindu Pallewela wrote: +1. Regards, Dumindu. On Jan 31, 2008 2:23 PM, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote: Hi All, Looking at the new features we have, it looks like we could do 1.3.0 release, rather than doing a 1.2.1 patch release. I would like to propose Dinesh Pre

Re: 1.2.1 release

Dinesh Premalal wrote: Hi Dumindu, "Dumindu Pallewela" <[EMAIL PROTECTED]> writes: Why are we releasing 1.2.1 with all the features added after 1.2 release? Shouldn't it rather be in 1.3? I guess it will be more sensible if we released 1.2.1 with patches for issues identified with 1.2 relea

[jira] Closed: (AXIS2C-937) axiom_util_get_child_text() is not implemented

[ https://issues.apache.org/jira/browse/AXIS2C-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Malinda Kaushalye Kapuruge closed AXIS2C-937. - > axiom_util_get_child_text() is not implemen

[jira] Resolved: (AXIS2C-937) axiom_util_get_child_text() is not implemented

[ https://issues.apache.org/jira/browse/AXIS2C-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Malinda Kaushalye Kapuruge resolved AXIS2C-937. --- Resolution: Fixed Implemented. Now it's posisble to get text

Re: [Axis2][VOTE]Lahiru Gunathilake as a committer

+1. Kau Dinesh Premalal wrote: Hi Devs, I would like to propose Lahiru Gunathilake as an Axis2/C committer. Lahiru hascontributed a lot to improve Guththila parser and test many components in Axis2/C. Here [1] is some of the issues that he has worked on. I'm sure that he will be a resour

[jira] Assigned: (AXIS2C-937) axiom_util_get_child_text() is not implemented

[ https://issues.apache.org/jira/browse/AXIS2C-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Malinda Kaushalye Kapuruge reassigned AXIS2C-937: - Assignee: Malinda Kaushalye Kapuruge > axiom_util_get_child_t

Re: md5 in tools?

Samisa Abeysinghe wrote: I see that md5 implementation has been placed in tools, with separate build system. Should it not go to utl? It is a utility that we would use, and not a tool like tcpmon. +1 Thanks, Samisa... - To

[jira] Created: (AXIS2C-937) axiom_util_get_child_text() is not implemented

Versions: Current (Nightly) Environment: N/A Reporter: Malinda Kaushalye Kapuruge Fix For: Current (Nightly) axiom_util_get_child_text() function is specified in the header but not implemented in the src. -- This message is automatically generated by JIRA. - You

Re: [Axis2] Can we make Guththila the default parser?

Hi, Tested and works fine... :) -Kau Milinda Pathirage wrote: Hi devs, I tested Rampart/C with Axis2/c (guththila enabled). All the secpolicy samples were successful. I think above mentioned fix by supun has fixed the bugs in guththila when working with Rampart/C. Thanks, Milinda On Jan 24,

Re: [Axis2] [Vote] Dinesh as Release Manager for Apache Axis2/C 1.2.1 Release

Samisa Abeysinghe wrote: Hi All, I would like to propose Dinesh Premalal as the release manager for Apache Axis2/C 1.2.1 release. Since we have identified few glitches, it is worth to fix them with a patch release, along with any bugs we have fixed since the release of 1.2.0. Dine

Re: version incompatibilities

Samisa Abeysinghe wrote: Oops! That is a glitch :( We should add this to our check list in the release process Wiki. Devs, should we do a patch release fixing this? I think we should. +1 -Kau Thanks, Samisa... Michael Sutter wrote: Hello list, I have found two incompatibilities in versi

[jira] Assigned: (AXIS2C-931) ASF policy on cryptographic features

[ https://issues.apache.org/jira/browse/AXIS2C-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Malinda Kaushalye Kapuruge reassigned AXIS2C-931: - Assignee: Glen Daniels > ASF policy on cryptographic featu

Re: [Axis2] Can we make Guththila the default parser?

Hi, I tried with the svn head and had no luck. :(. The problem is still there. Seems the patch here[1] has already applied to the head. Can somebody shed some light on this? Is it necessary to re-open the issue? -Kau [1]https://issues.apache.org/jira/browse/AXIS2C-913 Kaushalye Kapuruge

Re: [Axis2] Can we make Guththila the default parser?

Hi Samisa, We had few issues running security samples with Guththila. Hope those are fixed by now. I will try build Axis2/C with guththila and engage Apache Ramaprt/C. Cheers, Kaushalye Samisa Abeysinghe wrote: Can we make Guththila the default parser in the future releases? Thanks, Samisa...

Re: ASF policy on cryptographic features

I raised a JIRA here[1]. -Kau [1]https://issues.apache.org/jira/browse/AXIS2C-931 Kaushalye Kapuruge wrote: Devs, Since Apache Axis2/C is having cryptographic features (for https support), it needs to be listed here[1] according to the ASF policy. Please find more details here[2]. This has to

[jira] Created: (AXIS2C-931) ASF policy on cryptographic features

: Current (Nightly) Environment: N/A Reporter: Malinda Kaushalye Kapuruge Fix For: 1.2.1 Since Apache Axis2/C is having cryptographic features (for https support), it needs to be listed here[1] according to the ASF policy. Please find more details here[2]. This has to

[jira] Commented: (AXIS2C-866) REOPEN - /util/src/base64.c incorrect calculation of length in 'axutil_base64_decode_len'

[ https://issues.apache.org/jira/browse/AXIS2C-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561603#action_12561603 ] Malinda Kaushalye Kapuruge commented on AXIS2C-866: --- I prefer the Op

ASF policy on cryptographic features

Devs, Since Apache Axis2/C is having cryptographic features (for https support), it needs to be listed here[1] according to the ASF policy. Please find more details here[2]. This has to be done by someone having site-dev karma (which includes all of the PMC chairs) Cheers, Kaushalye [1]http://

[jira] Commented: (AXIS2C-890) IssuedToken and SAMLToken assertion support for neethi

[ https://issues.apache.org/jira/browse/AXIS2C-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561580#action_12561580 ] Malinda Kaushalye Kapuruge commented on AXIS2C-890: --- Please link

Re: [RampartC] Code Freeze for 1.1.0 Release

Hi Devs, Apache Rampart/C code freeze is over. Cheers, Kaushalye Kaushalye Kapuruge wrote: Hi Devs, This is to announce a code freeze in the svn for the Apache Rampart/C version 1.1.0 release. During this code freeze, which will be starting from 11th January 2008 1200 hrs GMT, please refrain

Re: Axis2/c win32 BIN_DIR

Kasun Indrasiri wrote: Hi, In axis2c win32 configure file, the path to libraries such as LibXML, Zlib etc.should set to main directory (e.g. D:\libxml2-2.6.20.win32) but a new user may confused the BIN_DIR thing with (D:\libxml2-2.6.20.win32\bin ) unless he strictly follows the installtion gui

Re: [Axis2][VOTE]Senaka Fernando as a committer

+1, -Kau Milinda Pathirage wrote: Here's my +1. Thanks Milinda On Jan 16, 2008 8:00 PM, Supun Kamburugamuva <[EMAIL PROTECTED] > wrote: +1 Thanks Supun.. On Jan 17, 2008 8:59 AM, Sahan Gamage <[EMAIL PROTECTED] > wr

Re: [Rampart/C] [ANN] Apache Rampart/C 1.1.0 Released

ut. Cheers, Kaushalye Samisa Abeysinghe wrote: This release note does not mention with which release of Axis2/C it works :( Samisa... Kaushalye Kapuruge wrote: Hi All, Apache Rampart/C team is pleased to announce the release of Apache Rampart/C 1.1 You may download the release from http://ws.

[Rampart/C] [ANN] Apache Rampart/C 1.1.0 Released

Hi All, Apache Rampart/C team is pleased to announce the release of Apache Rampart/C 1.1 You may download the release from http://ws.apache.org/rampart/c/download.cgi Key features of the release --- 1. Ability to send and verify UsernameTokens with - U

Re: [Vote][Rampart-C] Vote for Apache Rampart/C 1.1.0 Release - Take 1

Hi Devs, We have got 11 votes for the Apache Rampart/C 1.1.0 release, including 3 PMC votes. There are no negative votes. The summary can be seen here[1]. So I will close the vote and proceed with the release. Thanks Kaushalye [1]http://markmail.org/message/ltji7jmg4yqrs5j7 Kaushalye Kapuruge

[Vote][Rampart-C] Vote for Apache Rampart/C 1.1.0 Release - Take 1

Hi Devs, I have uploaded the Apache Rampart/C 1.1.0 release artifacts here http://people.apache.org/~kaushalye/release/rampart-c/1.1.0 The key to verify the release artifacts can be found at http://people.apache.org/~kaushalye/release/KEYS Please test and review. If the released artifacts are f

[RampartC] Code Freeze for 1.1.0 Release

Hi Devs, This is to announce a code freeze in the svn for the Apache Rampart/C version 1.1.0 release. During this code freeze, which will be starting from 11th January 2008 1200 hrs GMT, please refrain from adding new features except bug fixes and documentations. Cheers, Kaushalye -- http://b

Re: [Vote] [Axis2-C] Vote for Apache Axis2/C 1.2.0 Release - Take 5

Dinesh Premalal wrote: Hi, Dinesh Premalal <[EMAIL PROTECTED]> writes: There is a bug in the generated site. It states latest version as 1.1.0 I think it is kind of minor bug. Since Axis2/C 1.2.0 release already delayed considerable time, I would suggest to go along with the vot

Re: [Axis2][VOTE]Bill Mitchell as a committer

+1 -Kau Milinda Pathirage wrote: Here's my +1 for Bill. Milinda On Jan 8, 2008 12:37 PM, Manjula Peiris <[EMAIL PROTECTED] > wrote: +1 -Manjula. On Tue, 2008-01-08 at 11:10 +0530, Sanjaya Ratnaweera wrote: > +1 > > ~sanjaya >

[jira] Commented: (AXIS2C-851) Frequently Asked Questions

[ https://issues.apache.org/jira/browse/AXIS2C-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556513#action_12556513 ] Malinda Kaushalye Kapuruge commented on AXIS2C-851: --- Yes we can.

Re: [Vote] [Axis2-C] Vote for Apache Axis2/C 1.2.0 Release - Take 1

Hi, Tried the source tar ball on linux. Also tested with Apache Rampart/C. All worked fine. Here is my +1. Cheers, Kau Damitha Kumarage wrote: Hi Devs, I have packaged and uploaded the Apache Axis2/C 1.2.0 release artifacts at http://people.apache.org/~damitha/release/axis2/1.2.0/ The key u

Re: Axis2/C FAQs

Question: How can I secure SOAP messages? Answer: To secure SOAP messages, you need to engage Apache Rampart/C[1], which can be downloaded from here[2]. Please refer the installation guide[3] and configuration guide[4] for more details. [1]http://ws.apache.org/rampart/c/ [2]http://ws.apache.org

Re: Axis2/C FAQs

Samisa Abeysinghe wrote: Spencer Davis wrote: I have been looking back through the users list and have been having some trouble finding things for he FAQ. I did find a few things that were either asked multiple times or they seemed like a lot of people would be interested in them and they could

[jira] Resolved: (AXIS2C-802) Non-optimized node to string

[ https://issues.apache.org/jira/browse/AXIS2C-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Malinda Kaushalye Kapuruge resolved AXIS2C-802. --- Resolution: Fixed Fixed. This is how to get non optimized data from

[jira] Created: (AXIS2C-802) Non-optimized node to string

Environment: N/A Reporter: Malinda Kaushalye Kapuruge Assignee: Malinda Kaushalye Kapuruge Fix For: Current (Nightly) Need to introduce a new function to convert an axiom_node to a string in a non-optimized way. This is required, when the user needs to get the

Re: MTOM and encryption

Dinesh Premalal wrote: Hi Kaushalye, Samisa Abeysinghe <[EMAIL PROTECTED]> writes: Kaushalye Kapuruge wrote: Hi List, We are experiencing some problems encrypting messages with optimized MTOM attachments. Say a client need to send an image(or binary content) in a confidenti

Re: MTOM and encryption

Thilina Gunarathne wrote: I do not understand why somebody need to encrypt MTOM attachment. Actually one of the main motivations behind introducing MTOM is the ability to secure the attachments. But when it comes to encryption, the serialization of the OM node (before the crypto proces

MTOM and encryption

Hi List, We are experiencing some problems encrypting messages with optimized MTOM attachments. Say a client need to send an image(or binary content) in a confidential way. And the optimization is set to TRUE. In a normal scenario, where *no encryption* is available, the image content is sent a

Selvaratnam Uthaiyashankar as a committer

Hi list, I would like to propose Selvaratnam Uthaiyashankar as an Apache Axis2/C committer. He has contributed to Apache Rampart/C by writing the key derivation module, which is very essential for WS Security and WS Secure Conversation scenarios. This follows all his efforts in implementing W

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

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

Re: [Fwd: svn commit: r590625 - /webservices/axis2/trunk/c/util/src/base64.c]

Samisa Abeysinghe wrote: Kaushalye, Please let the users know that you have done this change. I comment on the JIRA issue[1]. Anyways will drop a mail too. I think there was a mail on the user list on if this change would be done or now as well as how to use this function. No diversion fr

[jira] Commented: (AXIS2C-731) /util/src/base64.c incorrect calculation of length in 'axutil_base64_decode_len'

[ https://issues.apache.org/jira/browse/AXIS2C-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539057 ] Malinda Kaushalye Kapuruge commented on AXIS2C-731: --- I've tested the code. It worked fin

Re: [Axis2] Improvement to the way we use the repo

Deepal jayasinghe wrote: Kaushalye Kapuruge wrote: Samisa Abeysinghe wrote: Hi All, At the moment, we place all our stuff in the repo. Given the repo location, one can find the axis2.xml, services and modules folders etc. However, I think that this is quite limiting and

Re: [Axis2] Improvement to the way we use the repo

Samisa Abeysinghe wrote: Hi All, At the moment, we place all our stuff in the repo. Given the repo location, one can find the axis2.xml, services and modules folders etc. However, I think that this is quite limiting and inflexible at times. Say you want to have two different deployments w

Re: [Axis2] Improvement to the way we use the repo

Deepal jayasinghe wrote: If we are going to specifiy each and every service and its location in the axis2.xml hot deployement won't work. What are we talking about , are we going to specify all the services in axis2.xml. I am not going to agree with that , if we are going to do so , then w

Re: [Vote] [Savan-C] Vote for Apache Savan/C 0.90 Release - Take 3

+1. -Kau Dinesh Premalal wrote: +1 thanks, Dinesh -- http://kaushalye.blogspot.com/ http://wso2.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

[Rampart/C] [ANN] Apache Rampart/C 1.0.0 Released

Hi All, Apache Rampart/C team is pleased to announce the release of Apache Rampart/C 1.0. You may download the release from http://ws.apache.org/rampart/c/download.cgi Key features of the release 1. Ability to send and verify UsernameTokens with - PlainText password - Digested password

Re: [Vote][Rampart-C] Vote for Apache Rampart/C 1.0.0 Release - Take 2

Hi Devs, We have got 12 votes for the 1.0 release including 3 PMC votes. There are no negative votes. Please refer the summary[1]. So I will close the vote and proceed with the release. Cheers, Kaushalye [1]http://marc.info/?t=11912268161&r=1&w=2 Kaushalye Kapuruge wrote: Hi Devs,

Re: [Vote] [Sandesha2/C] For Apache Sandesha2/C 0.91 Release - Take 3

+1. Cheers, Kaushalye Chamikara Jayalath wrote: +1 Chamikara On 10/2/07, *Dushshantha Chandradasa* <[EMAIL PROTECTED] > wrote: here is my +1 Regards, Dushshantha and uploaded the second set of Apache Sandesha2/C 0.91 release artifa

Re: [Axis2] Next release 1.1.1 or 1.2.0?

+1 for 1.2 I think it's inevitable when Neethi/C is getting matured. Unless Neethi/C become a separate project. (Which I don't see as an important step at this moment). Cheers, Kau Manjula Peiris wrote: On Thu, 2007-10-04 at 08:54 +0600, Samisa Abeysinghe wrote: Dinesh Premalal wrote:

[Vote][Rampart-C] Vote for Apache Rampart/C 1.0.0 Release - Take 2

Hi Devs, I have re-packaged and uploaded the Apache Rampart/C 1.0.0 release artifacts here http://people.apache.org/~kaushalye/release/rampart-c/1.0.0-2/ This is after fixing issues of the previous set of artifacts. [Thank all for reporting those issues] The key to verify the release artifa

Re: [Vote] [Axis2] Vote for Apache Axis2/C 1.1.0 Release - Take 3

Tested on Debian GNU/Linux 4.0. +1 -Kaushalye Samisa Abeysinghe wrote: Hi Devs, After fixing the issues found with the second set of release artifacts, I have re-packaged and uploaded the third set of Apache Axis2/C 1.1.0 release artifacts at http://people.apache.org/~samisa/1.1.0-3/

[Vote][Rampart-C]Vote for Apache Rampart/C 1.0.0 Release

Hi Devs, I have packaged and uploaded the Apache Rampart/C 1.0.0 release artifacts at http://people.apache.org/~kaushalye/release/rampart-c/1.0.0/ The key to verify the release artifacts can be found at http://people.apache.org/~kaushalye/release/KEYS Please test and review. If the released a

Re: [Vote] [Axis2] Vote for Apache Axis2/C 1.1.0 Release

Tested on Debian 4.0. Also tested with Rampart/C. All the security scenarios worked fine. Here is my +1. Cheers, Kaushalye Samisa Abeysinghe wrote: Hi Devs, I have packaged and uploaded the Apache Axis2/C 1.1.0 release artifacts at http://people.apache.org/~samisa/1.1.0/ The key use

[jira] Assigned: (AXIS2C-695) memory leak fixes in directory handler

[ https://issues.apache.org/jira/browse/AXIS2C-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Malinda Kaushalye Kapuruge reassigned AXIS2C-695: - Assignee: Malinda Kaushalye Kapuruge > memory leak fixes

Re: Savan/C 0.90 release

+1, Kau Damitha Kumarage wrote: Hi devs, Since Savan/C development has continued for some time and seems ripe enough to be packed into a release I propose we do a Savan/C 0.90 release. I would like to be the release manager. Currently following features are implemented 1. Support for WS-E

Re: Sandesha2/C 0.91 release

+1. Cheers, Kau Manjula Peiris wrote: Hi devs, It is sometime back we have done the Sandesha2/C 0.90 release. Since Axis2/C 1.1 release will happen , I propose we do a Sandesha2/C 0.91 release. I would like to be the release manager. Your suggestions are welcome. Thanks, -Manjula.

Re: [Rampart/C] SAML Support?

Manjula Peiris wrote: Hi Jamie, See my commnets in line. On Tue, 2007-08-21 at 11:58 +0100, Jamie Lyon wrote: Hi, See my reply below. -Original Message- I now still have the problem of actually setting the SAML token. All the functions to do so are in

Re: [Rampart/C] SAML Support?

he username? Or is it not possible, and the username can only be set within a policy? Thanks, Jamie -Original Message- From: Kaushalye Kapuruge [mailto:[EMAIL PROTECTED] Sent: 16 August 2007 11:47 To: Apache AXIS C Developers List Subject: Re: [Rampart/C] SAML Support? Hi Jamie, Rampart

Re: [Rampart/C] SAML Support?

Hi Jamie, Rampart/C still doesn't have the SAML support. But it's definitely something we have planned to do(Problem is when:) ). If you like to have it implemented by yourself, only for the client side, it's not that difficult. Please have a look at the function rampart_shb_build_message() in

Re: Error: "Key Reference Info is mismatch with policy"?

Hi Jamie, In Rampart/C v 0.90, we had implemented it in such a way that user can specify different policies for incoming and outgoing messages. But after that we changed it to be compatible with other implementations, mainly due to the interoperability between different policy frameworks. I als

[jira] Created: (AXIS2C-661) There is no OM model in generated payloads. Thus failing C14N.

Components: code generation Affects Versions: 1.1.0 Environment: UNIX, Win32 Reporter: Malinda Kaushalye Kapuruge Fix For: 1.1.0 When the code generation tool is used, the AXIOM model fails to give the child nodes. This causes problems to the C14N algorithm in

Re: [Rampart/C] Generating incorrect digests?

: This works perfectly, thanks very much! Cheers, Jamie -Original Message- From: Kaushalye Kapuruge [mailto:[EMAIL PROTECTED] Sent: 01 August 2007 06:30 To: Apache AXIS C Developers List Subject: Re: [Rampart/C] Generating incorrect digests? Hi Jamie, It appears to me that the tcp log

Re: [Rampart/C] Generating incorrect digests?

Hi Jamie, It appears to me that the tcp log and the server log don't tally. The tcp-log shows attribute in Timestamp as u:Id whilst the server-log shows wsu:Id. May be the server expects attribute to be with wsu: prefix. Could you please try this... 1. Open RAMPART/src/util/rampart_signature.c 2

Re: [Rampart/C] Generating incorrect digests?

Hi, See my comments in-line... Cheers, Kaushalye Jamie Lyon wrote: Hi, I’m trying to get a client signing messages to work with a server using Axis1/WSS4J. I’ve successfully got Rampart/C set up, and have the client signing messages, however the digests are failing to verify for all items

  1   2   3   4   >