+1
Thanks,
Ruchith
On Fri, Nov 6, 2009 at 12:20 PM, Glen Daniels g...@thoughtcraft.com wrote:
Greetings, everyone.
A bunch of us here at ApacheCon were talking about the Axis2 TLP idea, and
how to move this forward in the simplest and most effective way. We came up
with *exactly* the same
+1
Thanks,
Ruchith
On Tue, Oct 20, 2009 at 10:48 AM, Glen Daniels g...@thoughtcraft.com wrote:
OK, after adding the default 30-second timeout for connection starvation
issues, and confirming that Rampart now works fine with 1.5.1, let's try this
one more time. Please VOTE on releasing 1.5.1
On Mon, Nov 3, 2008 at 12:51 PM, Glen Daniels [EMAIL PROTECTED] wrote:
I don't think that we should AUTOMATICALLY grant access to every Synapse/CXF
(or Axis2 for that matter, into the future) committer, no. But I do think
+1
the barrier to entry for those folks should be a lot lower (pretty
IMHO Axis2 project as a TLP should be both Java and C.
Thanks,
Ruchith
On Sat, Nov 1, 2008 at 1:14 AM, Manjula Peiris [EMAIL PROTECTED] wrote:
On Sat, 2008-11-01 at 09:23 +0530, Samisa Abeysinghe wrote:
It looks to me that the amount of confusion and frustration demonstrated
in this thread
+1
Thanks,
Ruchith
On Thu, Aug 21, 2008 at 8:21 AM, Nandana Mihindukulasooriya
[EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am calling fresh a vote again for Axis2 1.4.1 and only the source
distribution is changed. Only change is removing some binaries that were
+1
Thanks,
Ruchith
On Tue, Aug 19, 2008 at 2:28 AM, Nandana Mihindukulasooriya
[EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Devs,
Please review:
http://people.apache.org/~nandana/axis2-1.4.1/dist
Maven2 repository:
IMHO when it comes to .mar files we should version them as x.yz
In the case of 1.4.1 release the mar file versions can be: 1.41
This confirms to the module version constraints of Axis2.
Thanks,
Ruchith
On Wed, Jul 9, 2008 at 3:33 PM, Saminda Abeyruwan [EMAIL PROTECTED] wrote:
Guys, Axis2
+1 for Nandana as the release manager.
Thanks,
Ruchith
On Mon, Jul 7, 2008 at 6:03 PM, Davanum Srinivas [EMAIL PROTECTED] wrote:
Nandana,
+1 from me for you to be the Release Manager for 1.4.1
IMHO, we should use 1.4 branch. The *ONLY* change should be the
security change. Nothing more.
Hi,
All soap headers with mustUnderstand attributes must be processed
before the request reaches the service. If not Axis2 will throw an
exception.
Axis2 expects handlers to process SOAP headers and then set the
mustUnderstand attribute.
Thanks,
Ruchith
On Thu, May 22, 2008 at 2:38 AM,
| Smith Barney Technology | CitiGroup
GWM | New York
(212) 657 - 9358
-Original Message-
From: Ruchith Fernando [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 22, 2008 2:38 PM
To: axis-dev@ws.apache.org
Subject: Re: Axis2 1.2 service to understand mustUnderstand attribute
without using
+1
Thanks,
Ruchith
On Thu, Apr 24, 2008 at 10:09 PM, Davanum Srinivas [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Folks,
After all the excitement of the past few days :) We almost forgot the
release
Please review:
+1 for all three.
Thanks,
Ruchith
On Thu, Apr 17, 2008 at 7:15 PM, Davanum Srinivas [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Folks,
As promised (though a day late)...Here's are the dists:
http://people.apache.org/~dims/axis2-1.4-commons/
Please VOTE:
+1
Thanks,
Ruchith
On Fri, Mar 7, 2008 at 11:43 AM, Deepal jayasinghe [EMAIL PROTECTED] wrote:
Hi Dims,
Deepal,
Would you have time for Axis2? I can volunteer as Release Manager if
you wish or we can share the responsibility as
usual. Either works for me.
To be honest I was
Hi Folks,
During the last WCF plugfest [1] at MSFT we were able to fix all
issues related to WS-Security 1.0, WS-Security 1.1 and
WS-SecureConversation.
All these fixes are available in the Rampart/Java trunk at the moment.
You can try the latest Rampart snapshots here: [2]
Thanks,
Ruchith
1.
+1
Thanks,
Ruchith
On Jan 16, 2008 8:52 PM, Dinesh Premalal [EMAIL PROTECTED] wrote:
Hi Devs,
I would like to propose Senaka Fernando as an Axis2/C committer. He
has done a great job for the development of Axis2/C. He is very much active
in the mailing lists and provide numerous
+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
+1
Thanks,
Ruchith
On Jan 8, 2008 2:19 AM, Damitha Kumarage [EMAIL PROTECTED] wrote:
Hi Devs,
I have re-packaged and uploaded the Apache Axis2/C 1.2.0 release
artifacts at [1].
The key used to sign the release artifacts can be found at [2].
The only change from the previous release
in the flow?
Cheers,
David
On Dec 13, 2007 5:30 AM, Ruchith Fernando [EMAIL PROTECTED]
wrote:
+1 ... I also believe we should be able to have module define/arrange
phases without
having to edit the axis2.xml file and the handlers themselves can take
care of fault processing
+1 ... I also believe we should be able to have module define/arrange
phases without
having to edit the axis2.xml file and the handlers themselves can take
care of fault processing.
Even in Rampart we use the same handler in the fault flows and we do
the fault handling internally
without really
+1
Thanks,
Ruchith
On Nov 21, 2007 3:21 PM, Kaushalye Kapuruge [EMAIL PROTECTED] wrote:
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
Hi,
Seems like you have mixed Rampart-1.0 style parameter based
configuration with policy configuration.
If you are using parameter based config please *only* stick to the
configuration described in the article[1].
If not please you policy the way they are used in Rampart samples.
Thanks,
Hi Dobri,
Are you using rampart-policy-version.jar to create and serialize this policy?
We fixed a lot of policy serialization issues in rampart-policy after
1.3. Can you please try using the rampart-policy-SNAPSHOT.jar from the
latest trunk?
Thanks,
Ruchith
p.s. Please subscribe ([EMAIL
On 11/1/07, AP [EMAIL PROTECTED] wrote:
After searching on wss4j mailing list I found that the following resolves my
problem:
1. Download the bouncycastle jar file from: http://www.bouncycastle.org/
and place it in your JRE's lib/ext directory java.security file:
2. Add the following
Hi,
Please use rampart-1.3 with axis2-1.3 :
http://www.apache.org/dyn/closer.cgi/ws/rampart/1_3
Thanks,
Ruchith
Thilina Gunarathne wrote:
Hi,
Your question would be answered better in the rampart list..
I'm cc'ing it... Make sure to join that list..
thanks,
Thilina
On 10/30/07,
) [EMAIL PROTECTED] wrote:
Thanks for following up Ruchith, really appreciated. I look forward to this
fix - will this appear in the latest builds, or will it only appear in the
next release build.
Best,
Tim.
-Original Message-
From: Ruchith Fernando [mailto:[EMAIL PROTECTED]
Sent
5. Rahas, secpolicy, security was moved out to a separate sub-project
within WS along with other security stuff right?
(If yes
(why do we have them inside Axis2?)
(Ignore this ;) ))
hehe ... seems like we got a lisp fan :)
I should have ignored this :D
Anyway do an svn stat ... they are
Hi,
This is an issue in Rampart because it doesn't processes the security
header of fault messages.
https://issues.apache.org/jira/browse/RAMPART-90
This will be fixed in the next release of Apache Rampart.
Thanks,
Ruchith
On 10/12/07, Tim Munro (myDIALS) [EMAIL PROTECTED] wrote:
Hi All,
I
Hi David,
I agree with the proposal!
Just one clarification though :
Are we going to include the SecuredAddressingDispatchValidator in the
addressing module? If so should we a property in the message context
to point to the AxisOperation used for security configuration?
Thanks,
Ruchith
On
+1
Thanks,
Ruchith
On 10/1/07, Manjula Peiris [EMAIL PROTECTED] wrote:
Hi Devs,
After fixing the issues in the last release artifacts I have re-packaged
and uploaded the second set of Apache Sandesha2/C
0.91 release artifacts at
http://people.apache.org/~manjula/release/0.91-3/
The key
+1
Thanks,
Ruchith
On 10/1/07, Kaushalye Kapuruge [EMAIL PROTECTED] wrote:
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
+1
Thanks,
Ruchith
On 9/26/07, Samisa Abeysinghe [EMAIL PROTECTED] 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
+1
Thanks,
Ruchith
On 9/20/07, Samisa Abeysinghe [EMAIL PROTECTED] 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 used to sign the release artifacts can be found at
+1
Thanks,
Ruchith
On 9/14/07, Manjula Peiris [EMAIL PROTECTED] 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
This is the 1.3 release of Apache Rampart.
Apache Rampart 1.3 is a toolkit that provides implementations of the
WS-Sec* specifications for Apache Axis2 1.3, based on Apache WSS4J 1.5.3
and the Apache AXIOM-DOOM 1.2.5 implementations.
You can download the releases from:
We just started a vote to release 1.3 with the artefacts available here :
http://people.apache.org/~ruchithf/rampart/1_3/
If all goes well ... we will announce the release in 3 days from now :-)
Thanks,
Ruchith
On 8/22/07, stlecho [EMAIL PROTECTED] wrote:
All,
We are currently using Axis2
:
Thanks for the supplied information. I think it would be great if future
releases of Axis2 and the related modules - Rampart in this case - were
released at the same time. Are there any plans to synchronize both releases
?
Regards, Stefan Lecho.
Ruchith Fernando wrote:
We just started a vote
Deepal
Hi Dims,
Yes please .
Thanks
Deepal
Davanum Srinivas wrote:
Ruchith, Folks,
I was poking around Sandesha 1.3 branch. I can help with that if we
are short handed and no one else volunteers :)
-- dims
On 8/6/07, Ruchith Fernando [EMAIL PROTECTED] wrote:
We'll cut
+1
Thanks,
Ruchith
On 8/10/07, Deepal jayasinghe [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I have uploaded Axis2 1.3 (take3) into my Apache home location [1]
again . As a result of we found a few issues in 1.3 take2 I had to
upload the artifacts again
Apologies for jumping in late! Please see my comments below:
On 7/30/07, David Illsley [EMAIL PROTECTED] wrote:
Ah, the perrenial ws-sec+ws-a problem.
This is a really complex issue, and unfortunately I don't think it can
be resolved this simply i.e. what happens if security rejects the ws-a
You can authenticate the user based on the signature ... but you will
have to implement your own access control based on the identified
users.
Thanks,
Ruchith
On 7/20/07, balaji hari [EMAIL PROTECTED] wrote:
We are evaluating rampart for implementing web services security. Using
digital
security validation.
Cheers,
David
On 09/08/07, Ruchith Fernando [EMAIL PROTECTED] wrote:
Apologies for jumping in late! Please see my comments below:
On 7/30/07, David Illsley [EMAIL PROTECTED] wrote:
Ah, the perrenial ws-sec+ws-a problem.
This is a really complex issue
IMHO this is out of the scope of WS-Security specification and
WS-SecureConversation will be able to help.
You can authenticate the user and create the security context. Now you
can use this context in sending the subsequent messages.
Thanks,
Ruchith
On 7/10/07, Kevin TierOne [EMAIL PROTECTED]
Hi Deepal,
Where can I find the addressing module of the RC3 release? It is not
in either http://people.apache.org/~deepal/axis2/1.3-RC3/m2-repo/ or
http://people.apache.org/repo/m2-snapshot-repository
Thanks,
Ruchith
On 8/7/07, Deepal jayasinghe [EMAIL PROTECTED] wrote:
Jarek Gawor wrote:
Hi All,
There two widely used cases where the client will have to provide a
username and a password when accessing a service.
- UsernameToken authentication
- HTTP basic auth
Right now with Axis2 these two requires the user to provide the
username in different ways. It will be great if we
currently validate against the XSD ? Thanks.
Regards,
Angel
On 7/10/07, Ruchith Fernando [EMAIL PROTECTED] wrote:
Hmm ... This raises the issue of us not having documented the schema
of RampartConfig :-) ... I'll create a JIRA on this !
Thanks,
Ruchith
On 6/27/07, Nencho Lupanov [EMAIL
Yes ... this certainly can be improved to check whether we actually
received the parts that we expected or not!
Thanks,
Ruchith
On 6/28/07, Angel Todorov [EMAIL PROTECTED] wrote:
Hi all,
I've found this piece of code in the
RampartPolicyBasedResultsValidator.java:
int refCount = 0;
,
Ruchith
On 7/11/07, Nencho Lupanov [EMAIL PROTECTED] wrote:
Hi Ruchith,
the sslConfig assertion is cutom - e.g. not presented in the xsd chema but
it still
processed without errorsso it is not validated?
Regards,
Nencho
2007/7/11, Ruchith Fernando [EMAIL PROTECTED]:
Well ... I believe
Hi ... apologies about the delay in my response on this ... IMHO this
sort of behaviour is not possible and Rampart does NOT modify the SOAP
version (since we always use the appropriate factory to convert to
DOOM). Therefore I don't think rampart always spits out SOAP 1.1.
Angel, are you sure
Hmm ... This raises the issue of us not having documented the schema
of RampartConfig :-) ... I'll create a JIRA on this !
Thanks,
Ruchith
On 6/27/07, Nencho Lupanov [EMAIL PROTECTED] wrote:
Hi all,
recently i fixed a bug in rampart that prevented the usage of ssl encyption
in a transport
Hmm .. I think since the value just has to be a long value there's
another way to fix this :-)
Try using 1.21 if it is a version after 1.2
Thanks,
Ruchith
On 7/7/07, Chamikara Jayalath [EMAIL PROTECTED] wrote:
Hi David,
AFAIK the version number of a module must be a long value. I.e we
Hi Devs,
Some of the Rampart tests are failing due the properties set in the
options object of the ServiceClient are not available in the inflow to
be accessed by a handler (out-in operation). The properties are
available in only the outflow.
Is this behavior correct?
Thanks,
Ruchith
On 6/25/07, Glen Daniels [EMAIL PROTECTED] wrote:
David Illsley wrote:
Yep, properties which are not copied to the operation context in the
outflow will not be available on the inflow message context (unless
you walk up the tree and find the related message context).
It might be nice to have
+1
Thanks,
Ruchith
On 6/19/07, Sahan Gamage [EMAIL PROTECTED] wrote:
+1
-sahan
On 6/19/07, Damitha Kumarage [EMAIL PROTECTED] wrote:
+1
Damitha
Kaushalye Kapuruge wrote:
Hi All,
I would like to propose Samisa Abeysinghe as the release manager for
Apache Axis2/C 1.1.0 release.
http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200703.mbox/[EMAIL
PROTECTED]
- Ruchith
On 6/18/07, Ajith Ranabahu [EMAIL PROTECTED] wrote:
I remember a discussion but not sure what was the last decision. I'm
ok with it anyway :)
Ajith
On 6/17/07, Davanum Srinivas [EMAIL PROTECTED]
This is intentional!
To use rampart we will have to copy all those dependent jars to the
main axis2 classpath all the time (Because the callback handler impl
will have to be supplied by a service and the WSPasswordCallback
interface required wss4j etc.).
Therefore there's no need to make the
+1 from me !
Thanks,
Ruchith
On 6/6/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
Hi All,
I would like to propose Charitha Kankanamge as an Apache Axis2/Java committer.
He has helped us to improve Axis2 in many ways , he has created more than 80
JIRAs [1] and send patches for some of them
This is the 1.2 release of Apache Rampart.
Apache Rampart 1.2 is a toolkit that provides implementations of the
WS-Sec* specifications for Apache Axis2 1.2, based on Apache WSS4J 1.5.2
and the Apache AXIOM-DOOM 1.2.4 implementations.
There are two main Apache Axis2 modules provided with this
Apache WSS4J Team is happy to announce the WSS4J-1.5.2 release.
You can download the releases from:
http://www.apache.org/dyn/closer.cgi/ws/wss4j/1_5_2
Apart from the binary and source distributions, We have an additional
ZIP file that contains other required JAR files to install and run WSS4J.
Savan module [1] supports WS-Eventing.
Thanks,
Ruchith
[1] https://svn.apache.org/repos/asf/webservices/savan/trunk/java/
On 5/30/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi
I have seen
http://wiki.apache.org/ws/StackComparison that Axis2 is supporting WS-Eventing
and no
Hi,
On 5/15/07, David Illsley [EMAIL PROTECTED] wrote:
Hi Amila,
I've been working on a similar issue with a different WS-Sec
implementation on top of Axis2 in the last couple of weeks. I've had a
few discussions about potential vulnerabilites introduced by running
the addressing based
Can you please include xalan in the classpath and try.
Thanks,
Ruchith
On 4/5/07, Mark Badorrek [EMAIL PROTECTED] wrote:
No help from WSS4J - can anyone here advise?
Dear all,
I'me having a small problem with axis2/rampart that I hope you can help
with:
Environment:
JDK 1.5
Tomcat
IncludeToken/Once is not handled properly in Rampart. Please file a bug [1]
Thanks,
Ruchith
[1] https://issues.apache.org/jira/browse/RAMPART
On 5/2/07, Nencho Lupanov [EMAIL PROTECTED] wrote:
Hi All ,
I am trying the rampart sample that comes with the distro.
I am going with sample01, only
+1
Thanks,
Ruchith
On 5/8/07, Samisa Abeysinghe [EMAIL PROTECTED] wrote:
+1 for the release.
Samisa...
Dinesh Premalal wrote:
+1
thanks,
Dinesh
--
Dinesh Premalal
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
WSO2, Inc.; http://www.wso2.com/
http://xydinesh.wordpress.com/
GPG Key ID
+1
Thanks,
Ruchith
On 5/3/07, Samisa Abeysinghe [EMAIL PROTECTED] wrote:
Hi Devs,
After fixing the issues found with the initial release artifacts, I
have re-packaged and uploaded the Apache Axis2/C 1.0.0 release
artifacts at
http://people.apache.org/~samisa/release/1.0.0/final/
+1
Thanks,
Ruchith
On 5/4/07, Kaushalye Kapuruge [EMAIL PROTECTED] wrote:
Hi Devs,
I've re-packed and uploaded the Apache Rampart/C 0.90 release here [1].
The key used to sign can be found here[2].
Please review and vote.
Here is my +1.
Cheers,
Kaushalye
[1]
Hi All,
I will be in Maryland, US in the second week of May. Is anybody
interested in attending tutorials on Apache Axis2 and Apache Rampart?
Both are 1/2 day programs.
This would be on Thursday the 10th of May.
Please drop me a note at [EMAIL PROTECTED] and let me know.
Thanks,
Ruchith
--
Right now you can't do this ... however there has been a number of
requests to make the MessageContext instance available to the callback
handler ... I'll try to look into the possibility of doing so before
the next release!
Thanks,
Ruchith
On 4/20/07, Nencho Lupanov [EMAIL PROTECTED] wrote:
I think Sanka updated axis2 policy handling to support something like
this ... Sanka can you please update us on this?
Thanks,
Ruchith
On 4/2/07, Johny Edu [EMAIL PROTECTED] wrote:
Hi all,
I am trying to run the sample01 policy example that comes with
rampart1.1 release,
but, i am trying
Hi Allen,
Can you please send a sample message which causes this error?
Thanks,
Ruchith
On 4/17/07, Liu, Xiao-Tao (Allen, HPIT-GADSC) [EMAIL PROTECTED] wrote:
Hi,
I am taking use of Axis2 to build a client to access a .net ws with X509
certificate signature. All the steps are fine except
BTW please subscribe to [EMAIL PROTECTED] and post rampart
related problems there.
Thanks,
Ruchith
On 4/18/07, Ruchith Fernando [EMAIL PROTECTED] wrote:
Hi Allen,
Can you please send a sample message which causes this error?
Thanks,
Ruchith
On 4/17/07, Liu, Xiao-Tao (Allen, HPIT-GADSC
Hi,
Right now rampart policy samples demonstrates the case where policy it
self is specified in the services.xml file. However rampart simply
picks up the effective policy from the message context using
getEffectivePolicy(). Therefore once we have this mechanism
implemented we should be able to
On 3/28/07, Sanjiva Weerawarana [EMAIL PROTECTED] wrote:
+1 to use a single convention .. I think Glen removed an incorrect use of
equalsIgnoreCase in Axiom ... which is probably what's causing breakage.
I suggest going with normal camelCase.
Are we going to do this for 1.2?
Thanks,
Ruchith
Hi Devs,
I noticed that ServiceContext#getMyEPR() returns an incorrect EPR
value when addressing headers are missing in the request. I
experienced this with
org.apache.axis2.transport.http.SimpleHTTPServer.
For example if the service is Foo the getEPR().getAddress() returns
only
+1
Thanks,
Ruchith
On 3/20/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
Hi All,
I would like to propose Sumedha Rubasinghe as an Apache Axis2/Java
committer. He has contributed Axis2 , AXIOM a lot specially implementing
SAAJ module. In addition to that he is very active in the community
Hi,
There are nonce and created elements in the request created by your
java client. Are you using a plain text password? Also are you using
Rampart or WSS4J to add the security header?
Thanks,
Ruchith
On 3/17/07, Ayman Yasin [EMAIL PROTECTED] wrote:
Hi all,
I am trying to write a
+1 for moving out and for separate mailing list and JIRA
Thanks,
Ruchith
On 3/22/07, Kaushalye Kapuruge [EMAIL PROTECTED] wrote:
Hi,
I don't think dropping Rampart/C questions in the java list is a good
idea. We need separate mailing list for Rampart/C. Until then we can
use Axis2/C mailing
+1
Thanks,
Ruchith
On 3/16/07, Kaushalye Kapuruge [EMAIL PROTECTED] wrote:
Hi list,
I would like to propose Dumindu Pallewela as an Apache Axis2/C committer.
He has contributed in Rampart/C by implementing the XML
Canonicalization. (https://issues.apache.org/jira/browse/AXIS2C-511.)
This was
Hi devs,
We had a build break in Rampart due to the MessageId addressing
header being absent in the response message. Is this behavior correct?
Thanks,
Ruchith
On 3/8/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: ruchithf
Date: Thu Mar 8 07:00:53 2007
New Revision: 516065
URL:
resend with the axis2 prefix :-)
On 3/8/07, Ruchith Fernando [EMAIL PROTECTED] wrote:
Hi devs,
We had a build break in Rampart due to the MessageId addressing
header being absent in the response message. Is this behavior correct?
Thanks,
Ruchith
On 3/8/07, [EMAIL PROTECTED] [EMAIL PROTECTED
Very nice ...:-)
We should make sure Rampart and Rampart/C interops on those policies.
Thanks,
Ruchith
On 2/13/07, Kaushalye Kapuruge [EMAIL PROTECTED] wrote:
Hi List,
We are happy to announce that Rampart/C has the WS-Security Policy
(Version 1.1 July 2005) support now. The credit should go
Hi Thlina,
How can I access the surefire reports?
Thanks,
Ruchith
On 2/13/07, Thilina Gunarathne [EMAIL PROTECTED] wrote:
Hi Ruchith,
Rampart build[1] in the continuum seems to be continuously failing.
AFAIK it might be an issue with the security restrictions or the key
strength..
Anyway I
to rectify this as well.
Thanks,
Ruchith
On 2/9/07, Yevgeny Rouban [EMAIL PROTECTED] wrote:
Hello.
The threading fix committed to the Axiom DOM by Ruchith Fernando [1]
seems to not resolve the problem.
1. Imagine two threads enter the method setDOOMRequired(true).
The faster one calls
Hi All,
A few of us are traveling to Phoenix AZ in two weeks and are wondering
whether anyone would be interested in joining a 1/2 day course /
tutorial on Axis2 (A 1/2 day Synapse course will also be available
for those interested)
This would be on Wednesday the 14th of February
Please drop
+1
Thanks,
Ruchith
On 1/31/07, Thilina Gunarathne [EMAIL PROTECTED] wrote:
Hi All,
I would like to propose Isuru Eranga Suriarachchi as an Apache
Axis2/java committer.
Isuru started with improving and contributing to Axis2
documentation. Later he implemented JSON support for
Hi,
On 1/30/07, Wynn, Jackson E. [EMAIL PROTECTED] wrote:
Apologies to all if this is posted to the wrong group...
I am developing a prototype using Axis 2 and would like to learn more about
what WS-Trust capabilities rahas v1.1 supports. After reviewing the rampart
1.1 code base, it
You can post rampart/rahas related questions to
rampart-dev@ws.apache.org list :-)
Thanks,
Ruchith
On 1/30/07, Ruchith Fernando [EMAIL PROTECTED] wrote:
Hi,
On 1/30/07, Wynn, Jackson E. [EMAIL PROTECTED] wrote:
Apologies to all if this is posted to the wrong group...
I am developing
FYI : http://wiki.apache.org/ws/FrontPage/Axis2/CodeQuality
Thanks,
Ruchith
On 1/30/07, Sanjiva Weerawarana [EMAIL PROTECTED] wrote:
On Mon, 2007-01-29 at 13:37 -0800, Bill Nagy wrote:
I was unable to find them on the wiki (I looked at both the current as
well as the old root pages.) The
BTW there's another way to do this mentioned here [1]
$ maven multiproject:goal -Dgoal=eclipse
Thanks,
Ruchith
[1] http://issues.apache.org/jira/browse/AXIS2-1503
On 1/25/07, Dimuthu Leelaratne [EMAIL PROTECTED] wrote:
Hi Hailong Wang,'
The exact list of required dependancies and their
Correction : this is another way to create the project files required
to create the eclipse project. NOT for getting the dependant jars.
Thanks,
Ruchtih
On 1/25/07, Ruchith Fernando [EMAIL PROTECTED] wrote:
BTW there's another way to do this mentioned here [1]
$ maven multiproject:goal -Dgoal
Hi All,
Apache Rampart SVN, mailing list and JIRA is now ready !
Mailing list : rampart-dev@ws.apache.org
JIRA : http://issues.apache.org/jira/browse/RAMPART
SVN : https://svn.apache.org/repos/asf/webservices/rampart/trunk/java
Thanks,
Ruchith
--
www.ruchith.org
www.wso2.org
Hi David,
Yep ! SNAPSHOT will be fine for us.
Thanks,
Ruchith
On 1/24/07, David Illsley [EMAIL PROTECTED] wrote:
Hi Dimuthu,
I'm working on the axis2 maven2 bits, which will probably include
decoupling the mar plugin release from the main releases. However,
that's not quite ready. Would a
Hi Thilo,
Apologies about the delay in the response.
On 1/23/07, Thilo Frotscher [EMAIL PROTECTED] wrote:
Hi!
Does anyone have information on this issue, please?
Thanks,
Thilo
Thilo Frotscher wrote:
Hello,
On the server side, Rampart configuration is done in service.xml.
In this
+1 from me !
Thanks,
Ruchith
On 1/19/07, Sanka Samaranayake [EMAIL PROTECTED] wrote:
Hi,
Savan is a WS-Eventing implementation on top Axis2 and currently lives as a
module inside Axis2.
I propose we move it into a separate Apache WS sub project which will make
Axis2 codebase clean
and also
Ok ... I updated the issue.
When we fix this [1] in OM the issue will be resolved.
I'll take a crack at it.
Thanks,
Ruchith
[1] https://issues.apache.org/jira/browse/WSCOMMONS-104
On 1/15/07, Sanjiva Weerawarana [EMAIL PROTECTED] wrote:
+1 but for 1.2. Unless we find some problems with
+1
Thanks,
Ruchith
On 1/12/07, Samisa Abeysinghe [EMAIL PROTECTED] wrote:
Hi All,
I would like to propose Supun Kamburugamuva as an Apache Axis2/C
commiter.
Supun developed the IIS module on his own and contributed that to
Axis2/C. He also has provided fixes to some other
We do have a bunch of WS-Trust integration tests where they requests
and obtains SAML tokens from an STS [1].
Thanks,
Ruchith
[1]
https://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_1/modules/integration/test/org/apache/rahas
On 1/8/07, Thilo Frotscher [EMAIL PROTECTED] wrote:
I have already made a request:
http://issues.apache.org/jira/browse/INFRA-1090
Thanks,
Ruchith
On 1/8/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote:
Hi All;
How about creating a JIRA project for security and its related sub
projects ?
Then we can report this kind of JIRAs there in that
IMHO we don't need a new project for this ... Can this be a new maven
module within Neethi (I think its just a couple of classes)? And
neethi can have new modules for this sort of assertions in the future.
Now this way one will be able to get the neethi.jar along with jars
what ever other
Hi Thilo,
On 1/8/07, Thilo Frotscher [EMAIL PROTECTED] wrote:
Hi!
If you want to make use of password callback classes, these always
depend on org.apache.ws.security.WSPasswordCallback, because the
Callback instances which are passed into the handle() method have
to be cast.
+1
Thanks,
Ruchith
On 1/2/07, Davanum Srinivas [EMAIL PROTECTED] wrote:
David/Team,
+1 to move security tests out of Axis2 build
+1 to setup continuum on ws.zones
thanks,
dims
On 1/2/07, David Illsley [EMAIL PROTECTED] wrote:
I'm dead against moving security out of the axis2 build and
1 - 100 of 323 matches
Mail list logo
