[jira] Created: (AXIS2-4832) Modules not getting loaded from classpath in BEA Weblogic 10.x

Modules not getting loaded from classpath in BEA Weblogic 10.x -- Key: AXIS2-4832 URL: https://issues.apache.org/jira/browse/AXIS2-4832 Project: Axis2 Issue Type: Bug Comp

Hudson build became unstable: axis2-transports-trunk #182

See - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org

Build failed in Hudson: Rampart #100

See -- Failed to access build log hudson.util.IOException2: remote file operation failed: /home/hudson/hudson-slave/workspace/Rampart at hudson.remoting.chan...@7ed80b73:ubuntu1 at hudson.FilePat

Hudson build became unstable: axis2-transpor ts-trunk » Apache Axis2 - Transport - Sms #182

See - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apac

Build failed in Hudson: Axis2-trunk-java-1.6 #168

See -- Failed to access build log hudson.util.IOException2: remote file operation failed: /home/hudson/hudson-slave/workspace/Axis2-trunk-java-1.6 at hudson.remoting.chan...@7ed80b73:ubuntu1

Hudson build is back to stable : Axis2-trunk-java-1.6 #167

See - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org

Hudson build is back to stable : Axis2-trunk-java -1.6 » Apache Axis2 - JAXWS Integration Tests #167

See - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.ap

Hudson build is back to normal : Axis2 #389

See - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org

Hudson build is back to normal : Axis2 » Apache Axis2 - CORBA #389

See - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org

How to remove the soapenv:mustUnderstand attribute

Hi, I'm using release 1.5.1 and I have to remove the soapenv:mustUnderstand attribute from my header SOAP message. I tried to do this in earlier versions with no success. How can I do this? Any clue will be very helpful. I'm sending below a sample SOAP Envelope with the attribute. http:

[jira] Commented: (AXIS2-4311) Axis2 OSGi bundles have split packages

