I am not trying to say do not post on the mailing lists of course, but looking at what he had quoted below, a page full of conflicting info about supported standards, it is obvious it is a bug and deserves a JIRA to be fixed.
From: Sagara Gunathunga [mailto:sagara.gunathu...@gmail.com] Sent: Wednesday, April 25, 2012 9:36 AM To: java-user@axis.apache.org Subject: Re: [rampart-1.5.2] supported standards On Wed, Apr 25, 2012 at 8:43 PM, Philippe A. <futhar...@gmail.com<mailto:futhar...@gmail.com>> wrote: It is not unusual to post on the mailing list before reporting a bug. Who knows, I could get some feedback. . +1 Philippe. It always best practice to contact use list first if you not clear about the issue because user list is dedicated to provide user helps. If it's a real bug you can fill a JIRA later. It has very less chance to get response if you fill user issue in the JIRA and if it's not a real bug. The purpose of JIRA project is to track and mange identified issues/improvements of a project. 2012/4/18 George Stanchev <gstanc...@serena.com<mailto:gstanc...@serena.com>> Either way it is nice to submit a JIRAs, for encountered issues or for ENH requests, this way it has a chance of being addressed... From: Philippe A. [mailto:futhar...@gmail.com<mailto:futhar...@gmail.com>] Sent: Wednesday, April 18, 2012 10:22 AM To: java-user@axis.apache.org<mailto:java-user@axis.apache.org> Subject: Re: [rampart-1.5.2] supported standards Here's another documentation request. It would be very nice to document what parts of the standards are implemented by Rampart/Axis (or which aren't, whichever is easier to document). It would make users's lives easier. For example, I tried using sp:EncryptBeforeSigning with my sp:SymmetricBinding. It did not work. The request makes it to the server. The client faults on the response. Is it because of a bug or because it is not supported? There is no way for me to tell. 2012/4/17 Philippe A. <futhar...@gmail.com<mailto:futhar...@gmail.com>> Please also note that said page lists some specifications twice. WS Security Policy * WS-SecurityPolicy 1.1<http://specs.xmlsoap.org/ws/2005/07/securitypolicy/ws-securitypolicy.pdf> Web Services Trust Language (WS-Trust) * WS Trust 1.0 <http://specs.xmlsoap.org/ws/2005/02/trust/WS-Trust.pdf> WS Secure Conversation * WS Secure Conversation 1.0 <http://specs.xmlsoap.org/ws/2005/02/sc/WS-SecureConversation.pdf> WS-SX specifications * WS-SecurityPolicy 1.2 <http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/ws-securitypolicy-1.2-spec-os.pdf> * WS Trust 1.3<http://docs.oasis-open.org/ws-sx/ws-trust/200512/ws-trust-1.3-os.pdf> * WS Secure Conversation 1.3<http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512/ws-secureconversation-1.3-os.pdf> 2012/4/13 Philippe A. <futhar...@gmail.com<mailto:futhar...@gmail.com>> Hello, Is it possible to confirm that the list of specifications given here are up to date and supported by Rampart 1.5.2 (with Axis 1.5.6)? http://axis.apache.org/axis2/java/rampart/specifications.html I would suggest to include some indication of when that page was last updated, be it a date or version number. Thanks, -- Philippe -- Philippe -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/> LinkedIn - http://www.linkedin.com/in/ssagara
