+1. I've suggested in the past that Rampart should really be merged back
into Axis2, since it's essentially a required component and having it as
a separate project only adds administrative overhead with no noticeable
benefit.
- Dennis
--
Dennis M. Sosnoski
SOA and Web Services in Java
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Mark Badorrek wrote:
As I've outlined earlier I'm a little concerned that we're at the cusp of an
RC2 for Axis2, yet there has been no official release of Rampart 1.3 to go with
it.
Remember that Rampart hasn't worked with Axis2 since Axis2_1.2.1. Thus we do have a history of delivering a product that many can't use. I'm not sufficiently involved with the Axis2/Rampart interface to know where the miss-step occurred. In any case it doesn't matter.
This release looks to be a quite significant one with a plethora of bugs fixed, inclusion with geronimo etc. We were all asked to hammer the RC to see if it holds together. I can't do this for WS-Security.
This is too good an opportunity to waste and as such can anyone give me a compelling reason not to write a 'Blocker' jira on Axis2 until it can formally pass a Rampart regression test?
Cheers,
Mark B
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