[ https://issues.apache.org/jira/browse/AXIS2-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915450#action_12915450 ] Ancoron Luciferis commented on AXIS2-4311: -- What about fragment/extension bundles?

Build failed in Hudson: Axis2 » Apache Axis2 - CORBA #388

See -- [INFO] [INFO] Building Apache Axis2 - CORBA [INFO]task-segment: [clean, deploy] [INFO] ---

Build failed in Hudson: Axis2 #388

See Changes: [scheu] AXIS2-4831 Contributor: Rich Scheuerle Summary: SWA attachment may not be added if the MTOMXMLStreamWriter is not used [veithen] Explicitly specify the version of maven-default-skin to avoid the failure we have seen

[jira] Commented: (AXIS2-4818) Inheritance on method parameters not working

[ https://issues.apache.org/jira/browse/AXIS2-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915380#action_12915380 ] Chetan Saundankar commented on AXIS2-4818: -- Auto generated wsdl did not contain em

Re: [VOTE] Release Axis2 1.5.2

The individual JAR files for 1.5.3-SNAPSHOT are available from our snapshot repository: http://repository.apache.org/snapshots/org/apache/axis2/ Andreas On Mon, Sep 27, 2010 at 18:06, Raghu Upadhyayula wrote: > Thanks Andreas.  I've seen the JIRA updated email for Axis2-4465.  I'll try > the A

Re: svn commit: r991441 - /axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/description/java2wsdl/Java2WSDLConstants.java

Isuru, Actually, the proper way of doing this is to configure an ExtensionRegistry on the WSDLReader so that WSDL4J knows what is the expected type for the wsas:Action attribute (otherwise it will try to guess the attribute type, and this fails in this particular case). Here is the code that shoul

Re: [VOTE] Release WSS4J 1.5.9 [attn Rampart devs]

Hi Colm, all, Thanks for the push of this release - I'll take a look at the artifacts later this afternoon. One question to you and to the Rampart devs, which is of course "has this been tested with Rampart?" Thanks, --Glen On 9/27/2010 11:57 AM, Colm O hEigeartaigh wrote: > To the Apache Web S

RE: [VOTE] Release Axis2 1.5.2

Thanks Andreas. I've seen the JIRA updated email for Axis2-4465. I'll try the Axis2 1.5.3-SNAPSHOT. Where can I get 1.5.3-SNAPSHOT?? Thanks Raghu -Original Message- From: Andreas Veithen [mailto:andreas.veit...@gmail.com] Sent: Sunday, September 26, 2010 10:18 AM To: java-dev@axis

Re: [jira] Commented: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

Rich, IMO this approach of opening an issue just to record a commit is really not appropriate ... that's not what we use JIRA for! Sanjiva. On Mon, Sep 27, 2010 at 9:08 PM, Andreas Veithen (JIRA) wrote: > >[ > https://issues.apache.org/jira/browse/AXIS2-4828?page=com.atlassian.jira.plugin.sy

[jira] Resolved: (AXIS2-4831) JAX-WS:Occasionally a SWA style attachment is not marshaled

[ https://issues.apache.org/jira/browse/AXIS2-4831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Scheuerle resolved AXIS2-4831. --- Resolution: Fixed > JAX-WS:Occasionally a SWA style attachment is not marshaled > ---

[jira] Commented: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

[ https://issues.apache.org/jira/browse/AXIS2-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915335#action_12915335 ] Andreas Veithen commented on AXIS2-4828: Rich, it would be nice if before marking a

[jira] Created: (AXIS2-4831) JAX-WS:Occasionally a SWA style attachment is not marshaled

JAX-WS:Occasionally a SWA style attachment is not marshaled --- Key: AXIS2-4831 URL: https://issues.apache.org/jira/browse/AXIS2-4831 Project: Axis2 Issue Type: Bug Reporter

[jira] Resolved: (AXIS2-4828) SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when doing SWA

[ https://issues.apache.org/jira/browse/AXIS2-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Scheuerle resolved AXIS2-4828. --- Resolution: Fixed > SOAPMessageFormatter should buffer the SOAP Body in an OutputStream when

Re: [Axis2] Creation of the 1.6 branch

Hi, These days I'm in a client site and really busy with my daytime job and I don't think I can release Woden myself until mid December , It would be great if any one else willing to be a RM for Woden this time. Since last few months Woden code base is stable and ready for next release, I was st

Re: [Axis2] Creation of the 1.6 branch

hi, I think the actual blocker for Axis2 1.6 release is woden release. We need to find a way to have the woden release. thanks, Amila. On Mon, Sep 27, 2010 at 4:54 PM, Andreas Veithen wrote: > I'm expecting that the proponents of the last minute approach are not > simply sitting in the peanut g

[jira] Reopened: (AXIS2-4829) need to put header information in skeleton response

[ https://issues.apache.org/jira/browse/AXIS2-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chiranjib reopened AXIS2-4829: -- My problem is not to add header information into requestmy problem was totaly different. I am generat

Re: [ANN][Axis2] Axis2 1.5.2 released

Indeed. I forgot to add that to the announcement for annou...@apache.org. Unfortunately the message already went through moderation, so we cannot change this. I'm preparing a more precise documentation of the Axis2 release process and I will add a note about this so that we can avoid this in the fu

Re: [Axis2] Creation of the 1.6 branch

I'm expecting that the proponents of the last minute approach are not simply sitting in the peanut gallery, but that one of them is ready to step forward as a volunteer to do the release using this approach... Andreas On Mon, Sep 27, 2010 at 11:25, Samisa Abeysinghe wrote: > +1 for creating the

[ANN] Axis2 1.5.2 released

The Apache Axis2 team is pleased to announce the general availability of the Axis2 1.5.2 release. 1.5.2 is a maintenance release to fix the security issue described in CVE-2010-1632 [1] as well as an XSS vulnerability in the admin console and some other minor issues. It also upgrades Axiom to vers

[jira] Resolved: (AXIS2-4817) Inheritance on method parameters not working

[ https://issues.apache.org/jira/browse/AXIS2-4817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2-4817. -- Resolution: Duplicate Same as AXIS2-4818 > Inheritance on method parameters not workin

[jira] Assigned: (AXIS2-4829) need to put header information in skeleton response

[ https://issues.apache.org/jira/browse/AXIS2-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe reassigned AXIS2-4829: Assignee: Samisa Abeysinghe > need to put header information in skeleton response >

[jira] Updated: (AXIS2-4829) need to put header information in skeleton response

[ https://issues.apache.org/jira/browse/AXIS2-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2-4829: - Priority: Trivial (was: Blocker) This is a trivial query > need to put header informati

[jira] Resolved: (AXIS2-4829) need to put header information in skeleton response

[ https://issues.apache.org/jira/browse/AXIS2-4829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2-4829. -- Resolution: Fixed Please refer: http://www.keith-chapman.org/2008/10/axis2-adding-cust

[jira] Commented: (AXIS2-4830) File getting truncated in WS response when tried bigger file

[ https://issues.apache.org/jira/browse/AXIS2-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915252#action_12915252 ] Samisa Abeysinghe commented on AXIS2-4830: -- Can you please attach the code that ca

Build failed in Hudson: Axis2 #387

See Changes: [veithen] Reverted r1001508 (second attempt to do release:branch failed). [veithen] [maven-release-plugin] prepare branch 1_6 [veithen] Reverted r1001503 because release:branch failed in the middle of the process. [veithen]

Build failed in Hudson: Axis2 » Apache Axis2 - Root #387

See Changes: [veithen] Reverted r1001508 (second attempt to do release:branch failed). [veithen] [maven-release-plugin] prepare branch 1_6 [veithen] Reverted r1001503 because release:branch failed in the middle of

Re:

Have you looked into transports in Axis2? I think you need to understand them first. On Thu, Sep 23, 2010 at 11:34 AM, Gayan Dhanushka wrote: > Hi all, > I have an idea of doing a twitter transport using apache axis 2. This is > like you can post to twitter via an ESB. Can somebody tell me how to

Re: [Axis2] Creation of the 1.6 branch

+1 for creating the branch at the last minute. On Mon, Sep 27, 2010 at 2:50 AM, Deepal jayasinghe wrote: > I agree with Glen. We should only cut the new branch when we are > absolutely sure about the release date. > > Deepal > > Hmm. I guess I'm not entirely convinced that we should cut the br

Re: [Axis2] Creation of the 1.6 branch

Glen, I think your point of view is based on a wrong assumption about the "extra work" caused by branching earlier in the release process. Assume that we create the branch today and that people just continue committing to the trunk without taking into account the existence of the 1.6 branch. If af