Following is a status update on this task. On Wed, Jan 4, 2012 at 4:53 PM, Andreas Veithen <andreas.veit...@gmail.com> wrote: > On Tue, Jan 3, 2012 at 08:56, Amila Jayasekara <ami...@wso2.com> wrote: >> Hi All, >> >> Current Rampart trunk uses WSS4j 1.5.13. But WSS4J 1.6.4 is available >> with more features and bug fixes. It will add a great value to Rampart >> if we can migrate to WSS4J 1.6.4. Therefore we are working on >> upgrading WSS4J version to 1.6.4. We are planning to do this in >> following steps, >> >> 1. Upgrade OpenSAML version in Rampart trunk. Rampart currently uses >> both 1.1 and 2.2.3. We need to upgrade OpenSAML version to 2.5.1-1. >> This is the opensaml version used by WSS4J.
This is completed. Changes are commited to trunk and all integration tests and unit tests are also passing. Please refer [1] for more information. >> 2. Upgrade WSS4J version in trunk to 1.6.4, with minimum code changes. >> Objective of this step is to upgrade WSS4J version of Rampart and make >> sure all existing unit tests pass. This is in-progress. Thanks AmilaJ >> 3. Change Rampart code to use new WSS4J 1.6.4 API's and features and >> stabilize the code. This includes SAML2 features and Kerberos >> features. >> 4. Add more integration tests. >> >> As mentioned above we are planning to do above changes in trunk it >> self. > > Note that you also have the option to do the changes on a branch > (specifically created for that purpose) and to reintegrate them into > the trunk once they are stabilized. This frees you from the > requirement to keep the code buildable, i.e. you can check in partial > changes, even if they temporarily break the build or the tests. This > may be interesting if you need to get feedback/contributions from > other developers. If you use the corresponding Subversion features > correctly, then maintaining such a branch doesn't add much overhead. > >> The current Rampart releases (1.6.x) will remain supporting >> WSS4J 1.5.x. >> Relevant Jiras for OpenSAML and WSS4J version upgrades are stated in >> [1] and [2]. Will create Jiras for new features as we proceed with >> changes. >> >> Comments/Feedback and Objections are welcome on above approach. >> >> [1] https://issues.apache.org/jira/browse/RAMPART-354 >> [2] https://issues.apache.org/jira/browse/RAMPART-355 >> >> Thank you >> Regards, >> AmilaJ >> >> -- >> Mobile : +94773330538 >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org >> For additional commands, e-mail: java-dev-h...@axis.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org > For additional commands, e-mail: java-dev-h...@axis.apache.org > -- Mobile : +94773330538 --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
