Andreas, I tried it with the current 1.6.2 snapshots of axis2 and rampart, and the client works fine. The bug was apparently due to rampart's policy serialization in earlier versions, as you described.
Thanks, Gordon Andreas Veithen wrote > > There are actually two things: > > 1. Neethi 2 (which is used in Axis2 1.5.x and 1.6.0) is much more > lenient and parses certain invalid policies without throwing an > exception. Neethi 3 (which is used starting with Axis2 1.6.1) no > longer accepts those policies and triggers the exception that you are > seeing. > > 2. When generating client code, Axis2 doesn't simply copy the policy > from the WSDL. It actually re-serializes the model created by Neethi > from the original policy. The problem is that in all released Rampart > versions (i.e. all versions up to and including 1.6.1), the code > responsible for serializing the policy has some issues that cause it > to produce invalid serialized policies in some cases. These invalid > policies are accepted by Neethi 2, but not by Neethi 3. That problem > has been fixed in Rampart 1.6.2-SNAPSHOT and 1.7.0-SNAPSHOT. > > Therefore the problem should only exist in Axis2/Rampart 1.6.1. Work > on the 1.6.2 releases will start soon, but there are no plans for > 1.7.0. Therefore you should test your code with 1.6.2-SNAPSHOT and > report if there are still issues (so that there is a chance to get > them fixed before the release). > > Andreas > -- View this message in context: http://axis2.867.n6.nabble.com/Policy-not-supported-is-it-a-bug-tp4340911p4880005.html Sent from the Axis2-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axis.apache.org
