[jira] Assigned: (AXIS2C-896) Implementation of Digest Authentication Scheme in Axis2/C

[ https://issues.apache.org/jira/browse/AXIS2C-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dumindu Pallewela reassigned AXIS2C-896: Assignee: Dumindu Pallewela Implementation of Digest Authentication Scheme in

Invailability of sed command on Windows addressed

Hi devs, It is a known fact that we can't use the sed command on windows unless you install an add-on. Under these circumstances we have burdened our users to do appropriate replacements so that the sed command wouldn't be necessary. The Rampart/C secpolicy set of samples is a good example.

[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-tabpanelfocusedCommentId=12559072#action_12559072 ] Samisa Abeysinghe commented on AXIS2C-866: -- Oops, this is a mishap. I know this

[Axis2] Release date on site incorrect

It says: 30th September 2007 - Apache Axis2/C Version 1.2.0 Released Can someone please fix this. I cannot checkout the site right now form my machine and I do not have maven to generate site, else I would have fixed this :( Thanks, Samisa...

Re: [Axis2] Release date on site incorrect

Samisa Abeysinghe wrote: It says: 30th September 2007 - Apache Axis2/C Version 1.2.0 Released Can someone please fix this. I cannot checkout the site right now form my machine and I do not have maven to generate site, else I would have fixed this :( Also, the bug fix link

Re: Invailability of sed command on Windows addressed

Hi Senaka, Is this a problem anywhere outside secpolicy samples? in secpolicy samples, however, this cannot be done without sed like functionality, because we need to set the paths inside certain files according to the install path that is defined at the build-time. Do you see any other way out

Re: Invailability of sed command on Windows addressed

On Tue, 2008-01-15 at 07:54 -0500, Senaka Fernando wrote: Hi devs, It is a known fact that we can't use the sed command on windows unless you install an add-on. Under these circumstances we have burdened our users to do appropriate replacements so that the sed command wouldn't be necessary.

Re: Invailability of sed command on Windows addressed

I don't think that it has been an issue beyond secpolicy AFAIK, but, I will try installing it in a different location to be sure about that. Option No.2 is to use another environment variable (ex:- %SECPOLICY_SAMPLE_HOME%) which in fact would invariably be a windows specific one. In the Linux

Re: AW: execute axiom_document_free(om_document, env); // and my hash_table key/val pairs are gone

Hi Josef, The builder document logic is as follows. The document will always have a builder and the builder is responsible for creating the document. That is why it doesn't make sense to free only the document. Reconstructing a document would involve reconstructing a builder. It would be better

Re: [Axis2] Release date on site incorrect

Also please note that http://ws.apache.org/axis2/c/docs/hello/service/hello_svc.c.html is still not found on the site. Please take a look at that too. Regards, Senaka Samisa Abeysinghe wrote: It says: 30th September 2007 - Apache Axis2/C Version 1.2.0 Released Can someone please fix this. I

Re: [Axis2] Release date on site incorrect

Hi all, The Manual on the site is not updated. Also I believe that the installation guide seems to be the old one. Please take a look into other documentation, links etc. too. Regards, Senaka Also please note that http://ws.apache.org/axis2/c/docs/hello/service/hello_svc.c.html is still not

[jira] Resolved: (AXIS2C-896) Implementation of Digest Authentication Scheme in Axis2/C

[ https://issues.apache.org/jira/browse/AXIS2C-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dumindu Pallewela resolved AXIS2C-896. -- Resolution: Fixed Fix Version/s: 1.2.1 Patch committed at revision 612211.

[jira] Resolved: (AXIS2C-733) Validating the server certificate should not be mandatory

[ https://issues.apache.org/jira/browse/AXIS2C-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dumindu Pallewela resolved AXIS2C-733. -- Resolution: Fixed Fix Version/s: Current (Nightly) Instead of giving an option

Re: Invailability of sed command on Windows addressed

Should we not discuss this on rampart list? Samisa... Dumindu Pallewela wrote: Hi Senaka, Is this a problem anywhere outside secpolicy samples? in secpolicy samples, however, this cannot be done without sed like functionality, because we need to set the paths inside certain files according

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

Hi all, I tested Source Distribution on Ubuntu 7.10. All the secpolicy samples worked well. Here's my +1. Thanks Milinda... On Jan 15, 2008 11:41 AM, Sanjaya Ratnaweera [EMAIL PROTECTED] wrote: +1 Thanks ~sanjaya Samisa Abeysinghe wrote: +1. Samisa... Manjula Peiris wrote:

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

Hi, Here is my +1. Thanks, Supun.. On Jan 15, 2008 4:15 PM, Milinda Pathirage [EMAIL PROTECTED] wrote: Hi all, I tested Source Distribution on Ubuntu 7.10. All the secpolicy samples worked well. Here's my +1. Thanks Milinda... On Jan 15, 2008 11:41 AM, Sanjaya Ratnaweera [EMAIL

Re: Invailability of sed command on Windows addressed

Hi, We have started discussion on rampart-dev list with the same subject. Please follow it. Regards, Shankar. Samisa Abeysinghe wrote: Should we not discuss this on rampart list? Samisa... Dumindu Pallewela wrote: Hi Senaka, Is this a problem anywhere outside secpolicy samples? in

[jira] Updated: (AXIS2C-899) zlib library should not be included when AXIS2_ARCHIVE_ENABLED is false.

[ https://issues.apache.org/jira/browse/AXIS2C-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diluka Moratuwage updated AXIS2C-899: - Attachment: zlib.patch When AXIS2_ARCHIVE_ENABLED is false, zlib is not needed to be

[jira] Commented: (AXIS2C-828) MTOM Sample failed with Libcurl (HTTP) transport

[ https://issues.apache.org/jira/browse/AXIS2C-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559350#action_12559350 ] Dinesh Premalal commented on AXIS2C-828: Senaka, Applied and tested your patch

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

+1 thanks, Dinesh -- http://nethu.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

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

+1 -Deepal Hi, Here is my +1. Thanks, Supun.. On Jan 15, 2008 4:15 PM, Milinda Pathirage [EMAIL PROTECTED] wrote: Hi all, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL

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

+1 Thanks, Ruchith On Jan 11, 2008 5:54 PM, Kaushalye Kapuruge [EMAIL PROTECTED] wrote: 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

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

+1 Thanks Nandika On Jan 16, 2008 10:51 AM, Ruchith Fernando [EMAIL PROTECTED] wrote: +1 Thanks, Ruchith On Jan 11, 2008 5:54 PM, Kaushalye Kapuruge [EMAIL PROTECTED] wrote: Hi Devs, I have uploaded the Apache Rampart/C 1.1.0 release artifacts here

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

Re: svn commit: r612034 - in /webservices/axis2/trunk/java/modules/clustering/src/org/apache/axis2/clustering/tribes: MembershipManager.java TribesClusterManager.java

Azeez, Is there any chance you could take a look at why the continuum build[1] is failing? [1] http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuildbuildId=4789id=61 On Jan 15, 2008 7:45 AM, [EMAIL PROTECTED] wrote: Author: azeez Date: Mon Jan

[jira] Resolved: (AXIS2-3283) No access to the operationContextMap in the ConfigurationContext class

[ https://issues.apache.org/jira/browse/AXIS2-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Illsley resolved AXIS2-3283. -- Resolution: Fixed Fix Version/s: nightly Assignee: David Illsley (was: Deepal

[jira] Created: (AXIS2-3446) How to Capture the Server Side Session Value From Axis Client

How to Capture the Server Side Session Value From Axis Client - Key: AXIS2-3446 URL: https://issues.apache.org/jira/browse/AXIS2-3446 Project: Axis 2.0 (Axis2) Issue Type: Task

[jira] Updated: (AXIS2-3446) How to Capture the Server Side Session Value From Axis Client

[ https://issues.apache.org/jira/browse/AXIS2-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sudheer anumalasetty updated AXIS2-3446: Description: Hi everyone: I have a situation like this My Service resides in

[jira] Commented: (AXIS2-1804) Error in generated WSDL file - wsaw namespace

[ https://issues.apache.org/jira/browse/AXIS2-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559076#action_12559076 ] Martin Gainty commented on AXIS2-1804: -- this was never fixed axis-2.1.3 All I want to

[jira] Created: (AXIS2-3447) CLONE -Error in generated WSDL file - wsaw namespace

CLONE -Error in generated WSDL file - wsaw namespace Key: AXIS2-3447 URL: https://issues.apache.org/jira/browse/AXIS2-3447 Project: Axis 2.0 (Axis2) Issue Type: Bug Components:

[jira] Commented: (AXIS2-3447) CLONE -Error in generated WSDL file - wsaw namespace

[ https://issues.apache.org/jira/browse/AXIS2-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559078#action_12559078 ] Martin Gainty commented on AXIS2-3447: -- this was never fixed axis-2.1.3 All I want

Re: [Axis2] JAXWS version in Axis2 1.4

Some discussion on jcp-open as well. [4] http://news.gmane.org/gmane.comp.apache.jcp%2dopen -- dims On Jan 15, 2008 11:17 AM, Davanum Srinivas [EMAIL PROTECTED] wrote: Glen, Sandakith, Jeff, Nick, Rich, - I believe the jaxws-tck svn and the associated mailing list is ready. - cxf folks i am

[Axis2] JAXWS version in Axis2 1.4

Glen, Sandakith, Jeff, Nick, Rich, - I believe the jaxws-tck svn and the associated mailing list is ready. - cxf folks i am told are running JAXWS 2.1 TCK - Sun posted JDK 1.6 update 4 with JAXWS 2.1 inside. So, what should we do for Axis2 1.4? I just saw Nick's jira float by [1] and wanted to

[jira] Created: (AXIS2-3448) JAX-WS 2.1: Support @MTOM and MTOMFeature

JAX-WS 2.1: Support @MTOM and MTOMFeature - Key: AXIS2-3448 URL: https://issues.apache.org/jira/browse/AXIS2-3448 Project: Axis 2.0 (Axis2) Issue Type: New Feature Components: jaxws

[jira] Work started: (AXIS2-3448) JAX-WS 2.1: Support @MTOM and MTOMFeature

[ https://issues.apache.org/jira/browse/AXIS2-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on AXIS2-3448 started by Nick Gallardo. JAX-WS 2.1: Support @MTOM and MTOMFeature - Key: AXIS2-3448

[jira] Created: (AXIS2-3449) JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature

JAX-WS 2.1: Support @RespectBinding and RespectBindingFeature - Key: AXIS2-3449 URL: https://issues.apache.org/jira/browse/AXIS2-3449 Project: Axis 2.0 (Axis2) Issue Type: New

Re: [Axis2] JAXWS version in Axis2 1.4

Dims, Thanks for starting the discussion. I wasn't aware of jcp-open. It's good to know there's an open forum for that information. Wrt. Axis2 1.4, my vote is that we certify based on JAX-WS 2.1 rather than 2.0. Brian has done a large amount of work in the jaxws21 branch. We can merge that

Re: [Axis2] JAXWS version in Axis2 1.4

Hi Dims, Nick It would be good to get the code that is currently in the jaxws21 branch moved over to the trunk asap. There is also an existing JIRA to cover the JAX-WS 2.1 development in general, http://issues.apache.org/jira/browse/AXIS2-2722 Cheers Brian DePradine Web Services Development

[jira] Created: (AXIS2-3450) wsdl2code maven2 plugin outputDirectory not properly used.

wsdl2code maven2 plugin outputDirectory not properly used. Key: AXIS2-3450 URL: https://issues.apache.org/jira/browse/AXIS2-3450 Project: Axis 2.0 (Axis2) Issue Type: Bug

[jira] Created: (AXIS2-3451) Example maven2 configuration is broken.

Example maven2 configuration is broken. --- Key: AXIS2-3451 URL: https://issues.apache.org/jira/browse/AXIS2-3451 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: documentation

[jira] Created: (AXIS2-3452) wsdl2code maven2 plugin should not generate build.xml file.

wsdl2code maven2 plugin should not generate build.xml file. --- Key: AXIS2-3452 URL: https://issues.apache.org/jira/browse/AXIS2-3452 Project: Axis 2.0 (Axis2) Issue Type: Improvement

[jira] Commented: (AXIS2-3172) Multiple ports in WSDL not supported

[ https://issues.apache.org/jira/browse/AXIS2-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12559344#action_12559344 ] Philip Kirkland commented on AXIS2-3172: Boyan did you manage to resolve this? I'm

Re: [Axis2] JAXWS version in Axis2 1.4

Hi Dims , Nick, Rich, - I believe the jaxws-tck svn and the associated mailing list is ready. - cxf folks i am told are running JAXWS 2.1 TCK - Sun posted JDK 1.6 update 4 with JAXWS 2.1 inside. So, what should we do for Axis2 1.4? I just saw Nick's jira float by [1] and wanted to kick

Re: svn commit: r612034 - in /webservices/axis2/trunk/java/modules/clustering/src/org/apache/axis2/clustering/tribes: MembershipManager.java TribesClusterManager.java

The test failure is not due to this commit. However, it seems like there are communication problems between nodes, may be due to some settings on that machine. So I've added a property, run.clustering.tests, which defaults to false. Thanks Azeez On Jan 15, 2008 2:10 PM, David Illsley [EMAIL

Recent work on clustering

Hi Folks, You may have noticed that there has been some new work going on in the Axis2 clustering implementation. Here is a summary of what has been taking place in the recent past: 1. Introduced RpcChannel - This is a blocking request-response communication

Re: svn commit: r612034 - in /webservices/axis2/trunk/java/modules/clustering/src/org/apache/axis2/clustering/tribes: MembershipManager.java TribesClusterManager.java

Excellent. Thanks! David On Jan 16, 2008 5:54 AM, Afkham Azeez [EMAIL PROTECTED] wrote: The test failure is not due to this commit. However, it seems like there are communication problems between nodes, may be due to some settings on that machine. So I've added a property,