[jira] [Commented] (AXIS2-5023) Ambigious use of isElementData in the Block interface

[ https://issues.apache.org/jira/browse/AXIS2-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030589#comment-13030589 ] Ivan commented on AXIS2-5023: - I am thinking to add a new method isElementDataOnly(), it retur

[jira] [Created] (AXIS2-5023) Ambigious use of isElementData in the Block interface

Ambigious use of isElementData in the Block interface - Key: AXIS2-5023 URL: https://issues.apache.org/jira/browse/AXIS2-5023 Project: Axis2 Issue Type: Bug Components: jaxws

[jira] [Issue Comment Edited] (AXIS2-5001) SOAPMessage.getSOAPHeaders() return null while no headers in the soap envelope

[ https://issues.apache.org/jira/browse/AXIS2-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030587#comment-13030587 ] Ivan edited comment on AXIS2-5001 at 5/9/11 2:48 AM: - I also checked a

[jira] [Commented] (AXIS2-5001) SOAPMessage.getSOAPHeaders() return null while no headers in the soap envelope

[ https://issues.apache.org/jira/browse/AXIS2-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030587#comment-13030587 ] Ivan commented on AXIS2-5001: - I also checked all SAAJ, JAX-WS and even SOAP spec in the past,

Re: Axis2 Transport build error

This is happen when I run "mvn clean install " while apache-release profile is activated on ~/.m2/settings.xml file. Thanks ! On Mon, May 9, 2011 at 1:33 AM, Andreas Veithen wrote: > What is the exact Maven command that you are trying to execute? > > Andreas > > On Thu, May 5, 2011 at 09:14,

[jira] [Commented] (AXIS2-5022) Support addressing meta data with policy 1.5 framework

[ https://issues.apache.org/jira/browse/AXIS2-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030570#comment-13030570 ] Ivan commented on AXIS2-5022: - Before creating the patch, I checked those sub modules in curre

[jira] [Commented] (AXIS2-5021) Extra slash is added for wsdl access address

[ https://issues.apache.org/jira/browse/AXIS2-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030562#comment-13030562 ] Ivan commented on AXIS2-5021: - Hehe, should clearly refer the spec, :-) ---> Spec 5.2.2 Confor

Re: [VOTE] [AXIS2] Release Axis2-1.6.0

I noticed that there a couple of license files missing in the legal directory. Except from that, I think that the 1.5 and 1.6 branches are in a releasable state. I believe that I have addressed most of the issues related to the samples and reported previously in this thread. The 1.5 branch also co

Re: Axis2 Transport release ?

On Wed, May 4, 2011 at 20:22, Sagara Gunathunga wrote: > Hi all , > > Recently we agreed to release Axis2 , Sandesha and Rampart > simultaneously.  IMO it's better to release Axis2-transport also with > above releases. > > In addition specially in users point of view it's better to match > transpo

Re: Axis2 Transport build error

What is the exact Maven command that you are trying to execute? Andreas On Thu, May 5, 2011 at 09:14, Sagara Gunathunga wrote: > I'm getting following error when building Transport trunk testkit module. > > [INFO] MavenReportException: Error while creating archive:Exit code: 1 > - javadoc: error

[jira] [Commented] (RAMPART-40) implementation of the Xpath support

[ https://issues.apache.org/jira/browse/RAMPART-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030536#comment-13030536 ] Andreas Veithen commented on RAMPART-40: There is something fundamentally wrong wi

[jira] [Commented] (AXIS2-5013) Issue in Mail transport for In-Out MEP

[ https://issues.apache.org/jira/browse/AXIS2-5013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030522#comment-13030522 ] Andreas Veithen commented on AXIS2-5013: Can you show us the code that prints the

[jira] [Commented] (AXIS2-5021) Extra slash is added for wsdl access address

[ https://issues.apache.org/jira/browse/AXIS2-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030521#comment-13030521 ] Andreas Veithen commented on AXIS2-5021: Ivan, can you please fix the issue descri

[jira] [Commented] (AXIS2-5001) SOAPMessage.getSOAPHeaders() return null while no headers in the soap envelope

[ https://issues.apache.org/jira/browse/AXIS2-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030517#comment-13030517 ] Andreas Veithen commented on AXIS2-5001: That sounds like a workaround that doesn'

[jira] [Commented] (AXIS2-5022) Support addressing meta data with policy 1.5 framework

[ https://issues.apache.org/jira/browse/AXIS2-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030516#comment-13030516 ] Andreas Veithen commented on AXIS2-5022: By design, Axis2 is able to engage module

[jira] [Updated] (AXIS2-3316) Control whether a WSDL is returned when ?wsdl comes in - both at service level and global level

[ https://issues.apache.org/jira/browse/AXIS2-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-3316: --- Fix Version/s: 1.6.0 > Control whether a WSDL is returned when ?wsdl comes in - both at serv

Re: block ?wsdl url

Yes, it is on the way. Probably it should be available by the end of this month. On Sun, May 8, 2011 at 10:35 AM, Peeyush Tuli < [email protected]> wrote: > Thanks for the reply, > > Is there a scheduled date for the next release of axis2 as of now? > > Thanks, > Peeyush > > On May

[jira] [Updated] (AXIS2-5022) Support addressing meta data with policy 1.5 framework

[ https://issues.apache.org/jira/browse/AXIS2-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated AXIS2-5022: Attachment: AXIS2-5022.patch Attach a draft patch, and it works in my local environment. Some of TCK cases related

Re: block ?wsdl url

An RC build is available here. http://people.apache.org/~ruwan/axis2/dist/1.6.0/ Please check it out and let us know whether your requirement is fulfilled. On Sun, May 8, 2011 at 7:34 PM, Afkham Azeez wrote: > Yes, it is on the way. Probably it should be available by the end of this > month. >

[jira] [Created] (AXIS2-5022) Support addressing meta data with policy 1.5 framework

Support addressing meta data with policy 1.5 framework -- Key: AXIS2-5022 URL: https://issues.apache.org/jira/browse/AXIS2-5022 Project: Axis2 Issue Type: Bug Components: Addressi

[jira] [Commented] (AXIS2-5001) SOAPMessage.getSOAPHeaders() return null while no headers in the soap envelope

[ https://issues.apache.org/jira/browse/AXIS2-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030487#comment-13030487 ] Ivan commented on AXIS2-5001: - Hi, Andreas, thanks for following this issue. From my investiga

[jira] [Updated] (AXIS2-5021) Extra slash is added for wsdl access address

[ https://issues.apache.org/jira/browse/AXIS2-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated AXIS2-5021: Attachment: AXIS2-5021.patch Attach a patch to remove the extra slash in the wsdl address. > Extra slash is added

[jira] [Created] (AXIS2-5021) Extra slash is added for wsdl access address

Extra slash is added for wsdl access address Key: AXIS2-5021 URL: https://issues.apache.org/jira/browse/AXIS2-5021 Project: Axis2 Issue Type: Bug Components: jaxws Affects Versions: