Re: [VOTE] Release Sandesha2 1.4 and Axis2 1.5.4

The vote has been open for more than 72 hours and we have the required 3 binding +1 votes, without any 0 or -1 votes. I will start by promoting the Maven artifacts so that Synapse can continue with their release. I'll do the rest (deploying the distributions and the site) later. Andreas On Thu, D

Build failed in Hudson: sandesha2-trunk #174

See -- [...truncated 127 lines...] [INFO] Installing to

Build failed in Hudson: sandesha2-trunk » Sandesha2 - Rampart Integration #174

See -- [INFO] [INFO] Building Sandesha2 - Rampart Integration [INFO]t

[jira] Issue Comment Edited: (AXIS2-4008) Generated stub classes are copied to the Eclipse workspace folder instead of the project location

[ https://issues.apache.org/jira/browse/AXIS2-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974548#action_12974548 ] Harshana Eranga Martin edited comment on AXIS2-4008 at 12/23/10 1:56 AM:

[jira] Commented: (AXIS2-4008) Generated stub classes are copied to the Eclipse workspace folder instead of the project location

[ https://issues.apache.org/jira/browse/AXIS2-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974548#action_12974548 ] Harshana Eranga Martin commented on AXIS2-4008: --- Hi Norman, I was able to re

Re: Release Rampart 1.5.1 in sync with Axis2 1.5.4

This is what we've been doing with the WSO2 Application Server releases for past many years. We've always released with compatible Axis2, Rampart & Sandesha versions. I think that is the best model to follow for Apache Axis2, Rampart & Sandesha2 as well. Even the source packs contains the sources f

Re: [VOTE] Apache Rampart 1.5.1 release

+1 (Binding) Azeez On Thu, Dec 23, 2010 at 10:07 AM, Selvaratnam Uthaiyashankar < uthaiyashan...@gmail.com> wrote: > Devs, > > This is the vote for Apache Rampart 1.5.1 release. > > Please review the signed artifacts: > > http://people.apache.org/~shankar/rampart/1.5.1/dist/ > > The m2 repositor

Hudson build is still unstable: Axis2 #542

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 still unstable: Axis2 » A pache Axis2 - JAXWS Integration Tests #542

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

Re: [Axis2] 2 day hackathon on Axis2 at WSO2

On Thu, Dec 23, 2010 at 3:51 AM, Samisa Abeysinghe < samisa.abeysin...@gmail.com> wrote: > And we have to keep on doing this regularly. > +1. This is just the beginning. A new beginning! :) > > I found that Rampart had quite a bunch of quality patches provided, that we > had not applied for a l

Re: [VOTE] Apache Rampart 1.5.1 release

+1 for the release. Thanks, Dimuthu On Thu, Dec 23, 2010 at 11:13 AM, Ruwan Linton wrote: > Tested with Synapse-2.0 proposed release and seems to work just fine :-) > > +1 for the release (Binding) > > Thanks, > Ruwan > > > On Thu, Dec 23, 2010 at 11:09 AM, Prabath Siriwardana wrote: > >> +1 (Bi

[jira] Resolved: (RAMPART-278) PolicyBasedResultsValidator throws exception when headers encrypted before signing.

[ https://issues.apache.org/jira/browse/RAMPART-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Leelarathne resolved RAMPART-278. - Resolution: Fixed Applied the patch to trunk. Revision 1052173 > PolicyBasedRes

Re: [VOTE] Apache Rampart 1.5.1 release

Tested with Synapse-2.0 proposed release and seems to work just fine :-) +1 for the release (Binding) Thanks, Ruwan On Thu, Dec 23, 2010 at 11:09 AM, Prabath Siriwardana wrote: > +1 (Binding) > > Thanks & regards, > -Prabath > > > On Thu, Dec 23, 2010 at 11:01 AM, Samisa Abeysinghe < > samisa.a

Re: [VOTE] Apache Rampart 1.5.1 release

+1 Thanks, ~Isuru On Thu, Dec 23, 2010 at 10:07 AM, Selvaratnam Uthaiyashankar < uthaiyashan...@gmail.com> wrote: > Devs, > > This is the vote for Apache Rampart 1.5.1 release. > > Please review the signed artifacts: > > http://people.apache.org/~shankar/rampart/1.5.1/dist/

[jira] Resolved: (AXIS2-618) Could the WSDL served up by axis2 utilize a CSS stylesheet?

[ https://issues.apache.org/jira/browse/AXIS2-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2-618. - Resolution: Won't Fix This has been hanging there for more than 4 years. And it is unlikel

Re: [VOTE] Apache Rampart 1.5.1 release

+1 (Binding) Thanks & regards, -Prabath On Thu, Dec 23, 2010 at 11:01 AM, Samisa Abeysinghe < samisa.abeysin...@gmail.com> wrote: > I tested and all seems fine! > > Here is my vote: +1 (Binding) > > Samisa... > > > On Thu, Dec 23, 2010 at 10:07 AM, Selvaratnam Uthaiyashankar < > uthaiyashan...@g

Re: [VOTE] Apache Rampart 1.5.1 release

I tested and all seems fine! Here is my vote: +1 (Binding) Samisa... On Thu, Dec 23, 2010 at 10:07 AM, Selvaratnam Uthaiyashankar < uthaiyashan...@gmail.com> wrote: > Devs, > > This is the vote for Apache Rampart 1.5.1 release. > > Please review the signed artifacts: > > http://people.apache.or

Re: [VOTE] Release Sandesha2 1.4 and Axis2 1.5.4

+1 for both releases.. Thanks, ~Isuru On Mon, Dec 20, 2010 at 4:19 AM, Andreas Veithen wrote: > All, > > Here is the vote for the Sandesha2 release. Since the release > candidate depends on a fix in Axis2, I also had to prepare a new > maintenance release from the 1.5 branch. Since the releases

Re: Release Rampart 1.5.1 in sync with Axis2 1.5.4

On Thu, Dec 23, 2010 at 6:00 AM, Nandana Mihindukulasooriya < nandana@gmail.com> wrote: > On Wed, Dec 22, 2010 at 4:27 PM, Ruwan Linton wrote: > >> Well, even right now, One has to build the distribution module separately >> after building the axis2 project from the root pom. So in effect it i

[jira] Assigned: (RAMPART-278) PolicyBasedResultsValidator throws exception when headers encrypted before signing.

[ https://issues.apache.org/jira/browse/RAMPART-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Leelarathne reassigned RAMPART-278: --- Assignee: Dimuthu Leelarathne > PolicyBasedResultsValidator throws exception

Build failed in Hudson: sandesha2-trunk #173

See -- [...truncated 127 lines...] [INFO] Installing to

Build failed in Hudson: sandesha2-trunk » Sandesha2 - Rampart Integration #173

See -- [INFO] [INFO] Building Sandesha2 - Rampart Integration [INFO]t

Re: [VOTE] Release Sandesha2 1.4 and Axis2 1.5.4

I tested it with Rampart and all works fine. +1 for both release. Regards, Shankar On Mon, Dec 20, 2010 at 4:19 AM, Andreas Veithen wrote: > All, > > Here is the vote for the Sandesha2 release. Since the release > candidate depends on a fix in Axis2, I also had to prepare a new > maintenance re

[VOTE] Apache Rampart 1.5.1 release

Devs, This is the vote for Apache Rampart 1.5.1 release. Please review the signed artifacts: http://people.apache.org/~shankar/rampart/1.5.1/dist/ The m2 repository is available at: http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/ The site is temporarily hosted at: http://people.apache

Re: Release Rampart 1.5.1 in sync with Axis2 1.5.4

I think there is no objection to this, so I will start on this distro as a subproject in axis2 on the trunk. I don't think we can get this distribution into the axis2 modules without a major structural change, so assume it is OK to create a subproject for the distro and have svn externs to the axis

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

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 #261

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

[jira] Commented: (AXIS2-4755) dynamic serviceclient: axisservice-names are not unique

[ https://issues.apache.org/jira/browse/AXIS2-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974467#action_12974467 ] Srinath Perera commented on AXIS2-4755: --- And I want the error you got as well > dyna

[jira] Commented: (AXIS2-4755) dynamic serviceclient: axisservice-names are not unique

[ https://issues.apache.org/jira/browse/AXIS2-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974466#action_12974466 ] Srinath Perera commented on AXIS2-4755: --- Cloud you create a testcase (with some aar f

[jira] Resolved: (AXIS2-4169) WSDL port addresses are not moduified when a service archive which contains a wsdl is deployed

[ https://issues.apache.org/jira/browse/AXIS2-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srinath Perera resolved AXIS2-4169. --- Resolution: Fixed Tried this with the current trunk, and it is working. Please reopen if you

[jira] Commented: (AXIS2-3354) Allow for sharing XSD schemas between services

[ https://issues.apache.org/jira/browse/AXIS2-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974461#action_12974461 ] Srinath Perera commented on AXIS2-3354: --- Hi Mauro, The fix you mentioned, have you

[jira] Issue Comment Edited: (AXIS2-3354) Allow for sharing XSD schemas between services

[ https://issues.apache.org/jira/browse/AXIS2-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974461#action_12974461 ] Srinath Perera edited comment on AXIS2-3354 at 12/22/10 8:23 PM:

[jira] Resolved: (RAMPART-218) EncryptedElements assertion failed validation in PolicyBasedResultsValidator

[ https://issues.apache.org/jira/browse/RAMPART-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandana Mihindukulasooriya resolved RAMPART-218. Resolution: Fixed Fix Version/s: 1.5.1 This is fixed in the

Re: Release Rampart 1.5.1 in sync with Axis2 1.5.4

On Wed, Dec 22, 2010 at 4:27 PM, Ruwan Linton wrote: > Well, even right now, One has to build the distribution module separately > after building the axis2 project from the root pom. So in effect it is > really a separate thing. I suggest we move the axis2 distribution into a > separate subproject

Hudson build is back to normal : sandesha2-trunk #172

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 : sandesha2- trunk » Sandesha2 - Rampart Integration #172

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

[jira] Resolved: (RAMPART-136) Rampart doesn't support RequiredElements Assertion

[ https://issues.apache.org/jira/browse/RAMPART-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nandana Mihindukulasooriya resolved RAMPART-136. Resolution: Fixed Fix Version/s: 1.5.1 Fixed the issue and

Re: [Axis2] 2 day hackathon on Axis2 at WSO2

And we have to keep on doing this regularly. I found that Rampart had quite a bunch of quality patches provided, that we had not applied for a long time. I am thankful to all those who provided the patches as well as their patience in terms of waiting this long to get them applied to source tree.

Hudson build became unstable: Axis2 #541

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

RE: FW: Question on REST and Axis 1.3

Andreas/Devlopers, Good job on smart mouthing me there :) Don't get me wrong for being persistent but I am able to reproduce this issue in Axis2 1.4 too. I am unable to test on Axis2 1.5.x because of the unavailability of Eclipse JST Web Services project (https://issues.apache.org/jira/browse

RE: Is there a proper documentation on deploying AXIS2 in IBM Web Sphere

> What was the WebSphere version that >> you used? > I used the WebSphere v 7. Which fix pack level? We currently have Axis2 1.5.1 working with WAS V7 FP 11, I think was working OK with FP 9; don't know about earlier FPs, but always go with latest possible. We're currently still renaming the .m

[jira] Resolved: (AXIS2-3723) AXIS2 is not aware of "is" methods when generating soap messages from JAXB java beans

[ https://issues.apache.org/jira/browse/AXIS2-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2-3723. Resolution: Fixed > AXIS2 is not aware of "is" methods when generating soap messages from J

[jira] Resolved: (AXIS2-3807) codegen changes Ant Home thus no Ant Builder task works anymore - missing AntMain

[ https://issues.apache.org/jira/browse/AXIS2-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2-3807. Resolution: Fixed Fix Version/s: 1.6 Assignee: Senaka Fernando > codegen ch

[jira] Issue Comment Edited: (AXIS2-4451) Incorrect resolution of imported schema URLs

[ https://issues.apache.org/jira/browse/AXIS2-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974359#action_12974359 ] Senaka Fernando edited comment on AXIS2-4451 at 12/22/10 2:54 PM: ---

[jira] Resolved: (AXIS2-4451) Incorrect resolution of imported schema URLs

[ https://issues.apache.org/jira/browse/AXIS2-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2-4451. Resolution: Invalid Fix Version/s: 1.6 Assignee: Senaka Fernando #1 and #2

[jira] Resolved: (AXIS2-3947) EJB provider run only once

[ https://issues.apache.org/jira/browse/AXIS2-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2-3947. Resolution: Fixed > EJB provider run only once > -- > >

[jira] Assigned: (AXIS2-3947) EJB provider run only once

[ https://issues.apache.org/jira/browse/AXIS2-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando reassigned AXIS2-3947: -- Assignee: Senaka Fernando (was: sumedha rubasinghe) > EJB provider run only once > ---

Question on AXIS2-4124

Hi Glen, I believe that you have fixed the issue [1], sometime back, according to [2]. I now don't get a response as explained, as it seems. But, neither do I get a soap fault. I wonder what the your fix for [2] did? [1] https://issues.apache.org/jira/browse/AXIS2-4124 [2] https://issues.apache.o

[jira] Assigned: (AXIS2-3723) AXIS2 is not aware of "is" methods when generating soap messages from JAXB java beans

[ https://issues.apache.org/jira/browse/AXIS2-3723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando reassigned AXIS2-3723: -- Assignee: Senaka Fernando (was: Amila Chinthaka Suriarachchi) > AXIS2 is not aware of

Re: Release Rampart 1.5.1 in sync with Axis2 1.5.4

Andreas basically it forces us to make sure Rampart & Sandesha are ALWAYS available as part of the Axis2 release. That means we won't (not that we can't but rather won't) do an axis2 release until the other two are ready too. We already do that for addressing .. so this simply collapses the other t

[jira] Resolved: (AXIS2-4399) wsdl2java - overwriting output (with -or) causes an exception

[ https://issues.apache.org/jira/browse/AXIS2-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-4399. - Resolution: Fixed > wsdl2java - overwriting output (with -or) causes an exception > -

[jira] Updated: (AXIS2-4717) Getting "Connection reset by peer" when sending a string which contains the sequence \n\n\n\n

[ https://issues.apache.org/jira/browse/AXIS2-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez updated AXIS2-4717: Priority: Minor (was: Major) > Getting "Connection reset by peer" when sending a string which cont

Re: [Axis2] 2 day hackathon on Axis2 at WSO2

The two day hackathon has been a great success. We have been able to resolve about 180 issues in Axis2 & Rampart. I would like to thank everybody who motivated us & contributed towards this. Azeez On Tue, Dec 21, 2010 at 10:26 AM, Afkham Azeez wrote: > Hi folks, > We are having a 2 day hackatho

Re: svn commit: r1051511 - /axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/description/ClientUtils.java

Hi Andreas, I did revert the change for the function where it add the transport listener. But this method seems to be wrong because it says it inferTransport but actually it is doing write operations as well. I'll try to re-factor this method properly if possible. The other method, we are using i

Re: Release Rampart 1.5.1 in sync with Axis2 1.5.4

Supposed to enforce both Rampart and Sadesha2 to be released in-line with Axis2. Or test what ever the working Rampart Sandesha2 packs with Axis2. Ideally we should also build us a good set of integration tests under this so that we can automate the tests of Rampart/Sandesha with Axis2. Thanks, Ru

Re: Release Rampart 1.5.1 in sync with Axis2 1.5.4

Samisa, Having a single distribution to ship all those enforces the artifacts to be released once. Otherwise we will have the same situation in another 6 months. Thanks, Ruwan On Wed, Dec 22, 2010 at 9:50 PM, Samisa Abeysinghe < samisa.abeysin...@gmail.com> wrote: > The first problem that we ha

[jira] Commented: (RAMPART-15) Need the ability to allow security elements' Ids to be set from a callback

[ https://issues.apache.org/jira/browse/RAMPART-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974261#action_12974261 ] George Stanchev commented on RAMPART-15: How does SAML resolve the described issue?

Re: Release Rampart 1.5.1 in sync with Axis2 1.5.4

The first problem that we have to solve is the problem of Rampart/Sandesha counterparts not being there for a given Axis2 release. If we can first fix that, then packaging them together in one pack or not is secondary. Samisa... On Wed, Dec 22, 2010 at 9:18 PM, Andreas Veithen wrote: > That is

[jira] Resolved: (AXIS2-4661) Findbugs Warnings

[ https://issues.apache.org/jira/browse/AXIS2-4661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-4661. - Resolution: Fixed Thanks for the wonderful suggestions. We have incorporated these into the trun

Re: Release Rampart 1.5.1 in sync with Axis2 1.5.4

That is not true. The entire stuff is built in a single run by mvn release:perform. We could have another distribution that includes Axis2, the transports, Rampart and Sandesha, but I don't understand what problem this is supposed to solve. Andreas On Wed, Dec 22, 2010 at 16:27, Ruwan Linton wro

Re: Release Rampart 1.5.1 in sync with Axis2 1.5.4

On Wed, Dec 22, 2010 at 8:57 PM, Ruwan Linton wrote: > Well, even right now, One has to build the distribution module separately > after building the axis2 project from the root pom. So in effect it is > really a separate thing. I suggest we move the axis2 distribution into a > separate subproject

Hudson build is back to normal : Rampart #216

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

Re: Release Rampart 1.5.1 in sync with Axis2 1.5.4

Well, even right now, One has to build the distribution module separately after building the axis2 project from the root pom. So in effect it is really a separate thing. I suggest we move the axis2 distribution into a separate subproject under Axis2. I really think that the Axis2 distro should have

Hudson build is back to normal : Rampart » Apache Rampart #216

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

[jira] Resolved: (RAMPART-313) Improvements to the site axis.apache.org/axis2/java/rampart/

[ https://issues.apache.org/jira/browse/RAMPART-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar resolved RAMPART-313. -- Resolution: Fixed Applied patch (rampart-site-newupdate.patch) in revision 1051930 >

[jira] Updated: (RAMPART-313) Improvements to the site axis.apache.org/axis2/java/rampart/

[ https://issues.apache.org/jira/browse/RAMPART-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chanaka Jayasena updated RAMPART-313: - Attachment: rampart-site-newupdate.patch > Improvements to the site axis.apache.org/axis

[jira] Reopened: (RAMPART-313) Improvements to the site axis.apache.org/axis2/java/rampart/

[ https://issues.apache.org/jira/browse/RAMPART-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chanaka Jayasena reopened RAMPART-313: -- The left menu on the Rampart site looks odd in the current version. I am attaching a patc

Build failed in Hudson: Rampart » Apache Rampart #215

See Changes: [samisa] Fixed the typo in Axis2 version and Sandesha version [samisa] Fixed mar versions to be 1.5.1 [samisa] Fixed the versions for next release as well as dependency versions [shankar

Build failed in Hudson: Rampart #215

See Changes: [samisa] Fixed the typo in Axis2 version and Sandesha version [samisa] Fixed mar versions to be 1.5.1 [samisa] Fixed the versions for next release as well as dependency versions [shankar] Applying patch from RAMPART-315 [

Hudson build is back to stable : Axis2 #539

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 » A pache Axis2 - JAXWS Integration Tests #539

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

Re: Release Rampart 1.5.1 in sync with Axis2 1.5.4

If it is too many logistics to build one pack, we can have separate packs but release all three at the same time, at least few days apart Samisa... On Wed, Dec 22, 2010 at 6:12 PM, Andreas Veithen wrote: > This would require again changes to the project structure and/or to > the build and releas

[jira] Assigned: (AXIS2-4661) Findbugs Warnings

[ https://issues.apache.org/jira/browse/AXIS2-4661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez reassigned AXIS2-4661: --- Assignee: Afkham Azeez > Findbugs Warnings > - > > Key: AXIS2

[jira] Updated: (RAMPART-136) Rampart doesn't support RequiredElements Assertion

[ https://issues.apache.org/jira/browse/RAMPART-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar updated RAMPART-136: - Fix Version/s: (was: 1.5.1) > Rampart doesn't support RequiredElements Assertion > -

[jira] Updated: (RAMPART-216) Wrong SignatureMethod and DigestMethod generated in request in case of algoritm suite having SHA256 hashing algorithm (example: Basic256Sha256)

[ https://issues.apache.org/jira/browse/RAMPART-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar updated RAMPART-216: - Fix Version/s: (was: 1.5.1) > Wrong SignatureMethod and DigestMethod generated in re

[jira] Updated: (RAMPART-229) There should be a way to add custom tokens to the security header

[ https://issues.apache.org/jira/browse/RAMPART-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar updated RAMPART-229: - Fix Version/s: (was: 1.5.1) > There should be a way to add custom tokens to the secu

[jira] Updated: (RAMPART-197) Rampart handler not processing empty security header with mustUnderstand="1"

[ https://issues.apache.org/jira/browse/RAMPART-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar updated RAMPART-197: - Fix Version/s: (was: 1.5.1) > Rampart handler not processing empty security header w

[jira] Updated: (RAMPART-41) "IncludeToken/Once" is not handled properly in Rampart

[ https://issues.apache.org/jira/browse/RAMPART-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar updated RAMPART-41: Fix Version/s: (was: 1.5.1) > "IncludeToken/Once" is not handled properly in Rampart >

[jira] Commented: (AXIS2-4834) Allow calls to HTTP endpoint using same address as the SOAP endpoint

[ https://issues.apache.org/jira/browse/AXIS2-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974201#action_12974201 ] Isuru Eranga Suriarachchi commented on AXIS2-4834: -- Yes please. And also,

[jira] Resolved: (RAMPART-316) commons-lang jar is not available with Axis2 which breaks Sample-08

[ https://issues.apache.org/jira/browse/RAMPART-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar resolved RAMPART-316. -- Resolution: Fixed Fix Version/s: NextVersion Assignee: S.Uthaiyashankar

[jira] Commented: (AXIS2-4834) Allow calls to HTTP endpoint using same address as the SOAP endpoint

[ https://issues.apache.org/jira/browse/AXIS2-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974198#action_12974198 ] Dennis Kieselhorst commented on AXIS2-4834: --- Hmm didn't work for me (wsdl-first a

[jira] Reopened: (AXIS2-4524) Caching BeanInfo in adb module's BeanUtil improves performance

[ https://issues.apache.org/jira/browse/AXIS2-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen reopened AXIS2-4524: This change creates a memory leak because the BeanInfo objects have references to class object

[jira] Commented: (AXIS2-4834) Allow calls to HTTP endpoint using same address as the SOAP endpoint

[ https://issues.apache.org/jira/browse/AXIS2-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974196#action_12974196 ] Isuru Eranga Suriarachchi commented on AXIS2-4834: -- Hi Dennis, If there i

[jira] Updated: (AXIS2-4646) Publish updates schemas for module.xml and services.xml

[ https://issues.apache.org/jira/browse/AXIS2-4646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathiravelu Pradeeban updated AXIS2-4646: - Attachment: AXIS2-4646.diff Attached patch fixes the issues in the published serv

Re: Release Rampart 1.5.1 in sync with Axis2 1.5.4

On Wed, Dec 22, 2010 at 9:39 AM, Ruwan Linton wrote: > Why do't we create a one single distribution with Rampart and Sandesh2 > when we release Axis2. > > +1

[jira] Resolved: (AXIS2-4736) Axis Servlet consumes 100% cpu

[ https://issues.apache.org/jira/browse/AXIS2-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-4736. - Resolution: Cannot Reproduce resolving since the steps to reproduce this are not provided > Axis

[jira] Resolved: (AXIS2-4741) Dead Code in ADBXMLStreamReaderImpl.java

[ https://issues.apache.org/jira/browse/AXIS2-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-4741. - Resolution: Fixed > Dead Code in ADBXMLStreamReaderImpl.java > -

[jira] Updated: (RAMPART-316) commons-lang jar is not available with Axis2 which breaks Sample-08

[ https://issues.apache.org/jira/browse/RAMPART-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thilina Buddhika updated RAMPART-316: - Attachment: RAMPART-316.patch This patch addresses the above mentioned issue. It copies

[jira] Commented: (AXIS2-4747) Possible bug when generating code for livebookings wsdl

[ https://issues.apache.org/jira/browse/AXIS2-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974189#action_12974189 ] Afkham Azeez commented on AXIS2-4747: - This WARNING is printed when the code is generat

[jira] Assigned: (AXIS2-4834) Allow calls to HTTP endpoint using same address as the SOAP endpoint

[ https://issues.apache.org/jira/browse/AXIS2-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isuru Eranga Suriarachchi reassigned AXIS2-4834: Assignee: Isuru Eranga Suriarachchi > Allow calls to HTTP endpoint

[jira] Created: (RAMPART-316) commons-lang jar is not available with Axis2 which breaks Sample-08

commons-lang jar is not available with Axis2 which breaks Sample-08 --- Key: RAMPART-316 URL: https://issues.apache.org/jira/browse/RAMPART-316 Project: Rampart Issue Type: Bug

[jira] Updated: (AXIS2-4771) ComparatorUtil.compare(UnsignedLong, String) doesn't exist

[ https://issues.apache.org/jira/browse/AXIS2-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS2-4771: --- Fix Version/s: (was: 1.5.5) 1.6 Yes, this was fixed in r990778, but on

[jira] Resolved: (RAMPART-262) SymmetricBinding client can invoke the AsymmetricBinding service policy

[ https://issues.apache.org/jira/browse/RAMPART-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar resolved RAMPART-262. -- Resolution: Duplicate duplicated by RAMPART-269 > SymmetricBinding client can invoke

[jira] Resolved: (AXIS2-4750) Clean up metadata resources.properties file

[ https://issues.apache.org/jira/browse/AXIS2-4750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Afkham Azeez resolved AXIS2-4750. - Resolution: Fixed Applied patch > Clean up metadata resources.properties file >

Re: Release Rampart 1.5.1 in sync with Axis2 1.5.4

Note: if you are planning to use Nexus to perform the release, then you need to request inclusion of the org.apache.rampart package into the staging profile for Axis2. See INFRA-3271 for an example of this type of request. Andreas On Wed, Dec 22, 2010 at 03:26, Samisa Abeysinghe wrote: > We have

[jira] Resolved: (RAMPART-292) Exclude expiration date

[ https://issues.apache.org/jira/browse/RAMPART-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar resolved RAMPART-292. -- Resolution: Duplicate Assignee: S.Uthaiyashankar Duplicate of RAMPART-144 > Exc

[jira] Updated: (RAMPART-144) Timestamp with just create time element

[ https://issues.apache.org/jira/browse/RAMPART-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar updated RAMPART-144: - Issue Type: New Feature (was: Bug) > Timestamp with just create time element >

Hudson build is back to normal : Rampart #214

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 : Rampart » Apache Rampart #214

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

[jira] Updated: (AXIS2-3841) wsdl2java fails with NullPointException due to WSDL4J.Defintion returning null targetNamespace

[ https://issues.apache.org/jira/browse/AXIS2-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tharindu Mathew updated AXIS2-3841: --- Attachment: HelloWorld.wsdl A WSDL that will reproduce this issue. > wsdl2java fails with Nu

  1   2   3   >